make errors while compiling glibc-2.10.1 in LFS - 6.5
Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Thanks for your help and I got the doubts cleared upto here...
Now new problem creep in....
I am getting errors while compiling binutils-2.19.1-pass 2...
make: Entering directory `/mnt/lfs/sources/binutils-build'
Configuring in ./intl
configure: loading cache ./config.cache
configure: error: `CC' has changed since the previous run:
configure: former value: `gcc'
configure: current value: `i686-lfs-linux-gnu-gcc -B/tools/lib/'
configure: error: `target_alias' has changed since the previous run:
configure: former value: `i686-lfs-linux-gnu'
configure: current value: `i686-pc-linux-gnu'
configure: error: in `/mnt/lfs/sources/binutils-build/intl':
configure: error: changes in the environment can compromise the build
configure: error: run `make distclean' and/or `rm ./config.cache' and start over
make: *** [configure-intl] Error 1
make: Leaving directory `/mnt/lfs/sources/binutils-build'
make: *** [all] Error 2
My host system satisfy all requirements as stated in the book...
please help..... Thanks in advance
Last edited by _Linux_Learner; 04-05-2010 at 08:36 AM.
It looks like you did not remove the previous source and/or build directory.
You need to start every build with a clean sheet. Remove the source and binutils-build directory, untar the binutils package and start again.
There is a small possibility that the source isn't clean to begin with (although I did not run into this when building LFS 6.5). If, after cleanly starting, you still get this message you could try the suggestion in the error message: configure: error: run `make distclean' and/or `rm ./config.cache' and start over. But like I stated before, I doubt this is the problem.
hey _Linux_Learner I am currently on the exact same step and found the answer to the not removing previous install bit...
anyway to answer your question... the meaning is given below the command in the book...
in short [and from my limited understanding] we are now setting the cross-compiler and tools to use the new system we are building and not the host system.... [only sort of makes seance to me 2....] so we should now have 2 versions of binutils one for the host and one for the new system... [I think... some one please correct me if I am wrong!!!]
The meaning of the new configure options:
CC="$LFS_TGT-gcc -B/tools/lib/" AR=$LFS_TGT-ar RANLIB=$LFS_TGT-ranlib
Because this is really a native build of Binutils, setting these variables ensures that the build system uses the cross-compiler and associated tools instead of the ones on the host system.
This tells the configure script to specify the library search path during the compilation of Binutils, resulting in /tools/lib being passed to the linker. This prevents the linker from searching through library directories on the host.