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.
I am a LFS newbie, my HOST MACHINE INFORMATION:
Linux version 2.6.9-1.667 (email@example.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:25 EST 2004
I am encountering the following error when i try installing glibc
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking sysdep dirs... sysdeps/i386/elf nptl/sysdeps/unix/sysv/linux/i386/i686 nptl/sysdeps/unix/sysv/linux/i386 nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread nptl/sysdeps/unix/sysv nptl/sysdeps/unix nptl/sysdeps/i386/i686 nptl/sysdeps/i386 sysdeps/unix/sysv/linux/i386 sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv/i386 sysdeps/unix/sysv sysdeps/unix/i386 sysdeps/unix sysdeps/posix sysdeps/i386/i686/fpu sysdeps/i386/i686 sysdeps/i386/i486 nptl/sysdeps/i386/i486 sysdeps/i386/fpu sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for gcc... gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether /tools/bin/as is GNU as... yes
checking whether /tools/bin/ld is GNU ld... yes
checking for /tools/bin/as... /tools/bin/as
checking version of /tools/bin/as... 2.15, ok
checking for /tools/bin/ld... /tools/bin/ld
checking version of /tools/bin/ld... 2.15, ok
checking for pwd... /bin/pwd
checking for gcc... gcc -B/tools/bin/
checking version of gcc -B/tools/bin/... 4.0.0, bad
checking for gnumake... no
checking for gmake... gmake
checking version of gmake... 3.80, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... msgfmt
checking version of msgfmt... 0.14.1, ok
checking for makeinfo... makeinfo
checking version of makeinfo... 4.7, ok
checking for sed... sed
checking version of sed... 4.1.2, ok
checking for autoconf... autoconf
checking whether autoconf works... yes
***These programs are missing are missing or too old : gcc
***Check the INSTALL file for required versions
Plase help me to rectify this problem....
thanx in advance
the line that shows gcc bad, is not of the host machine, it is the new gcc i have installed.. its newer than the prescribed gcc-3.4.1[as per LFS v6]. Am i right? and also the gcc got compiled without any issues....
I am listing the versions of the things i am using for the target..
Another thing, When i tried creating version file as described in pg 49 LFSv6: "make include/linux/version.h", i am geting the following report:
Makefile:486: .config: no such file or directory
But the version file is getting created, is it ok....
In jist i am getting struck in 2 places:
1]While creating version.h file as described in pg 49 LFS v6
2]while compiling glibc as described in pg 51 LFS v6 (i have put the output in my first post)
since there is no gcc-4.0 (that i know of) it is actually finding the newly installed gcc-3.4.1 but for whatever reason the 3.4.1 is being referred to as gcc-4.0, right? it's finding the 3.4.1 but thinks it's a 4.0, which it can't use.
i'm wondering how in the world a 4.0 reference got in there in the first place...
Thanx for supporting, i am going to download all the things with the vertions as prescribed by LFS 6 afresh including the kernel and start the whole story all over again.Let me hope 2 find luck on this go....
Thank u all......
the .config is the configuration file for the kernel compile. since you just untarred the archive, you will not have one yet, so this warning is expected. later when you actually configure your kernel to build it, you will create a .config file. basically, this is normal operation.
note that your earlier problem is glibc will check your gcc version and accept it or reject it. with applications it's ok/good to have the latest and greatest, with toolchains ( your devel environment) some versions of software work better than others when pared with certain versions of this software which works best with this version of software and etc... you get the idea - sometimes with development environments you need specific versions to make it as stable and efficient as possible. I'd recommend just sticking with the book versions, LFS systems have always had a very good development environment.
once you get your temp. toolchain built, I'd recommend using tar to back it up just in case, you never know when/if you might need it in the future:
tar -cf toolchain.tar /tools
(optionally if you want it compressed): gzip toolchain.tar
also, now is a good time ( sometime before you start the actual system building) to head over to the hints section at one of the LFS mirrors and check into those, there are alot of ways you can customize your system and tweak it to your liking. None of them are mandatory, but you should at least check into some type of package management to make upgrading/removal of packages more convenient.
hmmm...., i have now downloaded all the stuff including the patches given in pg 25 LFS v6..
I have a doubt..[might appear silly..] when should we apply these patches...
As far as I have seen ther are no commands mentioned in the LFSv6 Document???
Any inputs on these?????