From: eric@aib.com (Eric Youngdale)
To: hjl@nynexst.com
Cc: neal@ctd.comsat.com, ian@cygnus.com, raeburn@cygnus.com, gas2@cygnus.com
Subject: Re: Bad crt files
Date: Wed, 12 Oct 1994 07:34:00 -0000 [thread overview]
Message-ID: <m0qv4iH-00028rC@dgisv.aib.com> (raw)
In-Reply-To: <9410120341.AA13720@titanic.nynexst.com>
>BTW, Ian, how compatible is the GNU ELF ld with SVR4/x86 ld? Can it
>be a dropin replacement? Has anyone tried to use the GNU ELF ld to
>build a shared ELF library under SVR4/x86?
Yes, I used to do this all the time at my old job. I intended it
to be a drop in replacement, but the handling of the SHT_DYNSYM sections
in our version of SVr4 was a bit weird, and Solaris treated things more
logically. That being said, a little work might be needed on some flavors of
SVr4 to support a unified symbol table which the Dell SVr4 seemed to want.
This could be a linker option, I think.
-Eric
next prev parent reply other threads:[~1994-10-12 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m0quqzC-00034LC@neal.ctd.comsat.com>
1994-10-11 23:11 ` H.J. Lu
1994-10-12 7:34 ` Eric Youngdale [this message]
1994-10-12 22:18 ` GNU ld, ELF and C++ H.J. Lu
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=m0qv4iH-00028rC@dgisv.aib.com \
--to=eric@aib.com \
--cc=gas2@cygnus.com \
--cc=hjl@nynexst.com \
--cc=ian@cygnus.com \
--cc=neal@ctd.comsat.com \
--cc=raeburn@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).