Lubomir Sedlacik wrote:
> On Sun, Dec 03, 2006 at 11:20:13AM +0000, Christian Biere wrote:
> 
>>Module Name:	pkgsrc
>>Committed By:	cbiere
>>Date:		Sun Dec  3 11:20:12 UTC 2006
>>
>>Modified Files:
>>	pkgsrc/converters/libiconv: Makefile
>>
>>Log Message:
>>Added c++ to USE_LANGUAGES because configure (unnecessarily) looks for
>>a working C++ preprocessor and the build breaks if there's a non-working
>>CC in PATH otherwise.
> 
> 
> that's bogus.  why can't you fix configure instead?

That's the fault of libtool, not the configure scripts. In my local test 
environment, I have set

     CONFIGURE_ENV+=   CXXCPP=${CXX}\ -E
     MAKE_ENV+=        CXXCPP=${CXX}\ -E

and now all packages that use libtool fail in the configure stage. 
That's bad, but not our fault. I think there may be cases where programs 
require a C++ preprocessor, so the above settings look right to me.

Does anyone know why libtool always needs a C++ compiler to configure 
itself?

Roland