[lfs-dev] glibc-2.15 with i686

Pierre Labastie pierre.labastie at neuf.fr
Tue Mar 27 09:47:50 PDT 2012


Le 27/03/2012 15:12, Matthew Burgess a écrit :
>> 2- When building without optimization (noOpt in jhalfs), there is an error
>>
>> "glibc cannot be built without optimization"
> Is this a regression from Glibc-2.14.1?  It certainly sounds like an explicit
> decision from upstream.
Well, I have to test again and my 32 bit computer is slow (I never built 
glibc
with noOpt before). Will tell tomorrow...

Another thing:

I hit http://lists.gnu.org/archive/html/bug-binutils/2011-10/msg00235.html
when building binutils-pass2:

/bin/sh ./libtool --tag=CC   --mode=compile i686-lfs-linux-gnu-gcc 
-B/tools/lib/ -DHAVE_CONFIG_H -I. -I../../binutils-2.22/opcodes  -I. 
-I../../binutils-2.22/opcodes -I../bfd 
-I../../binutils-2.22/opcodes/../include 
-I../../binutils-2.22/opcodes/../bfd    -W -Wall -Wstrict-prototypes 
-Wmissing-prototypes -Wshadow -Werror -O3 -pipe -MT i386-dis.lo -MD -MP 
-MF .deps/i386-dis.Tpo -c -o i386-dis.lo 
../../binutils-2.22/opcodes/i386-dis.c
libtool: compile:  i686-lfs-linux-gnu-gcc -B/tools/lib/ -DHAVE_CONFIG_H 
-I. -I../../binutils-2.22/opcodes -I. -I../../binutils-2.22/opcodes 
-I../bfd -I../../binutils-2.22/opcodes/../include 
-I../../binutils-2.22/opcodes/../bfd -W -Wall -Wstrict-prototypes 
-Wmissing-prototypes -Wshadow -Werror -O3 -pipe -MT i386-dis.lo -MD -MP 
-MF .deps/i386-dis.Tpo -c ../../binutils-2.22/opcodes/i386-dis.c -o 
i386-dis.o
../../binutils-2.22/opcodes/i386-dis.c: In function 'print_insn':
../../binutils-2.22/opcodes/i386-dis.c:11334:17: error: array subscript 
is above array bounds [-Werror=array-bounds]
cc1: all warnings being treated as errors
make[5]: *** [i386-dis.lo] Error 1
make[5]: Leaving directory `/mnt/lfs/sources/binutils-build/opcodes'

------------------
According to the bug report, it appears when binutils is built with -O3 
with gcc-4.7.0. I am sure
it is a regression. There is a trivial patch in the thread above. Of 
course, you can also just tell me
to not use optimization. But it was perfectly working with the preceding 
toolchain...

Regards
Pierre




More information about the lfs-dev mailing list