On Thu, 19 Jan 2012, Ludovic Court�s wrote:
> It turns out that ICC manages to build a working GCC plug-in, so after
I would say there is some conceptual confusion here (based on this
sentence, without having looked at the autoconf macros you refer to).
Logically there are two or three differe
Dave Korn skrev 2012-01-20 01:15:
*snip*
>That could be tricky because I guess you won't be able to use
> libtool at configure time.
*snip*
It's possible to use libtool at configure time, but you need to invoke
LT_OUTPUT before you do so. Or is there a reason for that not to work
i
On 19/01/2012 16:51, Ludovic Courtès wrote:
> Right. But how would you write feature tests that would check (1)
> whether the GNU C language is supported,
Try and compile a conftest that uses it. If you wanted a possibly
over-engineered solution, write one conftest for each feature of GNU C
.org] On Behalf Of Ludovic
Courtès
Sent: Thursday, January 19, 2012 11:52 AM
To: Paul Eggert
Cc: g...@gcc.gnu.org; bug-autoconf@gnu.org
Subject: Re: Dealing with compilers that pretend to be GCC
Hi Paul,
Paul Eggert skribis:
> A 'configure' script is supposed to check for behavio
Hi Paul,
Paul Eggert skribis:
> A 'configure' script is supposed to check for behavior, not identity.
> If the compiler supports the features needed, then generally speaking
> a 'configure' script shouldn't care whether the compiler is truly GCC.
Right. But how would you write feature tests th
On 01/19/12 06:24, Ludovic Courtès wrote:
> I don’t see what can be done on “our” side (perhaps Autoconf’s feature
> test could be strengthened, but how?)
Which feature test would that be?
I certainly understand the problem, and have run into issues where
clang fools 'configure' into thinking a G
Hello,
A number of compilers claim to be GCC, without actually being GCC. This
has come to a point where they can hardly be distinguished–until one
actually tries to use them.
I had the following macro to determine whether plug-in support is
available:
https://gforge.inria.fr/scm/viewvc.php/
