On Tue, 26 Jul 2005, Alex Smith wrote: > I am receiving the following error when compiling GCC-3.4.3 in Chapter 6 > of the LFS 6.1 book: > > > if [ x"-fpic" != x ]; then \ > > /sources/workdir/src/gcc-build/gcc/xgcc > > -B/sources/workdir/src/gcc-build/gcc/ -B/usr/i686-pc-linux-gnu/bin/ > > -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include > > -isystem /usr/i686-pc-linux-gnu/sys-include -c -DHAVE_CONFIG_H -O2 > > -march=i686 -O2 -pipe -Wl,-O1 -I. > > -I../../../gcc-3.4.3/libiberty/../include -W -Wall -Wtraditional > > -pedantic -fpic ../../../gcc-3.4.3/libiberty/cplus-dem.c -o > > pic/cplus-dem.o; \ > > else true; fi > > ../../../gcc-3.4.3/libiberty/cplus-dem.c:55: error: conflicting types > > for 'malloc' > > ../../../gcc-3.4.3/libiberty/cplus-dem.c:55: error: conflicting types > > for 'malloc'
> > make[1]: *** [cplus-dem.o] Error 1 > > make[1]: Leaving directory > > `/sources/workdir/src/gcc-build/i686-pc-linux-gnu/libiberty' > > make: *** [all-target-libiberty] Error 2 > > > Do you know what is causing this. The only change I have made from the > LFS book is that I have used Glibc 2.3.5 instead of 2.3.4 > > Thanks, Alex > > Well, I've no idea what is breaking it, but the -march=i686 looks like a change from the book (although I believe it will probably produce a better system than omitting it), so maybe you changed something else that has slipped your memory ? Based on an incomplete understanding of what google dredged up, maybe you missed the no_fixincludes patch, either for this build, or perhaps in chapter 5 pass 2 ? Ken -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
