Re: Additional link flags for HP aCC and SGI CC

[Gary V. Vaughan]

Peter O'Gorman wrote:
> Albert Chin wrote:
> 
>> On Fri, Sep 03, 2004 at 12:09:19PM +0100, Gary V. Vaughan wrote:
>>>
>>> Besides, you can already do this, but at the moment you have to do it
>>> consciously and say `-Xcompiler -peculiar-flag-for-my-compiler', which
>>> at least forces the user to acknowledge that they are going behind
>>> libtool's back, so it will be hardly surprising to them if libtool gets
>>> confused later on...
>>
>> This doesn't help during ./configure. This is the crux of the problem.
> 
> Yes, I agree, it forces the user to add these flags by editing a
> Makefile.in or .am. Makes me wonder if we could have LT_CFLAGS and
> LT_LDFLAGS (or some such), and have automake use these flags if libtool
> is involved in the compile/link.

I definitely agree that this is a problem that needs to be worked on.

I'm not at all convinced that having libtool pass all flags it doesn't
understand through to the compiler is the best (or even a good) solution.

:-(

What about having LT_INIT add code at the beginning of configure to strip
-Xcompiler from CFLAGS for the duration of the configure tests, but revert
to the passed value before config.status is generated (hence Makefile will
get the libtooly CFLAGS).  There's more hair to it than this, but I think
the problem is analagous to LTLIBOBJs.

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