Re: Additional link flags for HP aCC and SGI CC

[Gary V. Vaughan]

Ludovic Courtès wrote:
> Hi again,

Salut!

> 9 days, 4 hours, 35 minutes, 38 seconds ago, 
> Gary V. Vaughan wrote:
> 
>>It does, but the interface to the user doesn't change depending on the
>>host machine.  -Xcompiler and -Xlinker are there so that if we find a
>>missing abstraction, libtool users can continue to work while we figure
>>out how to incorporate a clean abstraction into the user interface.
> 
> However, I think I found a quite good reason to incorporate (more)
> vendor-specific switches knowledge into Libtool (eg. `-AA' et al.).  :-)
> The reason is that those flags are needed at configure time where
> Libtool isn't used and where `-Xcompiler' and `-Xlinker' are potentially
> unknown and may make the compiler fail.

Agreed.  But, remember that I am picky about the level of abstraction...
I certainly won't accept --optimise=2; -Wall is just above the minimum
level for acceptance.  But if you figure out how to do --abi=64bit,threaded
I'll personally buy you a gallon of beer ;-)

> Of course, I could just use the raw CFLAGS/LDFLAGS at configure-time and
> "libtoolize" them (ie. prefix each switch with either `-Xcompiler' or
> `-Xlinker') at the very end of my `configure.ac' file but I find this
> solution inelegant.  That's probably the reason why Libtool already
> knowns the most commonly used vendor specific switches.  What do you
> think?

Sounds reasonable.

Cheers,
        Gary.
-- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature