ch5+glibc builds fine on rh null, gcc errors out
nathanladd at yahoo.com
Fri Sep 20 16:48:34 PDT 2002
I know, null is about the closest thing to the opposite of a good distro to
build LFS in, but I wanted to give it a try. I thought that if there were
any problems, ch5 would be where they'd happen, but surprisingly it went
fine. glibc compiled too, but gcc did not. I am (or was) attempting to
install the latest cvs.
gcc's configure script ran ok (it didn't error out or produce any garbage
that I could identify as a problem; of course I'm not an expert) but the
actual compiling gave about 60-80ish lines of straight compiler warnings in
regex.c regarding traditional C not allowing things like string
concatenation and unsigned and signed vars being mixed in an expression.
I'm not sure this has anything to do with the problem (in fact more than
likely it does not, since the error is a missing file), but I'd rather give
too much than too little.
The showstopping error is as follows:
../../gcc-3.2/libiberty/regex.c:1422: warning: traditional C rejects string
../../gcc-3.2/libiberty/regex.c:1424: warning: traditional C rejects string
../../gcc-3.2/libiberty/regex.c:1425: warning: traditional C rejects string
../../gcc-3.2/libiberty/regex.c:1427: warning: traditional C rejects string
../../gcc-3.2/libiberty/regex.c: In function `xregcomp':
../../gcc-3.2/libiberty/regex.c:8099: warning: signed and unsigned type in
../../gcc-3.2/libiberty/regex.c: In function `xregerror':
../../gcc-3.2/libiberty/regex.c:8234: warning: unused parameter `preg'
if [ x"-fpic" != x ]; then \
gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../gcc-3.2/libiberty/../include -W
-Wall -Wtraditional -pedantic -fpic ../../gcc-3.2/libiberty/cplus-dem.c -o
else true; fi
In file included from ../../gcc-3.2/libiberty/cplus-dem.c:41:
bits/sys_errlist.h: No such file or directory
make: *** [cplus-dem.o] Error 1
make: Leaving directory `/usr/src/lfs/gcc-build/libiberty'
make: *** [all-libiberty] Error 2
I checked the /static/include/bits directory (sys_errlist is at
/usr/include/bits in my host distro) and sure enough it wasn't there. I
think whatever package produces this file in ch5 silently errored (at least
I hope it errored silently--I would feel really dumb if I found out I
didn't notice an obvious error and went along my way).
Anyways, sorry for the long post, I just wanted to be verbose.
If the brain were so simple that we could understand it, we would be so
simple that we could't.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev