BUILD Failing
Matthew H Bemis
bemis@iol.unh.edu
Sat Nov 17 06:33:00 GMT 2001
> I have automated builds of gcc that run daily,, and ever since the 9th
> of Novemember I have not bee able to produce a gcc.o file. I get an
> error message that a temporary assembly file /tmp/ccxxxx.s file has
> inappropriate arguments for opcode 'ldq_u'. Just before the Error I get
> warnings that look like :
>
> /mnt/u2/toolchain/buildsys/source/gcc-head/gcc/gcc.c:803: warning:
> string length `564' is greater than the length `509' ISO C89
> In file included from specs.h:1,
> from
> /mnt/u2/toolchain/buildsys/source/gcc-head/gcc/gcc.c:832:
> /mnt/u2/toolchain/buildsys/source/gcc-head/gcc/cp/lang-specs.h:38:
> warning: string length `868' is greater than the length `509' ISO C89
> compilers are required to support
> /tmp/ccPg17YL.s: Assembler messages:
>
>
> the error is listed below
>
> /tmp/ccPg17YL.s:7195: Error: inappropriate arguments for opcode `ldq_u'
> make[2]: *** [gcc.o] Error 1
> make[2]: Leaving directory
> `/mnt/u2/toolchain/buildsys/build/alpha7/unknown/native/gcc-head/gcc'
> make[1]: *** [stage2_build] Error 2
> make[1]: Leaving directory
> `/mnt/u2/toolchain/buildsys/build/alpha7/unknown/native/gcc-head/gcc'
> make: *** [bootstrap] Error 2
>
has anyone seen this before...if so how would you go about debugging this?
Matt Bemis
Alpha Linux Consortium
Interoperability Lab UNH
More information about the Gcc
mailing list