Re: [Re: [gtkmm] gcc-3.3 and gtkmm-2.2.1]

[Carl Nygard <cjnygard fast net>]

On Sun, 2003-05-18 at 12:17, Paul Davis wrote:
> >I fixed the problem for myself by installing GCC 3.2 again and forcing
> >the g++ symlink to point to g++-3.2 instead of g++-3.3. It's quite a
> >dirty hack, though. Else I don't quite know what to do. Perhaps the
> 
> just for anyone who cares:
> 
> #!/bin/bash
> 
> progs="c++  c++filt  cpp  gcc  gcov  i686-pc-linux-gnu-gcc  protoize  unprotoize
> "
> 
> case $1 in 
>     2) dir=/usr/gcc2/bin ;;
>     3) dir=/usr/gcc3/bin ;;
> esac
> 
> for prog in $progs
> do
>     rm -f /usr/bin/$prog
>     ln -s $dir/$prog /usr/bin
> done
> 
> exit 0;


Wouldn't this be simpler??:

export PATH=/usr/gcc2/bin:$PATH

Normally if I have to have multiple compilers, I'll install in
/opt/gcc-X.x and manipulate the path when I need to.

-- 
Carl Nygard <cjnygard fast net>