From: David C. <wr...@mo...> - 2008-03-21 04:17:31
|
NightStrike wrote: > No, it's just not setup right. The msys.bat file configures a system > properly based on if you're 64-bit windows or 32-bit windows. So > start your shell with that instead of starting sh.exe directly. You > can use the --norxvt option to msys.bat to use a normal windows > console window instead of rxvt. OK, I'm using msys. I've figured out how to change the path there. I went to gmp and ran "./configure --host=x86_64-pc-mingw32" and then came across an error. While configure is running, it checks to see if it can find a working compiler. It failed and said to check the log file. When I looked in the log file, I came across this: configure:3851: checking compiler x86_64-pc-mingw32-gcc -O2 -m64 Test compile: configure:3865: x86_64-pc-mingw32-gcc -O2 -m64 conftest.c >&5 conftest.c: In function 'main': conftest.c:2: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. configure:3868: $? = 1 failed program was: int main () { return 0; } configure:4874: result: no Now, I tried to compile that same program on my own like: x86_64-pc-mingw32-gcc -o test.exe test.c And it worked fine. But, when I tried it the way the config file tried it: x86_64-pc-mingw32-gcc -O2 -m64 test.c It failed, just like it did for the script. Any ideas on what might be going wrong here? It fails whether or not I use rxvt, so that shouldn't be an issue. |