Thanks for your pointing, after I change the --enable-add-ons as you suggested, "make" runs OK. But now installment fails.From: Joel Miller <[EMAIL PROTECTED]> Reply-To: LFS Support List <[email protected]> To: LFS Support List <[email protected]> Subject: Re: glibc compile Date: Fri, 11 Mar 2005 14:24:43 -0500
lin q wrote:Hi,
I am compiling glibc and have some problems. I am following the book to have the glibc 2.3.2 on a source directory and create a parallel directory to build. And the command is,
../glibc-2.3.2/configure --prefix=/usr --disable-profile --enable-add-ons --libexecdir=/usr/bin --with-headers=/usr/include
I see a lot of print out, at the end it says 2 add-ons are enabled, only one must be included.
But the thing is "ls" only shows one file, "config.log", there is no other files. Since the book says I should run make here in build directory, I had imagined there will be some Makefile, but no 2nd file at all!
It sounds like the configure step failed. That would be why a Makefile wan't created.
Then I go to the source directory and run "make", it quickly errors out saying, Makeconfig:84 error, can not find "config.amke", I go to that file, it is like, "$(common-objpfx)/config.make". I wonder how "common-objpfx" is defined?
Do you see anything wrong?
You did not need to go to the source directory to type make. All commands for glibc will be executed from the build directory. The reason a Makefile wasn't created was because the configure step failed. From the sound of your error, I'm going to guess that you have a glibc-2.3.2 tarball that contains both linuxthreads and nptl. I know in glibc-2.3.4 it will automatically choose nptl over linuxthreads, but perhaps this wasn't the case back in 2.3.2. If you're using glibc-2.3.2 you must be using the LFS 5.0 book, so my suggested fix for you would be instead of --enable-add-ons in the configure command, use --enable-add-ons=linuxthreads and see if the configure completes successfully.
Actually I checked the Makefile before I run make, I see that I need to set up an environment viable, inst_libdir, so for my case I run the make like this,
make inst_libdir=/mnt/mybld install
It runs for quite a while, and then it stops with the following error message,
/usr/bin/install -c <my glibc build directory>/libc.so /lib/libc.2.3.2.so.new
/usr/bin/install:error while loading shared libraries: libc.so.6: cannot handle TLS data
The worst thing is after this, I can not run "ls", "vi", "df", etc. basic commands, they all retern me this error, "libc.so.6: cannot handle TLS data".
I can do "cd" and "pwd" commands though.
I am afraid I damaged some critical library on the host system. But how come? Shouldn't I use that "inst_libdir" virable? If I just run "make install", it is more likely that the created library will be copied to host system.
So my questions are: 1) What is wrong in installing glibc 2) Seems my system is half-dead, is there any way to fix it?
Thanks!
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar � get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
