On 05 June 2007 01:57, Tim Prince wrote:

> christian.joensson wrote:
>> phew, a few of the cygwin failures show up like this:
>> 
>> Executing on host: /usr/local/src/trunk/objdir/gcc/xgcc
>> -B/usr/local/src/trunk/objdir/gcc/   -O3 -g  -w -fno-show-column -c
>> -o 20001226-1.o
>> /usr/local/src/trunk/gcc/gcc/testsuite/gcc.c-torture/compile/20001226-1.c 
>> (timeout = 300) spawn /usr/local/src/trunk/objdir/gcc/xgcc
>> -B/usr/local/src/trunk/objdir/gcc/ -O3 -g -w -fno-show-column -c -o
>> 20001226-1.o
>> /usr/local/src/trunk/gcc/gcc/testsuite/gcc.c-torture/compile/20001226-1.c
>> /cygdrive/c/DOCUME~1/chj/LOCALS~1/Temp/cc2eakcj.s: Assembler messages:
>> /cygdrive/c/DOCUME~1/chj/LOCALS~1/Temp/cc2eakcj.s:0: Warning: end of 
>> file in string; '"' inserted
>> /cygdrive/c/DOCUME~1/chj/LOCALS~1/Temp/cc2eakcj.s:18: Warning: .stabs:
>> missing comma
> 
>> 
>> Windows XP Pro/SP2 cygwin
>> cygwin               1.5.24-2       (with D Korn's stdio.h patch to newlib)
> 
> trigraphs.c also failed for me for the first time, objecting to the
> patched version of stdio.h.


  Is there any reason to suppose these are connected?  You didn't mention what
kind of error you're seeing yet.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Reply via email to