[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Additional link flags for HP aCC and SGI CC
From: |
Ludovic Courtès |
Subject: |
Re: Additional link flags for HP aCC and SGI CC |
Date: |
Thu, 2 Sep 2004 18:04:44 +0200 |
User-agent: |
Mutt/1.5.4i [Guile enabled] |
Hi again,
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.
Due to lack of time, I haven't been able to hack on Libtool so that it
recognizes new high-level options such as `--warnings=on'.
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.
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?
Thanks!
Ludovic.
- Re: Additional link flags for HP aCC and SGI CC,
Ludovic Courtès <=