Hi, New to LFS

I am following the directions from the book:
http://www.linuxfromscratch.org/lfs/...tructions.html

I am in chapter 5 (binutils pass 2) and I have not seen any package builds that instruct you to retain said directories.

There are two reasons I am concerned.

1. This is my second attempt to build the toolchain. My last attempt failed to make Perl (5.29. Perl-5.22.1). I already triple checked my environment and the host system (Debian 7.9 Wheezy) requirements and they are OK. I suspect I missed something so I started over.


2. I came across some LFS instructions for an older version (V6.1.1) found here:
http://www.tldp.org/LDP/lfs/LFS-BOOK-6.1.1.txt

It mentions:
Then in binutils pass 1 these older instructions say:
These older instructions also mention the same for tcl and pass 2 of binutils.


I see no mention of this in the book for LFS version 7.9 for any steps in chapter 5 so far.

I just want to make sure I'm not missing anything. Could somone please let me know at what steps in LFS 7.9 you need to retain the source (and build) directories if any? As I said, I made it to step 5.22 (last try) and did not see mention of this exception to removing the directories.

Thanks,
Tim

You dont need to keep any of the untarred dirs once you have built the package, The source " tarballs" you need to keep for use againin Ch6, some are used a 2nd time in Ch5. All dirs are removed after being built.

1 members found this post helpful.

That's right, and the old versions of the book are not of much use as guidance building the current version today. They are historically interesting but pretty much irrelevant now. For example, version 1.0 in 1999 built toolchain packages in the host system with static libraries and copied the binaries created to $LFS. Also, back then, the init system and kernel were installed first. By version 2.1.5 in 2000, the toolchain stuff was still being compiled with static libraries, but in $LFS/usr. Version 4.0 in 2002 introduced the idea of the $LFS/static directory to keep all that toolchain stuff from cluttering the LFS system directories. The cross-compiler idea appeared in version 5.0 in 2003, but the first passes of binutils and gcc were still being compiled with static libraries. That version also was the first to mention the $LFS/tools directory. By 2005, version 6.1 came along with the basic cross-compiler techniques still used today. Even so, the packages and details are constantly changing.

2 members found this post helpful.

Thank You so much to both of you for the quick replies that exactly answered my question

I do find the LFS 7.9 documentation thorough and informative but I just felt the need
to double check that I didn't miss something regarding retention of those untarred source and build directories
as my first attempt of the tool chain build died at the Perl make.

Also, Thank you stoat for the LFS history synopsis. Seems like excellent progress over the years!

You guys Rock !!

Now the make of gcc -second pass just finished on this Pentium 4. So Onward !
Now if I can just make it past the Perl make this time, he he

Thanks and all the best,
Tim

When a careful person is following exactly the stable book and runs into a single package that fails to build over and over, it seems to me that a common explanation is one of the prerequisites being off. I know you said that you checked that, but just make sure you checked it carefully. For example, a common one is /bin/sh pointing to /bin/dash instead of /bin/bash. That one digit in the output of version-check.sh derails a lot of efforts around here. If Perl fails again, you can post the version-check output if you want extra eyes to go over it.

Thanks stoat.
Well, it wasn't over and over, just my first try that Perl make failed.

But, since you offered

Here is the output of my bash-version-check.sh


I always appreciate a second set of eyes !

Thanks,
Tim

Just to add in case someone googles (or duck-duck's) Perl make fail, I'd like to mention
that I really think that from my analysis of my Perl make output (tee is your friend!),
I am leaning toward something going wrong in my first tool chain build happening either
in the second pass of binutils or gcc. That is why I started over.

I posted because I was not sure and wanted to pass this by the seasoned experts here.

I'd really appreciate it if there is anything you see in my version-check that you see that needs addressing.
Please, Feel free to opine

If I have other issues not related to the OP topic, I'll open a new thread.

Thanks again,
Tim

I never keep sources from LFS lying around. Mostly, I program buildscripts to avoid this.

I have my scripts made to work with Slackware's pkgtools tucked away nicely in my /usr/src directory on a spare partition.

Every BLFS package is segregated while the core system is a single tarball.

1 members found this post helpful.

Just to update in case this thread may be helpful to others.

First, I now sucessfully completed my toolchain build of LFS 7.9

Now the possibly helpful part:

I was wondering where I went wrong on my first attempt.
That is why I was reviewing the process and came upon the mention of retained package builds
and posted my question.

Here it is (after context):

I do not copy and paste from the book directly to the comamnd line. I paste to a document
(ascii text) first so I can add tee to the commands for logging of the configure,
make, make install, make test (If I want), etc.. . Then copy and paste from there.

I figured that I could use the tee'd output to help troubleshoot if in case anything went wrong
and use them to help others in case they had issues.

I have also for comparison, downloaded the logs from:
http://www.linuxfromscratch.org/lfs/...able/i7-5820K/

and wrote scripts to compare my tee'd output to those for another type
of "Sanity check" as well as "grepping" for error, warning or fail.

Anyway, before I get TL;DR ..

In the second pass of gcc in chapter 5:

Seems somehow I added character after the line contuation \ which seemed to cause all the other directives to be ignored.

Interestingly, all the following steps "worked" until the make of Perl.
.. However, There were some interesting warnings.
Be careful not to dismiss those as due to differences in the "Included Host system" versions used.

So yes, the instructions in the book "Just Works".
Just be careful and double check before you hit enter !
And when it's been a long day, know when to call it quits
lol

Backups of your toolchain may not be a bad Idea as well especially
if building on a slower system.

I keep mine on an unmounted partition for safety.


@ReaperX7,
Thanks for sharing the helpful advice!
.. My scripting will come later.
I just want to do this "by hand" first and then make it more fun and fancy
All advice is most welcome!


On to Chapter 6

Thanks to you all and those at the LFS Project.

All the best and hope that helps,
Tim

Just as a side note, you might want to reinstall several packages from the LFS book and core after you get enough done to repackage and update core packages.

Whatever you do, do not touch glibc or kernel-headers. Leave them be. The book even says if you need to update those, it's just better to rebuild from scratch.

? Are you referring to my upcoming build of my actual LFS system (Chapter 6) or updating my tool-chain before proceeding?
before I start ?

Thanks,
Tim

@ReaperX7

Yep, .. repackage, update .. Thanks !!
hmm, That may be sooner than later.
Awesome!