*On Tue Apr 06, 2004 at 10:00:34AM -0400, Richard Sewards (richard.sewards@xxxxxxxxxxxxx) wrote: > I was able to build gcc 3.3.3 on Intel Solaris 8. I configured with: > > --prefix=/usr/local.share/gnu/3.3.3 > --exec-prefix=/usr/local.share/gnu/3.3.3/H-i386-pc-solaris2.8 > --srcdir=/usr/local.share/gnu/src/gcc-3.3.3 > --enable-languages=c,c++,java --with-cpu=i686 --disable-nls > > and compiled with gcc 3.2.2. I did not encounter any compile errors > like yours. What arguments to configure did you use? Well, I'm compiling with gcc 3.1.1 and wonder if there's something different. For arguments, I used the following: setenv CFLAGS `-D_LARGEFILE_SOURCE -march=i686 -O2 -funroll-loops -fexpensive-optimizations setenv BOOT_CFLAGS '-D_LARGEFILE_SOURCE -march=i686 -O2 -funroll-loops -fexpensive-optimizations --prefix=/package/gcc-3.3.3 --disable-nls --enable-shared --with-as=/public/bin/as --with-ld=/public/bin/ld --enable-threads=posix --enable-languages=c,c++,f77 Note, the as and ld are binutils-2.14 versions of as and ld. See http://www.csc.uvic.ca/~cconstan/typescript-3.3.3 for a full log of what I did. > However, I had to abandon the GNU linker (from binutils 2.14) on Intel > Solaris 8 with gcc 3.3.3, so I added: > > --without-gnu-as --with-as=/usr/ccs/bin/as > --without-gnu-ld --with-ld=/usr/ccs/bin/ld I didn't have problems, but I might recompile them. -- Carl B. Constantine University of Victoria Programmer Analyst http://www.csc.uvic.ca UNIX System Administrator Victoria, BC, Canada cconstan@xxxxxxxxxxx ELW A248, 721-8766
