[Openexr-devel] Trying to compile 1.1.0 with 2.95.3 compiler, unsuccessfully

[Thad Beier]

In the wonderful world of C++ (pronounced, of course, C-double-cross) 
you have
to always be extremely careful about which version of the compiler you 
are using,
as they have different ways of mangling programs.  Or something.  I 
don't know how
people do it.

Anyway.

I was attempting to compile the OpenEXR Shake plugin, and have 
successfully compiled
the 1.0.7 version with the 2.95.3 version of g++ (by creating a image of 
my development
environment, installing 2.95.3, and chroot-ing to that environment.  How 
do other people
do it?)

This works, and the plugin works.

But, if I wanted to read and write modern, tiled OpenEXR files, I'd have 
to have the 1.1.0
version of the library.  When I try to compile it with the 2.95.3 
compiler, I get a rather
voluminous set of error messages, apparently starting with

   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h: 
In function `static Int64 * __c
   opy_dispatch<const long long unsigned int *,long long unsigned int 
*,__true_type>::copy(const Int64 *, const Int64 *, Int
   64 *)':
   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h:177: 
template instantiation dept
   h exceeds maximum of 17
   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h:177:  
(use -ftemplate-depth-NN t
   o increase the maximum)
   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h:177:   
instantiating `__copy_tri
   vial<Int64>(const Int64 *, const Int64 *, Int64 *)'
   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h:177:   
instantiated from `__copy
   _dispatch<const long long unsigned int *,long long unsigned int 
*,__true_type>::copy(const Int64 *, const Int64 *, Int64
   *)'
   
/usr/local/lib/gcc-lib/i686-pc-linux-gnu/2.95.3/../../../../include/g++-3/stl_algobase.h:188:   
instantiated from `copy<c
   onst Int64 *, Int64 *>(const Int64 *, const Int64 *, Int64 *)'




I'm assuming that all the messages about

   ImfTiledInputFile.cpp: In method `void 
Imf::TiledInputFile::readTile(int, int, int, int)':
   ImfTiledInputFile.cpp:640: warning: choosing 
`Imf::Array<char>::operator char *()' over `Imf::Array<char>::operator const
char *() const'

are an inside joke that I'm just late to be clued in about.

Don't get me wrong -- I love OpenEXR, I love the PIZ wavelet 
compression, I love HDR.  I just hate C++.

Thad Beier
Hammerhead Productions