glibc fclose prob? was: Problem egcs-2.93.02

[Franz Sirl]

At 16:50 25.01.99 , Robert Lipe wrote:
>Kaoru Fukui wrote:
>
>> make[1]: Entering directory `/usr/src/redhat/BUILD/obj-ppc-linux/gcc'
>> rm -f SYSCALLS.c tmp-SYSCALLS.s
>> cat /usr/src/redhat/BUILD/egcs/gcc/sys-types.h 
>/usr/src/redhat/BUILD/egcs/gcc/
>> sys-protos.h > SYSCALLS.c
>> /usr/src/redhat/BUILD/obj-ppc-linux/gcc/xgcc 
>-B/usr/src/redhat/BUILD/obj-ppc-linux/
>> gcc/ -B/usr/ppc-redhat-linux/bin/  -DIN_GCC -DHAIFA    -O2 -fsigned-char
-I./
>> include     -I. -I/usr/src/redhat/BUILD/egcs/gcc 
>-I/usr/src/redhat/BUILD/egcs/
>> gcc/config -I/usr/src/redhat/BUILD/egcs/gcc/../include \
>>   -aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c
>> xgcc: Internal compiler error: program cpp got fatal signal 11
>> make[1]: *** [SYSCALLS.c.X] Error 1
>> make[1]: Leaving directory `/usr/src/redhat/BUILD/obj-ppc-linux/gcc'
>> make: *** [all-gcc] Error 2
>> 
>> My system is glibc-2.0.110.
>> Mklinux on Pm-6100 .
>
>
>I've seen what I suspect is the same problem.  I had been blaming glibc
>or the new kernels becuase the same EGCS source builds fine on two other
>ia32 targets here.  A few weeks ago, I upgraded my Linux lab system to
>the glibc-2.0.reallybignumber families becuase I needed the 2.2.prepatch
>series.
>
>Here's what the failure looks like.
>
>Core was generated by `./cpp -lang-c -isystem 
>/usr/local/i686-pc-linux-gnu/bin/include -isystem ./incl'.
>Program terminated with signal 11, Segmentation fault.
>Reading symbols from /lib/libc.so.6...done.
>Reading symbols from /lib/ld-linux.so.2...done.
>#0  0x400680da in _IO_new_fclose (fp=0x8060ea0) at iofclose.c:45
>iofclose.c:45: No such file or directory.
>Breakpoint 1 at 0x40037a46: file ../sysdeps/generic/abort.c, line 55.
>Breakpoint 2 at 0x40038bb5: file exit.c, line 40.
>Breakpoint 3 at 0x8059cdb: file /play/egcs/gcc/cccp.c, line 10692.
>(gdb) up
>#1  0x804c501 in main (argc=33, argv=0xbfffea54) at /play/egcs/gcc/cccp.c:2318
>2318      if (ferror (stdout) || fclose (stdout) != 0)
>(gdb) print *stdout
>$1 = {_flags = -72539124, _IO_read_ptr = 0x0, _IO_read_end = 0x0, 
>  _IO_read_base = 0x0, _IO_write_base = 0x0, _IO_write_ptr = 0x0, 
>  _IO_write_end = 0x0, _IO_buf_base = 0x0, _IO_buf_end = 0x0, 
>  _IO_save_base = 0x0, _IO_backup_base = 0x0, _IO_save_end = 0x0, 
>  _markers = 0x0, _chain = 0x8060e50, _fileno = -1, _blksize = 0, 
>  _old_offset = -1, _cur_column = 0, _vtable_offset = -72 '¸', _shortbuf =
"", 
>  _lock = 0x400f9150, _offset = -1, _unused2 = {1074707008, 
>    0 <repeats 15 times>}}
>
>
>If I remove the call/test for fclose:
>
>	  if (ferror (stdout) /* || fclose (stdout) != 0 */)
>		    fatal ("I/O error on output");
>
>compilation proceeds.
>
>I've tried a couple of RPMs from Rawhide ranging from (I think) 107 to
>109.  .110 won't unpack for me this morning.

No, the problem is that you need newer binutils, which are not yet
released. hjl is working on backporting these patches to the upcoming
binutils-2.9.1.0.20. Current mainline as of now won't build anyways due to
other problems (probably due to CONSTANT_P_RTX handling again? rth?):

_eprintf
_bb
../../../egcsm/gcc/varasm.c:3265: Internal compiler error in function
decode_rtx_const
Please submit a full bug report to `egcs-bugs@cygnus.com'.
See <URL: http://egcs.cygnus.com/faq.html#bugreport > for details.
make[4]: *** [libgcc2.a] Error 1
make[4]: Leaving directory `/home/fsirl/obj/cvsm/gcc'
make[3]: *** [stmp-multilib-sub] Error 2
make[3]: Leaving directory `/home/fsirl/obj/cvsm/gcc'
make[2]: *** [stmp-multilib] Error 1
make[2]: Leaving directory `/home/fsirl/obj/cvsm/gcc'
make[1]: *** [bootstrap-lean] Error 2
make[1]: Leaving directory `/home/fsirl/obj/cvsm/gcc'
make: *** [bootstrap-lean] Error 2

Last week cvs-980120 of egcs-mainline built fine with the gas-981127
binutils snapshot, as I reported here on the list.

Franz.