minaust
29th July 2014, 10:39
Hi everybody!
By reading various threads here and simply entering ./configure --help, I was cranking out 32-bit builds for myself and friends, CPU optimized. But I never saw a need for a 64-bit build.
My build environment: A working compiler-free msys environment acquired by running mingw-get and unchecking all the compilers. I then go to Komisar's site and download the latest mingw and appropriate libpack. Unzip and drop them into my mingw folder, and I'm off to the races. I've done 64-bit builds of my own personal-use utils. Here's what I tried:
./configure --extra-cflags="-march=bdver2" --disable-gpac --enable-strip
Works great for 32-bit. But
./configure --cross-prefix=x86_64-w64-mingw32- --host=x86_64-pc-mingw32
gets me the error message "no working c compiler found".
Is there a problem with my configure options, or is my build environment borked? :confused:
By reading various threads here and simply entering ./configure --help, I was cranking out 32-bit builds for myself and friends, CPU optimized. But I never saw a need for a 64-bit build.
My build environment: A working compiler-free msys environment acquired by running mingw-get and unchecking all the compilers. I then go to Komisar's site and download the latest mingw and appropriate libpack. Unzip and drop them into my mingw folder, and I'm off to the races. I've done 64-bit builds of my own personal-use utils. Here's what I tried:
./configure --extra-cflags="-march=bdver2" --disable-gpac --enable-strip
Works great for 32-bit. But
./configure --cross-prefix=x86_64-w64-mingw32- --host=x86_64-pc-mingw32
gets me the error message "no working c compiler found".
Is there a problem with my configure options, or is my build environment borked? :confused: