On Tuesday 16 November 2004 10:09, Owen Cook wrote: > On Tue, 16 Nov 2004, Sandip Bhattacharya wrote: > > > I am a bit out of my depth here, what is your version of gcc > > > > > > Do a gcc -v you will also get the build options > > > > [root at pluto build]# gcc -v > > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.3.3/specs > > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > > --infodir=/usr/share/info --enable-shared --enable-threads=posix > > --disable-checking --disable-libunwind-exceptions --with-system-zlib > > --enable-__cxa_atexit --host=i386-redhat-linux > > Thread model: posix > > gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7) > > I'm surprised it didn't include --enable-languages=c,c++ > > Anyway, not only am I out of my depth, I am starting to drown! > > I would simply build another gcc, say 3.3.2 with the same specs as above > plus --enable-languages=c,c++ in /opt and then try building > the cvs using that gcc ie, make CC=/opt/gcc-3.3.2/bin/gcc > > > or you might want to go up to 3.3.5 I think it is now
I would instead try installing these rpms: http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/gcc34-c++-3.4.0-1.i386.rpm http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/libstdc++34-3.4.0-1.i386.rpm http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/libstdc++34-devel-3.4.0-1.i386.rpm and any other dependencies required. Then, you will have a correctly installed parallel install of GCC 3.4, which won't break your system. Then, before running ./configure, you will need to adjust the default CC and CXX, something like this: peter at linux:~/cvs3/Scribus> export cc="/opt/gcc_34/bin/gcc_34" peter at linux:~/cvs3/Scribus> export gcc="/opt/gcc_34/bin/gcc_34" peter at linux:~/cvs3/Scribus> export CXX="/opt/gcc_34/bin/c++_34" peter at linux:~/cvs3/Scribus> export CC="/opt/gcc_34/bin/gcc_34" This is for GCC-3.4 on Suse 9.1 The exact syntax, will depend on the exact names of the files. Then configure will use these optional compilers. In the case of a stable GCC 3.3.x, it is rare to see an internal compiler failure and should be submitted to bugzilla. It is more typical to find compiler bugs with newer pre-release snapshots. I found one with GCC-40 in the recent CVS, but it was a compiler bug. Hope that helps, Peter
