From: David Edelsohn <dje@watson.ibm.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: pooh@msu.ru, egcs@cygnus.com
Subject: Re: egcs on AIX: native or gnu ld?
Date: Sat, 18 Oct 1997 16:18:00 -0000 [thread overview]
Message-ID: <9710182312.AA32330@rios1.watson.ibm.com> (raw)
In-Reply-To: <199710181927.MAA05506@atrus.synopsys.com>
>>>>> Joe Buck writes:
>> | 5) What about including support of shared libraries with native ld to the
>> | future snapshots of egcs?
Joe> g++ never worked with only a native ld on non-ELF systems. Something
Joe> has to resolve the constructors.
I don't think he meant native-ld alone. I assumed that he meant
collect2+native-ld instead of gnu-ld. Unfortunately, gnu-ld does not work
very well with AIX, particularly newer releases. This is partially due to
the difficult that I have encountered trying to extract the design
documents from IBM's RS/6000 Division to ease Cygnus's engineering effort.
The internal details are not very well documented in AIX's online
documentation.
David
These are my own opinions; I am not speaking as an official representative
of IBM Corporation.
===============================================================================
David Edelsohn T.J. Watson Research Center
dje@watson.ibm.com P.O. Box 218
+1 914 945 4364 (TL 862) Yorktown Heights, NY 10598
next prev parent reply other threads:[~1997-10-18 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-17 3:12 Andrey Slepuhin
1997-10-17 19:31 ` David Edelsohn
1997-10-18 12:56 ` Joe Buck
1997-10-18 16:18 ` David Edelsohn [this message]
1997-10-18 13:24 ` Andrey Slepuhin
1997-10-19 14:52 ` David Edelsohn
1997-10-20 2:42 ` Andrey Slepuhin
1997-10-20 10:49 ` David Edelsohn
1997-10-20 5:58 ` Andrey Slepuhin
1997-10-20 6:51 ` Andrey Slepuhin
1997-10-20 14:37 Mike Stump
1997-10-20 18:12 ` David Edelsohn
1997-10-20 18:12 Mike Stump
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=9710182312.AA32330@rios1.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
--cc=pooh@msu.ru \
/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).