niXman <i.nixman@xxxxxxxxx> writes: > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-directory > . > > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-directory > -m32 > . > > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-directory > -m64 > 64 > > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-os-directory > ../lib > > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-os-directory > -m32 > ../lib > > $ /home/niXman/mingw-build/gcc-4.6.3/./gcc/xgcc > -B/home/niXman/mingw-build/gcc-4.6.3/./gcc/ --print-multi-os-directory > -m64 > ../lib64 Thanks, that all looks right also. >> The question you are asking is basically why that xgcc command did not >> find the 64-bit crt file. As a first step, I'm trying to verify that it >> is configured to look in the expected directory. That is, that it is >> configured such that -m64 causes it to append ../lib64 to the -B and -L >> paths that are passed to it. >> >> Can you confirm that the 64-bit crt file is in one of those directory, >> e.g., /home/niXman/mb-0.8/../mingw-x32/i686-w64-mingw32/lib/../lib64 ? > > Yes. In /home/niXman/mb-0.8/../mingw-x32/i686-w64-mingw32/lib64 I want to inject a note of caution that in the presence of symlinks that is not necessarily the same as what I asked. Although I admit that it almost certainly is. I assume you can run the failing command yourself and see the failure. Can you run that command with -v and send us the complete output? Thanks. Ian
