From: "J. Kean Johnston" <jkj@sco.com>
To: Robert Lipe <robertl@dgii.com>
Cc: Bill Walker <bw@student.ecok.edu>, egcs@cygnus.com
Subject: Re: SCO experiences
Date: Fri, 03 Oct 1997 12:53:00 -0000 [thread overview]
Message-ID: <Pine.SCO.3.96.971003125337.10855C-100000@hyperion.pdev.sco.com> (raw)
In-Reply-To: <19971003093725.13937@dgii.com>
On Fri, 3 Oct 1997, Robert Lipe wrote:
> Stripping .o's before handing them to the linker can't be a good plan.
> It's not actually gcc that drops core. It's ld/collect2. Stick a
> debugger in it and see if you can give better hints.
I believe this is incorrect. The SCO linker dumps core and collect2
simply reports the failure. If you use the GCC 2.8 snapshots (which
dont use collect2 on SCO) the same problem will occur. Even the native
compiler does a nasty like this sometimes. It is the linker at fault
not egcs.
JKJ
next prev parent reply other threads:[~1997-10-03 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-03 5:54 Bill Walker
1997-10-03 7:38 ` Robert Lipe
1997-10-03 12:53 ` J. Kean Johnston [this message]
1997-10-03 12:14 ` Horst von Brand
1997-10-03 12:51 ` J. Kean Johnston
[not found] <m0xH7GY-0000NWC.cygnus.egcs@student.ecok.edu>
1997-10-03 8:11 ` Jason Merrill
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.SCO.3.96.971003125337.10855C-100000@hyperion.pdev.sco.com \
--to=jkj@sco.com \
--cc=bw@student.ecok.edu \
--cc=egcs@cygnus.com \
--cc=robertl@dgii.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).