On Tue, Jul 03, 2012 at 08:02:43PM +0530, Emerson Yesupatham wrote: > > Emerson: Yes, this is my first build. I thought the value for > --enable-kernel must be the "same" as Host systems linux version (uname -r). > Now, I did little bit research on --enable-kernel option and found the > following excerpt from > http://www.gnu.org/software/libc/manual/html_node/Configuring-and-compiling.html > > >>‘--enable-kernel=version’ > >>This option is currently only useful on GNU/Linux systems. The > >>versionparameter should have the form X.Y.Z and describes the smallest > >>version of > the Linux kernel the generated >>library is expected to support. The higher > the version number is, the less compatibility code is added, and the faster > the code gets. > > So I understand that, in case I need to boot a linux version lesser than > 2.6.35 then it is better to give a smallest version like 2.6.25 in > --enable-kernel option. However, I have question now, Is there any > dependecy between Host system's kernel version and --enable-kernel option? > why the LFS build is not proceeding if we give --enable-kernel=2.6.25 and > the actual Host systme linux version is less than it say 2.6.11 as in my > previous linux. Now I have upgraded my linux from 2.6.11 to 2.6.35. > While you are using the temporary libc compiled in /tools, and the final libc while you are still in chroot, you are running on the host system's kernel. So, if the host has a 2.6.11 kernel then it *cannot* run applications linked against a libc compiled for >= 2.6.25.
There are also tests in the glibc configure system: it will not build if you specify a kernel version greater than you are running. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
