From: Joe Buck <jbuck@synopsys.com>
To: dje@watson.ibm.com (David Edelsohn)
Cc: pooh@msu.ru, egcs@cygnus.com
Subject: Re: egcs on AIX: native or gnu ld?
Date: Sat, 18 Oct 1997 12:56:00 -0000 [thread overview]
Message-ID: <199710181927.MAA05506@atrus.synopsys.com> (raw)
In-Reply-To: <9710172147.AA20954@rios1.watson.ibm.com>
> Most of your questions deal with G++ implementation issues which I
> cannot address. I really do not know how -frepo works or about additional
> files it creates and how linkers other than GNU ld are suppose to handle
> them.
-frepo is handled by the collect2 program, which then calls either the
GNU or the "native" linker.
> It sounds like at least some of the features of G++ are relying
> upon GNU ld or SVR4/ELF-like linkers.
No, the collect program handles the constructor problems on other systems.
See the g++ FAQ for a discussion ( http://www.cygnus.com/misc/g++FAQ_toc.html ).
It may not be able to deal with global constructors in shared libraries,
though.
> | 5) What about including support of shared libraries with native ld to the
> | future snapshots of egcs?
g++ never worked with only a native ld on non-ELF systems. Something
has to resolve the constructors.
If, for a particular platform other than ELF, there is a way to make
shared libraries work with the native linker, and someone wants to
contribute it, fine, but it shouldn't be a priority when the workaround
"use the GNU linker" exists.
next prev parent reply other threads:[~1997-10-18 12:56 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 [this message]
1997-10-18 16:18 ` David Edelsohn
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=199710181927.MAA05506@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=dje@watson.ibm.com \
--cc=egcs@cygnus.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).