[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Don't use linker_flags when running CC
From: |
Boehne, Robert |
Subject: |
RE: Don't use linker_flags when running CC |
Date: |
Wed, 19 Feb 2003 09:32:50 -0600 |
Peter,
By design, linker_flags should be passed to the linker,
compiler_flags (which may be there for linking) should be passed
to the compiler driver even when linking.
I use LDFLAGS='-Wl,-bbigtoc' for everything I do under AIX,
and it links with xlC or g++ and the flag does get passed. If that
doesn't work for Darwin, it should, and that problem should be fixed.
I'm guessing it works properly though.
Alexandre, I think you should check this in, you've got my approval.
Thanks,
Robert
-----Original Message-----
From: Peter O'Gorman [mailto:address@hidden
Sent: Wednesday, February 19, 2003 6:54 AM
To: Alexandre Oliva
Cc: address@hidden
Subject: Re: Don't use linker_flags when running CC
On Wednesday, February 19, 2003, at 04:18 PM, Alexandre Oliva wrote:
> I ran into a problem in the old snapshot of libtool 1.5- used by GCC
> on Solaris that was caused by our mis-use of $linker_flags as an
> argument to $CC. This patch fixes all occurrences of the problem I
> could find in libtool mainline. Ok to install?
>
So what exactly was the problem on solaris which prompts you to modify
darwin archive_cmds?
Aren't all the linker_flags quoted and ${wl}'d ? Thus allowing them to
be passed as arguments to $CC?
Sorry, this patch seems unlikely to have been tested on all the
platforms which it applies to, so I'd like to know what the problem is
that you are fixing.
Peter
_______________________________________________
Libtool-patches mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/libtool-patches