This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: HP/Compaq Tru64 linker semantics

From: Jim Wilson <wilson at specifixinc dot com>
To: Rainer Orth <ro at TechFak dot Uni-Bielefeld dot DE>
Cc: Karl Vogel <karl dot vogel at seagha dot com>, gcc at gcc dot gnu dot org
Date: 28 Apr 2004 14:56:47 -0700
Subject: Re: HP/Compaq Tru64 linker semantics
References: <6DED3619289CD311BCEB00508B8E133601A68654@nt-server2.antwerp.seagha.com><40900DC4.1080504@specifixinc.com> <yddekq7alfy.fsf@xayide.TechFak.Uni-Bielefeld.DE>

On Wed, 2004-04-28 at 13:37, Rainer Orth wrote:
> One caveat, though: currently one cannot pass -oldstyle_liblookup through
> collect2 to ld, which is quite tedious.  This has been reported already

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.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

Follow-Ups:
- Re: HP/Compaq Tru64 linker semantics
  - From: Rainer Orth

References:
- HP/Compaq Tru64 linker semantics
  - From: Karl Vogel
- Re: HP/Compaq Tru64 linker semantics
  - From: Jim Wilson
- Re: HP/Compaq Tru64 linker semantics
  - From: Rainer Orth

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]