Hi,
Hi. Please don't reply to a message if your message has nothing to do with the message you're replying to. It messes up the message threading. Instead, just compose a new message. See the FAQ on netiquette if you have questions about this.
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.
-- Registered LFS User 6929 Registered Linux User 298182
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
