From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Karl Vogel <karl.vogel@seagha.com>
Cc: Jim Wilson <wilson@specifixinc.com>, gcc@gcc.gnu.org
Subject: Re: HP/Compaq Tru64 linker semantics
Date: Thu, 29 Apr 2004 21:03:00 -0000 [thread overview]
Message-ID: <16529.18286.362984.801997@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <40904283.8040509@seagha.com>
Karl Vogel writes:
> I did something like:
>
> +Index: gcc/config/alpha/osf.h
> +--- gcc/config/alpha/osf.h.orig 2003-12-12 02:19:23.000000000 +0100
> ++++ gcc/config/alpha/osf.h 2004-04-26 21:25:14.000000000 +0200
> +@@ -79,7 +79,7 @@
> + constructor and call-frame data structures are not accidentally
> + overridden. */
> + #define LINK_SPEC \
> +- "-G 8 %{O*:-O3} %{!O*:-O1} -S %{static:-non_shared} \
> ++ "-oldstyle_liblookup %{!o:-o a.out} -G 8 %{O*:-O3} %{!O*:-O1} -S %{static:-non_shared} \
> + %{!static:%{shared:-shared -hidden_symbol _GLOBAL_*} \
> + %{!shared:-call_shared}} %{pg} %{taso} %{rpath*}"
> +
That's not what I meant: as already stated, I don't think it's appropriate
for gcc to behave differently than the native cc with respect to library
lookup, even if this behavior is unusual compared to other unices.
My patch to allow passing -oldstyle_liblookup through collect2 to ld (but
only as -Wl,-oldstyle_liblookup) is here:
http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01920.html
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
prev parent reply other threads:[~2004-04-29 18:20 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
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 [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=16529.18286.362984.801997@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).