[Insight-users] Installation build errors : gcc 3.2 ok

[Luis Ibanez]

Hi Neil,

ITK do compile cleanly with gcc 3.1
It also compiles without problem with gcc 3.2

There is a nightly build on gcc3.2 on the dashboard.

The typical problems we have found with these
compilers are

1) inconsistent installation (e.g. mixing
    libraries between the different versions
    of the compiler).

2) inconsistent setup of the CC and CXX
    environment variables. Before you run
    CMake you have to make sure that CXX
    points to the g++ executable and CC
    points to the gcc executable of the
    corresponding version. (CC should not
    point to g++).


-------

Below are the safe options for building gcc3.2
and get a consistent installation:

configure --prefix=/usr/local
           --enable-shared
           --enable-threads
           --enable-languages=c,c++,f77
           --enable-version-specific-runtime-libs

------

If you lack administrator rights, you can build gcc
in your own account as a stands alone application.
Just select --prefix=$HOME/mygcc.

At the current price of hard disks it is not worth
to waste programmers time with a badly installed
compiler. You can build gcc 3.2 correctly in about
one hour, fill up some megabytes in your account,
and get rid of the problem altogether.

At this point it seems to be reasonable to start
dropping gcc 2.95~2.96 and migrate to 3.1 or 3.2.
New Linux distributions are being shipped with
gcc 3.2 anyways.



Please let us know if you find any further problems.


   Thanks


     Luis


==========================================

Neil Killeen wrote:
>>>2) Linking error
>>>
>>>  having now built the library trees ok, the build then failed
>>>once we started linking.  Viz.
>>>
>>>
> 
> i have resolved this linking problem.  it was to do with
> a new libstdc++ in our system that is incompatible
> with gcc 2.95.3
> 
> we also have gcc 3.1.1 with which the new libstdc++ is
> compatible.  However, itk does not compile with
> gcc 3.1.1 failing in template instantiation (didn't investigate
> further).
> 
> so i forced linking with the old libstdc++ and it was ok.
> 
> regards
> Neil
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-users
> 
>