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: Thu, 29 Apr 2004 00:55:00 -0000 [thread overview]
Message-ID: <16528.10942.725616.111974@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <1083189407.1072.44.camel@leaf.tuliptree.org>
Jim Wilson writes:
> This is because of confusion between "-o output" and
> "-oldstyle_liblookup" This should be fixable by defining
> SWITCHES_NEED_SPACES to include "o". This changes both gcc.c and
> collect2.c, and they will no longer accept "-ooutput" as valid, which
> should let the Tru64 linker option work.
True, this is even mentioned in the PR. I've just checked that this is
true: ld doesn't understand -otest (instead of -o test). I once had a
hacky patch to let collect2 pass through certain flags (like
-oldstyle_liblookup) unprocessed, but this is much cleaner.
I'll prepare a patch.
Thanks.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
next prev parent reply other threads:[~2004-04-28 22:05 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 [this message]
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=16528.10942.725616.111974@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).