Hi As I hadn't gone too far, I've scrapped my first attempt and starting again. It'll be interesting to see if I hit the same problem.
Cheers Gena On Wed, May 10, 2006 at 08:29:46PM +0100, Ken Moffat wrote: > On Wed, May 10, 2006 at 01:17:03PM +0100, Georgina Joyce wrote: > > Hi > > > > I have a debian sarge host system using gcc-3.3 and everything has gone > > well following the steps in the book, great job. However, I'm having > > problems with the second pass of gcc and I don't know what I've done, or > > not done. I've searched and a posting stated that someone had the same > > error with the second pass of binutils and the response was to use another > > version. What do I need to do? > > > > executing default commands > > make[1]: Entering directory `/mnt/lfs/gcc-build/libiberty' > > if [ x"-fpic" != x ]; then \ > > gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../gcc-3.4.3/libiberty/../include -W > > -Wall -Wtraditional -pedantic -fpic ../gcc-3.4.3/libiberty/regex.c -o > > pic/regex.o; \else true; fi > > In file included from ../gcc-3.4.3/libiberty/../include/xregex.h:26, > > from ../gcc-3.4.3/libiberty/regex.c:195: > > ../gcc-3.4.3/libiberty/../include/xregex2.h:548: warning: ISO C90 does not > > support `static' or type qualifiers in parameter array declarators > > In file included from ../gcc-3.4.3/libiberty/regex.c:649: > > ../gcc-3.4.3/libiberty/regex.c: In function `byte_compile_range': > > ../gcc-3.4.3/libiberty/regex.c:4548: warning: signed and unsigned type in > > conditional expression > > ../gcc-3.4.3/libiberty/regex.c:4558: warning: signed and unsigned type in > > conditional expression > > ../gcc-3.4.3/libiberty/regex.c:4558: warning: signed and unsigned type in > > conditional expression > > ../gcc-3.4.3/libiberty/regex.c: In function `xregcomp': > > ../gcc-3.4.3/libiberty/regex.c:8043: warning: signed and unsigned type in > > conditional expression > > ../gcc-3.4.3/libiberty/regex.c: At top level: > > ../gcc-3.4.3/libiberty/regex.c:8178: warning: unused parameter 'preg' > > Assembler messages: > > FATAL: can't create pic/regex.o: No such file or directory > > make[1]: *** [regex.o] Error 1 > > make[1]: Leaving directory `/mnt/lfs/gcc-build/libiberty' > > make: *** [all-libiberty] Error 2 > > [EMAIL PROTECTED]:/mnt/ > > > > Regards > > > > Gena > > > > Did you extract a fresh source tarball, and create a fresh build > directory ? The only references to that message that I can see on > google are from a failed cross-compile (no reason established, the > builder was pointed to a more authoritative method of doing it) and on > linuxquestions, for both binutils and gcc, where the problems seemed > to be related to reusing the pass 1 directories. > > We only normally tell people to use a different version of binutils > if they are building from fedora! (the fedora versions are often too > new for what is in the last release). > > 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 ---end quoted text--- -- 2E0AXU Freedom & Power provided by debian GNU Linux -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
