[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with Sun Studio 12 C++
From: |
Ralf Wildenhues |
Subject: |
Re: Problem with Sun Studio 12 C++ |
Date: |
Sun, 7 Jun 2009 07:06:58 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Eric Blake wrote on Sat, Jun 06, 2009 at 08:42:38PM CEST:
> >From 5f22e075cbae3331ed1d7ed56d4ed63117238425 Mon Sep 17 00:00:00 2001
> From: Eric Blake <address@hidden>
> Date: Sat, 6 Jun 2009 11:24:26 -0600
> Subject: [PATCH] Avoid ambiguous fallback in AC_PROG_CXX, AC_PROG_OBJC.
>
> * lib/autoconf/c.m4 (AC_PROG_CXX, AC_PROG_OBJC): Use 'no', rather
> than an ambiguous compiler name, when no compiler is present.
> Reported by Ralf Wildenhues and others.
This would be different from AC_PROG_{F77,FC} which both do not set
their variables when the compiler isn't found, and from AC_PROG_CC,
which AC_MSG_FAILUREs when no C compiler isn't found. Also, the change
does not take into account that the macros may use the compiler name for
subsequent tests: whether this is the GNU compiler, and if the first
compiler macro, the values of OBJEXT and EXEEXT. Calling a program
named 'no' for that purpose is not an improvement.
I don't have any idea for the CC on w32 issue, however.
Cheers,
Ralf