Make error in glibc

Chris Staub chris at
Tue May 4 22:17:28 PDT 2010

On 05/05/2010 12:57 AM, gaurav k wrote:
> I'm inside the extracted glibc directory, and this is what I do:
> $mkdir -v ../glibc-build
> $cd ../glibc-build
> $echo "CFLAGS += -march=i486 -mtune=native">  configparams

Assuming this is a literal copy of what you actually typed, this is 
incorrect. It's "configparms" not "configparams".

> $../glibc-2.11.1/configure --prefix=/tools --host=$LFS_TGT --build=$(../glibc-2.11.1/scripts/config.guess) --disable-profile --enable-add-ons --enable-kernel=2.6.18 --with-headers=/tools/include/ libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes
> $make
> What I tried was, I redirected the output of the following command to a file:
> $../glibc-2.11.1/configure --prefix=/tools --host=$LFS_TGT --build=$(../glibc-2.11.1/scripts/config.guess) --disable-profile --enable-add-ons --enable-kernel=2.6.18 --with-headers=/tools/include/ libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes>  file.txt
> and so was able to see the following on the shell:
> configure: WARNING: using cross tools not prefixed with host triplet
> configure: WARNING:
> *** These auxiliary programs are missing or incompatible versions: msgfmt makeinfo autoconf
> *** some features will be disabled.
> *** Check the INSTALL file for required versions.
> configure: WARNING: cpuid.h: present but cannot be compiled
> configure: WARNING: cpuid.h:     check for missing prerequisite headers?
> configure: WARNING: cpuid.h: see the Autoconf documentation
> configure: WARNING: cpuid.h:     section "Present But Cannot Be Compiled"
> configure: WARNING: cpuid.h: proceeding with the preprocessor's result
> configure: WARNING: cpuid.h: in the future, the compiler will take precedence
> I'm guessing THIS is the real problem?

No idea (though I think the above misspelling of configparms is the real 
issue), but the message about not finding makeinfo does also indicate 
that you've missed a page. See "Host System Requirements" and make sure 
you actually do have everything listed there.

More information about the lfs-support mailing list