Sergio Rojas wrote: > OK. I am using the flag -m64 to have everything compiled > with the same options, so one could make use of the processor > 64 bit computational capabilities. In general setting CFLAGS=-m64 is a terrible idea because that disables all optimizations! Remember, you only get the default "-g -O2" setting of CFLAGS if you don't override it, and the compiler only optimizes when -O is specified. So what you probably want is CFLAGS="-m64 -g -O2". For this reason it's traditional when doing this to set it in $CC instead, e.g. CC="gcc -m64", and leave CFLAGS untouched. In the specific case of bootstrapping gcc however, everything's a little more complicated. I think that you would have to override both CFLAGS and BOOT_CFLAGS, and setting -m64 in CC wouldn't work as that would only apply to the stage1. > checking for i386-pc-solaris2.10-gcc... > /home/srojas/MySoftware/my_install/./gcc/xgcc > -B/home/srojas/MySoftware/my_install/./gcc/ > -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/bin/ > -B/home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/lib/ -isystem > /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/include -isystem > /home/srojas/My_prog/GCC4_32bit/i386-pc-solaris2.10/sys-include > checking for suffix of object files... configure: error: cannot > compute suffix of object files: cannot compile > See `config.log' for more details. Well, what does config.log say? Note that you need to look in the correct one, corresponding to the dir where it was running configure when the error occured. The usual cause of this error (if this is in libgcc/) is that the loader can't find the gmp/mpfr libraries when trying to exec cc1 for the first time, which happens if you installed shared libraries outside of the system default paths and didn't add the location to LD_LIBRARY_PATH. (There should have been a message about this when you ran "make install" for gmp and mpfr.) Brian
