TIFF and LibTiff Mail List Archive


2013.03.09 21:47 "[Tiff] configuring without C++", by lazer100
2013.03.10 02:11 "Re: [Tiff] configuring without C++", by Bob Friesenhahn

2013.03.10 02:11 "Re: [Tiff] configuring without C++", by Bob Friesenhahn

Libtiff is now configured for i686-pc-linux-gnu

  Installation directory:             /usr/local
  Documentation directory:            ${prefix}/share/doc/tiff-4.0.3

  C compiler: gcc -g -O2 -Wall -W
  C++ compiler: g++
  C++ support: no

the configure is clearly testing out g++, it shouldnt be doing this as I have quite deliberately opted out of C++

this causes a problem on another more obscure system, where I am using a cross compiler

where C++ isnt fully implemented, and the configure fails there.

but I have isolated the problem to Ubuntu as this is a more mainstream system,

I dont know if the configure can be debugged to completely skip anything remotely related to C++, as I quite specifically only want the C side of libtiff

These checks are coming from libtool, which is used by the libtiff build, and provides part of the configure script. It might be possible to mask this out but it would require a new release.

I just checked and

  ./configure CXX=no --enable-cxx=no

successfully built libtiff without its C++ library component and configure did not quit due to not liking a random C++ compiler that it found. Notice that I added 'CXX=no' to the configure command line.

the output should not tell me what the C++ compiler is, as this is a not relevant.

if I go into a shop and say I only want to buy a wheelbarrow, I dont want to be

told that the paint they sell is by Dulux, as this is not relevant to buying a wheelbarrow.

but maybe I have misunderstood the meaning of --enable-cxx=no

Thank you for the entertaining analogy.

Bob Friesenhahn,
GraphicsMagick Maintainer,