From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Jim Wilson <wilson@specifixinc.com>
Cc: Karl Vogel <karl.vogel@seagha.com>, gcc@gcc.gnu.org
Subject: Re: HP/Compaq Tru64 linker semantics
Date: Wed, 28 Apr 2004 22:40:00 -0000 [thread overview]
Message-ID: <yddekq7alfy.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Jim Wilson's message of "Wed, 28 Apr 2004 13:02:12 -0700"
Jim Wilson <wilson@specifixinc.com> writes:
> Karl Vogel wrote:
> > I was wondering what the general opinion is.. follow GNU ld as close as
> > possible? Or follow the standard way of the platform?!
>
> I would suggest that we should follow what the platform does. People
> porting to Tru64 will expect gcc to work the same way as the native
> compiler, and if it doesn't, then packages with builtin Tru64
> assumptions may fail.
Fully agreed, even though this case of local vs. vendor supplied libdb has
bitten me as well. Even though this default (searching for all shared
libraries before the static ones) is highly unusual on Unix systems, we
should follow the vendor here so GCC users don't get another surprise when
using GCC.
One caveat, though: currently one cannot pass -oldstyle_liblookup through
collect2 to ld, which is quite tedious. This has been reported already
http://gcc.gnu.org/ml/gcc-bugs/1999-09n/msg00912.html
and there's a PR for this, other/1963, but it is unfixed an has been
(erroneously, I think) been closed as a duplicate of PR other/5762.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2004-04-28 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 16:59 Karl Vogel
2004-04-28 21:56 ` Jim Wilson
2004-04-28 22:40 ` Rainer Orth [this message]
2004-04-28 22:43 ` Andrew Pinski
2004-04-28 23:47 ` Rainer Orth
2004-04-29 0:49 ` Jim Wilson
2004-04-29 0:55 ` Rainer Orth
2004-04-29 4:07 ` Karl Vogel
2004-04-29 21:03 ` Rainer Orth
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=yddekq7alfy.fsf@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=gcc@gcc.gnu.org \
--cc=karl.vogel@seagha.com \
--cc=wilson@specifixinc.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).