On 10/26/10 02:52, Simon Geard wrote:
> On Mon, 2010-10-25 at 22:14 -0700, lfs wrote:
>> So the question is, Should I create the gcc-build directory and *then*
>> untar gmp,mpfr, mpc, from that(gcc-build) directory
> No. Remember the rule - before starting on a particular page, extract
> it's tarball, and cd into the directory. So, when extracting gmp, mpfr,
> and mpc, you should be in the GCC source directory (gcc-4.5.1).
>
> The idea is that you should then have 'gmp', 'mpfr' and 'mpc'
> directories within the main GCC source, and the reason is that they'll
> be built by GCC automatically. Unfortunately, the book doesn't really
> explain this, with the result that people seem to improvise this part,
> instead of following the instructions to the letter.
>
>
> Editors, can we perhaps add some extra text to the GCC Pass 1
> instructions (and perhaps a short reminder to Pass 2 as well)? Right
> now, all the book has to say is:
>
> "GCC now requires the GMP, MPFR and MPC packages. As these
> packages may not be included in your host distribution, they
> will be built with GCC"
>
> Can we go into a bit more detail about that "build with GCC" bit?
> Extracting seemingly unrelated tarballs into the GCC source tree *is* an
> unusual thing to do, unless you're aware that the GCC build will
> magically build those packages if present. A short explanation of how
> this works, and why we do it would 1) improve the educational aspects of
> the book, and 2) discourage people from improvising because the
> instructions seem wrong.
>
> Simon.
Thank you Simon.
That information would be a *great* help.
As it was, I created the gcc-build directory, and then packed the three
files from the gcc source dir., then I entered each dir and executed
`./configure' and
`./make', with no `make install', for each of the three dirs,.
I then unpacked gcc and did the triple (configure, make, make install)
and all went perfect.
But your point about gcc building the triple was the *exact discussion I
had with my wife, that the wording implied that gcc would build
(configure,make) the programs.
Here is a copy of my file that I am trying to follow to the letter:
Important
After installing each package, delete its source and build directories,
unless specifically instructed otherwise. Deleting the sources prevents
mis-configuration when the same package is reinstalled later.
Important
The build instructions assume that the bash shell is in use.
Important
Before issuing the build instructions for a package, the package should
be unpacked as user lfs, and a cd into the created directory should be
performed.
To re-emphasize the build process:
1. Place all the sources and patches in a directory that will be
accessible from the
chroot environment 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.
I see from your post another mistake I have made, and that is not
untaring the file before I start the page.
I have started the page from the top down.
And the 3rd *important* above does not convey that thought to me.
Could you or someone point me to the instructions that I have missed or
misinterpreted?
My thanks goes to all who work on this project (lfs) as it is a great
learning experience.
Peace
Nolan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
