glibc-2.3.2 (Chapter 5) is confused by earlier errors

Ronald Hummelink maillist at hummelink.xs4all.nl
Sat Nov 15 04:28:54 PST 2003


On Sat, 2003-11-15 at 13:05, Brett wrote:
> Hi
> 
> I'm trying to compile glibc-2.3.2 using the configuration given given in Chapter 5. I keep getting the errors below. I get the same results with gcc-3.3.1 and gcc-3.3.2. (I've also tried it with and without the glibc inlining-fixes patch).
> 
> ../sysdeps/generic/ldsodefs.h:273: error: declaration for parameter `_dl_lazy' but no such parameter
> ../sysdeps/generic/ldsodefs.h:270: error: declaration for parameter `_dl_verbose' but no such parameter
> ../sysdeps/generic/ldsodefs.h:267: error: declaration for parameter `_dl_clktck' but no such parameter
> ../sysdeps/generic/ldsodefs.h:259: error: declaration for parameter `_dl_platformlen' but no such parameter
> ../sysdeps/generic/ldsodefs.h:258: error: declaration for parameter `_dl_platform' but no such parameter
> ../sysdeps/generic/ldsodefs.h:256: error: declaration for parameter `_dl_osversion' but no such parameter
> ../sysdeps/unix/sysv/linux/init-first.c:67: error: `argc' undeclared (first use in this function)
> ../sysdeps/unix/sysv/linux/init-first.c:67: error: (Each undeclared identifier is reported only once
> ../sysdeps/unix/sysv/linux/init-first.c:67: error: for each function it appears in.)
> ../sysdeps/unix/sysv/linux/init-first.c:68: error: `argv' undeclared (first use in this function)
> ../sysdeps/unix/sysv/linux/init-first.c:69: error: `envp' undeclared (first use in this function)
> ../sysdeps/unix/sysv/linux/init-first.c:108: confused by earlier errors, bailing out
> make[2]: *** [/home/lfs/glibc-build/csu/init-first.o] Error 1
> make[1]: *** [csu/subdir_lib] Error 2
> make: *** [all] Error 2
> 

You're posting the last bit of the error, which doesn't hold the
information to help you easily.

Shameless copy paste from our ircbot ;)
<Ronald> gme?
<bugz> [Give make errors]: 1. Ignore lines showing an error number like:
"...] Error 1". 2. Ignore lines being "warnings". 3. Don't paste
anything before the actual command causing the error (gcc,g++,ld,...
line). 4. Don't paste the command itself unless if requested or if it's
small. 5. If there was many errors after the command, paste a few of the
earliest ones (3-4).

Ronald

> 
> Can someone tell me what I am doing wrong?
> 
> 
> Ta,
> 
> Brett
-- 
Linux is like a small snowball rolling downhill. Microsoft is just
waiting down the mountain...




More information about the lfs-support mailing list