the reason why I tried to force all the settings to 64-bit is because when I tried to compile some of the dependent libraries as 32-bit, they failed. As I recall, the checks for two of them simply would die at the default 32-bit compile. When I specified ABI=64 for these particular ones, all was peachy. gmp-5.1.2 (32bit and 64bit) mpfr-3.1.1 (only 64bit) mpc-1.0.1 (only 64bit) So, when I attempted the latest gcc, it would die because of the conflict between 32bit and these 64bit libraries. So that's when I attempted to force it all as 64bit. I was, however, able to compile gcc-4.0.2, so will now attempt to use that to compile the latest. Though, for gcc-4.0.2 to successfully compile, I did have to use GNU ld. Is it still the recommendation that Sun ld be used, but GNU as on Solaris SPARC? On Fri, Jun 28, 2013 at 10:23 PM, vijay nag <vijunag@xxxxxxxxx> wrote: > If the host tool chain that you are using to compile if by default emits > -m64 you dont have to explicitly specify -m64 in CFLAGS. I recently did a > cross compile of gcc-4.7.2 on build Amd64, host=Amd64 and > target=i686-pc-linux-gnu. Whatever was required for target machine I changed > the config scripts to have cflags=-m32. Some times config scripts outsmarts > you despite you specifying a cross compile and configure scripts will need > change then. > >