From: Robert Lipe <robertl@dgii.com>
To: Jim Wilson <wilson@cygnus.com>
Cc: egcs@cygnus.com
Subject: -belf Re: directory names in linker
Date: Sun, 29 Mar 1998 05:14:00 -0000 [thread overview]
Message-ID: <19980327222920.28457@dgii.com> (raw)
In-Reply-To: <199803262158.NAA08788@rtl.cygnus.com>
> I don't know what you are talking about, but -belf has never done what you
> think it does, and this has nothing to do with EGCS vs gcc. Please see
> the gcc documentation.
I was mystified, too. I was going to pipe up, but since he didn't bother
to name the host or target, I didn't bother to comment.
> It would be possible to build a copy of gcc where -belf did something useful,
> but that would require doing a lot of stuff by hand. Perhaps someone once
> distributed a binary package for gcc that was hand constructed in such a way
> that -belf worked. However, you can't expect -belf to work for a compiler that
For SCO OpenServer, some dude did indeed distribute a wildly popular (a couple
of tens of thousands distributed via download and CD) version of gcc that did
support '-belf', just like the OpenServer native compiler did.
I can't remember who that dude was, but I have it on Good Authority that
it was actually based on a Cygnus progressive tree becuase that's what
the dude happened to have. :-)
In fact, for this target, it's even explictly mentioned in the EGCS doc:
http://egcs-www.cygnus.com/install/specific.html
with some additional info in the SCO prgrammer FAQ at
http://www.dgii.com/cgi-bin/scoprgfaq/faq.pl
RJL
prev parent reply other threads:[~1998-03-29 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-21 13:50 Ruslan Shevchenko
1998-03-24 13:00 ` Jim Wilson
1998-03-24 14:49 ` Ruslan Shevchenko
1998-03-26 21:49 ` Jim Wilson
1998-03-29 5:14 ` Robert Lipe [this message]
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=19980327222920.28457@dgii.com \
--to=robertl@dgii.com \
--cc=egcs@cygnus.com \
--cc=wilson@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).