On Fri, Oct 31, 2003, Ralf S. Engelschall wrote:
> On Fri, Oct 31, 2003, Michael Schloh wrote:
>
>> [...]
>> Fix build failure when native CPP program is busted or not correctly
>> identified during configure
>> [...]
>> CC="${l_cc}" \
>> + CXX="${l_cxx}" \
>> CFLAGS="-I`pwd`/../zlib-%{V_zlib}" \
>> CPPFLAGS="-I`pwd`/../zlib-%{V_zlib}" \
>> LDFLAGS="-L`pwd`/../zlib-%{V_zlib}" \
>
> Be more careful here: the openpkg.spec is not allowed to use %{l_cxx}
> or the ${l_cxx} variable, because it is not provided by openpkg.boot!
>
Thanks for checking that out. Only now our curl package is not consistent
with the openpkg package. Not nice, but maybe necessary.
> I'll back this out, especially because cURL is C only and does not use
> C++. -- it is a failure of its Autoconf stuff to also search (and on
> some platforms fail) for C++...
>
I partially agree, but I assume that the author might have put the C++ check
in for some reason. It mentions something about this (building cURL's C code
with a C++ compiler) in the cURL docs.
It would be nice to just do CPP="${l_cc} -E" there, but an additional
problem is that the configure script picks up CPP when checking on 'cc', but
not when checking on 'c++'.
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe
Cable & Wireless Telecommunications Services GmbH
pgp00000.pgp
Description: PGP signature
