[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in checking for C++ preprocessor

From: Bob Friesenhahn
Subject: Re: Bug in checking for C++ preprocessor
Date: Thu, 17 Apr 2003 08:48:27 -0500 (CDT)

On Thu, 17 Apr 2003, Philipp Thomas wrote:

> With libtool 1.5 and autoconf 2.57 (haven't tried older versions of
> autoconf) the libtool checks fail if no C++ compiler is installed.

I have in fact already seen a case where the C++ compiler/preprocessor
failed Autoconf's sanity checks, causing configure to abort, even
though the user was not using C++.  The Autoconf default is to abort
if the tested compiler fails its sanity checks.  This is not good for
libtool, since with libtool 1.5, you would usually prefer that the
associated tag be discarded (with a warning), and the configuration
continue to completion.


> Which in it's current state makes libtool unusable for any environment
> where no C++ compiler is installed.
> I rather think it's a bug in autoconfs c.m4, as libtool calls AC_PROG_CXXCPP
> which in turn requires AC_PROG_CXX but doesn't check if the latter actually
> found a C++ compiler and thus fails because no C++ preprocessor is found.
> In our case it fails as it finds the /lib/cpp (symlink kept for
> compatibility reasons) but cpp then of course fails because it can't find
> cc1plus.
> So in it's current form libtool isn't useable for us.
> Philipp
> --
> Philipp Thomas <address@hidden>
> SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nuremberg, Germany
> _______________________________________________
> Bug-libtool mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-libtool

Bob Friesenhahn

reply via email to

[Prev in Thread] Current Thread [Next in Thread]