From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: another powerpc --enable-targets=all failure
Date: Fri, 17 Apr 1998 12:01:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.980417135810.17786u-100000@vespucci.advicom.net> (raw)
I thought I would build this one last time to put it to bed even though I
never want to build with --enable-targets=all again. :)
Again this is a one-tree style build with binutils 2.9, egcs-1.0.2, and
newlib-1.8.0
This time powerpc-rtems got well into the newlib part of the build before:
usr1/rtems/work/tools/b-t/gcc/xgcc -B/usr1/rtems/work/tools/b-t/gcc/
-idirafter /usr1/rtems/work/tools/b-t/powerpc-rtems/newlib/targ-include
-idirafter /usr1/rtems/work/tools/src/newlib/libc/include -nostdinc -O2 -g
-mlittle -mrelocatable-lib -mno-eabi -mstrict-align -O2
-DHAVE_GETTIMEOFDAY -DMALLOC_PROVIDED -DEXIT_PROVIDED
-DMISSING_SYSCALL_NAMES -DSIGNAL_PROVIDED -DREENTRANT_SYSCALLS_PROVIDED
-DHAVE_OPENDIR -DHAVE_RENAME -fno-builtin
-I/usr1/rtems/work/tools/b-t/powerpc-rtems/newlib/./targ-include
-I/usr1/rtems/work/tools/src/newlib/./libc/include -c
../../../../../../src/newlib/libc/stdio/wsetup.c
rm -f lib.a
/usr1/rtems/work/tools/b-t/binutils/ar rc lib.a clearerr.o fclose.o
fdopen.o feof.o ferror.o fflush.o fgetc.o fgetpos.o fgets.o fileno.o
findfp.o fiprintf.o flags.o fopen.o fprintf.o fputc.o fputs.o fread.o
freopen.o fscanf.o fseek.o fsetpos.o ftell.o fvwrite.o fwalk.o fwrite.o
getc.o getchar.o gets.o iprintf.o makebuf.o mktemp.o perror.o printf.o
putc.o putchar.o puts.o refill.o remove.o rename.o rewind.o rget.o scanf.o
setbuf.o setvbuf.o siprintf.o sprintf.o sscanf.o stdio.o tmpfile.o
tmpnam.o ungetc.o vfiprintf.o vfprintf.o vfscanf.o vprintf.o vsprintf.o
wbuf.o wsetup.o
gmake[5]: *** [lib.a] Segmentation fault (core dumped)
gmake[5]: *** Deleting file `lib.a'
gmake[5]: Leaving directory
`/usr1/rtems/work/tools/b-t/powerpc-rtems/le/newlib/libc/stdio'
Here is the gdb trace back of the core file:
$ gdb /usr1/rtems/work/tools/b-t/binutils/ar core
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (i386-redhat-linux), Copyright 1996 Free Software Foundation,
Inc...
Core was generated by `/usr1/rtems/work/tools/b-t/binutils/ar rc lib.a
clearerr.o fclose.o fdopen.o fe'.
Program terminated with signal 11, Segmentation fault.
find_solib: Can't read pathname for load map: Input/output error
#0 0x804db17 in _bfd_write_archive_contents (arch=0x81b55a0)
at ../../src/bfd/archive.c:1657
1657 unsigned int remaining = arelt_size (current);
(gdb) bt
#0 0x804db17 in _bfd_write_archive_contents (arch=0x81b55a0)
at ../../src/bfd/archive.c:1657
#1 0x804fefd in bfd_close (abfd=0x81b55a0) at ../../src/bfd/opncls.c:412
#2 0x804b384 in write_archive (iarch=0x8177320) at
../../src/binutils/ar.c:990
#3 0x804b7d2 in replace_members (arch=0x8177320,
files_to_move=0xbfffe76c,
quick=false) at ../../src/binutils/ar.c:1249
#4 0x804ae91 in main (argc=62, argv=0xbfffe760) at
../../src/binutils/ar.c:585
(gdb)
I am going out of town until next Thursday so won't be able to look into
this more until then. Just wanted to pass the report on since it was a
core dump.
Thanks.
--joel
reply other threads:[~1998-04-17 12:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.3.96.980417135810.17786u-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).