From: Jeffrey A Law <law@cygnus.com>
To: Manfred.Hollstein@ks.sel.alcatel.de
Cc: Alexandre Oliva <oliva@dcc.unicamp.br>, gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3
Date: Mon, 22 Dec 1997 12:06:00 -0000 [thread overview]
Message-ID: <26361.882821354@hurl.cygnus.com> (raw)
In-Reply-To: <9712110707.AA07283@lts.sel.alcatel.de>
In message < 9712110707.AA07283@lts.sel.alcatel.de >you write:
> Same here:
>
> $ gdb genattr core
> Core was generated by `genattr'.
> Program terminated with signal 11, Segmentation fault.
> #0 0xef7f1d08 in ?? ()
> Breakpoint 1 at 0x8130
> (gdb) bt
> #0 0xef7f1d08 in ?? ()
> #1 0xef7f1c28 in ?? ()
> #2 0xef7f0084 in ?? ()
> #3 0x8180 in memset ()
> #4 0x6368 in __do_global_ctors ()
> #5 0x6390 in __main ()
> #6 0x309c in main ()
>
> Also interesting, cpp built by the stage1 compiler:
>
> $ ./cpp -v -dM
> ld.so: unidentifiable procedure reference at 0x1e2a4
>
> Looks like gcc/egcs on SunOS are seriously broken!
Are we still having this problem?
jeff
next prev parent reply other threads:[~1997-12-22 12:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 12:02 Alexandre Oliva
1997-12-10 23:09 ` Manfred.Hollstein
1997-12-11 3:32 ` Paul Eggert
1997-12-11 1:51 ` Manfred.Hollstein
1997-12-22 12:06 ` Jeffrey A Law [this message]
1997-12-22 22:04 ` Alexandre Oliva
1997-12-26 8:11 ` New problems with gcc-2.8.0 based code [was: Re: cannot bootstrap neither gcc-2.8.0-971206 nor egcs-971207 on sparc-sun-sunos4.1.3 ] Manfred Hollstein
1997-12-27 12:13 ` New problems with gcc-2.8.0 based code - NOW FIXED! Manfred Hollstein
1997-12-28 23:23 ` Richard Stallman
1997-12-29 7:48 ` Jeffrey A Law
1997-12-29 11:17 ` Manfred Hollstein
1997-12-29 10:20 ` Jeffrey A Law
1997-12-30 8:57 ` Manfred Hollstein
1997-12-30 9:47 ` Andi Kleen
1998-01-01 10:02 ` Manfred Hollstein
1997-12-30 11:33 ` Philip Blundell
1997-12-30 13:17 ` Paul Koning
1997-12-29 11:08 ` Manfred Hollstein
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=26361.882821354@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/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).