On 10/26/2010 7:09 AM, Brett Mahar wrote:
> I agree, there is no way that I could figure that out from reading the
> book.

Then you failed to read Section 5.3 "General Compilation Instructions".
This has been discussed many times, and it has always been determined
that we expect readers to actually *read* the book, and not skip any
sections. And if you read the book, you'll come across a box labeled
"IMPORTANT", that tells you what to do, followed by this:

> To re-emphasize the build process:
>
> 1. Place all the sources and patches in a directory that will be accessible 
> from the
>    chroot envronment such as /mnt/lfs/sources/.  Do not put sources in 
> /mnt/lfs/tools/.
> 2. Change to the sources directory.
> 3. For each package:
>    a. Using the tar program, extract the package to be built.
>    b. Change to the directory created when the package was extracted.
>    c. Follow the book's instructions for building the package.
>    d. Change back to the sources directory.
>    e. Delete the extracted source directory and any <package>-build
>       directories that were created in the build process.

If you do what it says, you can't go wrong. After many discussions
about this, it has been determined that placing instructions on each
package that requires additional packages would be redundant. It
cannot be emphasized enough; we expect readers to read the book. If
you elect not to read and comprehend the book, then it is assumed
that adding redundant information would be equally ignored.

Please don't construe my message as defending the rationale of why
it is done this way, I'm simply letting you know the thought process
of the original drafters of the book. Simon is correct in that this
issue is constantly addressed here in the LFS-Support list. And Simon's
message makes perfect sense, if it is determined that we wish to be
redundant. LFS is a technical book and is expected to be read from
the beginning, and that the reader understand each and every page of
the book.

Simon does have a good point in mentioning that we could explain
*why* the extra packages are required, but I'm not sure we want to
dumb down the book and explain the procedure of building when it has
already been explained.

> Googling I found some posts along the lines of "follow the book
> and it will be right" but to my reading of the book I did follow it
> and it was not right.

But it is right, you just didn't follow the instructions!


> But maybe it makes sense if you already know how to do it.
> Only after hours of web trawling and fine-print-reading of gcc mailing
> lists did I get to an explanation that made sense (and worked).
> Would be great to see this explanation made more clear!

Brett, I'm sorry you wasted several hours; however, please answer this
question. Why didn't you read Section 5.3, which in 5 minutes would
have made the process perfectly clear?

-- 
Randy

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to