[Insight-users] compilation error with g++-4.0

[Luis Ibanez]

Hi Amadeus,



We certainly intend to support GCC 4.0 as well as any
other future releases of GCC.


However is still too early for us to use that compiler.
For example, there are not yet Debian packages for it.



The release 4.0.1 was just made on July 7th

           http://gcc.gnu.org/gcc-4.0/


In order to use it know we would have to build the
compiler...  however their own Dashboard doesn't look
too clean at this point:

        http://gcc.gnu.org/gcc-4.0/buildstat.html

Most of their builds are failing today. So, it seems to be
prudent to give GCC 4.0 a bit more of cocking time before
changing ITK in order to support the new GCC.



If you want to help in the process of porting ITK to
GCC 4.0 the way to go is to enable in your machine
a Nightly build.

In that way we could follow the Evolution of the
software as we adapt it to Gcc 4.0.

For instructions on how to setup a Nightly build
please look at the Wiki page:

   http://www.cmake.org/Wiki/CMake_Testing_With_CTest




    Regards,


       Luis




------------------------
Amadeus W. M. wrote:

> 
> However, I'm having major troubles compiling ITK with g++-4.0. On the
> first attempt I got this error message:
> 
> Dunno abot this gcc.
> 
> So I did a grep on this string, and I found it in 
> InsightToolkit-2.0.1/Utilities/vxl/vcl/vcl_compiler.h on line 79. So I
> see the gcc versions supported so far go up to gcc-3.x. I even made
> another elif clause:
> 
> #elif (__GNUC__==4)
> # define VCL_GCC_40
> ...
> 
> but the code that gets compiled this way has incompatibilities from the
> C++ standard, too many for me to fix. For instance, it uses
> std::select1st to select the first element in a std::pair. With g++-4.0,
> select1st is not in std (which is correct), but it is a gnu extension.
> 
> So for now, I configured ITK to compile with g++3.2 and so far so good
> (it's still compiling as we speak). 
> 
> Are there any plans to support g++-4.0? This is the compiler that comes
> closest to the standard. 
> 
> Thsnks!
> 
> 
> 
> 
>