------- Comment #2 from rob1weld at aol dot com 2009-01-03 19:15 ------- Since this bug is related to the assembler I tried setting the "--with-gnu-as --with-as=" options for configure and while that allowed the build to continue it then went down a path of uncharted waters (and numerous problems with the scripts not creating/copying libtool, not building the 64 directories, etc.).
What I finally ended up doing was this: ../gcc_trunk/configure --enable-languages=ada,c,c++,fortran,java,objc,obj-c++ --enable-multilib --enable-shared --disable-static --enable-decimal-float --enable-nls --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld Note that I set 'as' and 'ld' to the "binutils-2.19" version (it is first in the path). On the Solaris Platform it is common (and recommended) to set "--with-gnu-as --with-as=binutils-as --without-gnu-ld --with-ld=/usr/ccs/bin/ld" when compiling gcc -- since I had not set these configure options the later scripts tooks paths that are untested on this platform (and therefore failed). It would seem that this is a second bug; that the configure script does not have the same effect if it detects options automatically that it would have if the user manually set the configure option to the same value. I should not have to actually set configure options (to their automatically determined (default) value) in order that later scripts will work correctly. I have completed "make install" and now for a little testing. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38693
