Mark Geisert mark@maxrnd.com
Tue Apr 5 05:54:00 GMT 2016

I am running into a problem building Cygwin 2.5.0-0.11 from source on Windows 7 
64-bit.  This is not new with the latest test release but I believe it is new 
with 2.5.0 over 2.4.1.

When building in winsup/utils, I hit this:

c++wrap -pipe -march=haswell -fno-exceptions -fno-rtti -O2 -g -fno-rtti 
-fno-exceptions -fno-use-cxa-atexit -Wall -Wstrict-aliasing -Wwrite-strings 
-fno-common -pipe -fbuiltin -fmessage-length=0 -c -o cygwin-console-helper.o 
i686-w64-mingw32-g++  -o cygwin-console-helper.exe cygwin-console-helper.o -static
cygwin-console-helper.o: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
Makefile:153: recipe for target 'cygwin-console-helper.exe' failed
make[3]: *** [cygwin-console-helper.exe] Error 1
make[3]: Leaving directory '/oss/build/x86_64-unknown-cygwin/winsup/utils'
Makefile:83: recipe for target 'utils' failed
make[2]: *** [utils] Error 1
make[2]: Leaving directory '/oss/build/x86_64-unknown-cygwin/winsup'
Makefile:8947: recipe for target 'all-target-winsup' failed
make[1]: *** [all-target-winsup] Error 2
make[1]: Leaving directory '/oss/build'
Makefile:853: recipe for target 'all' failed
make: *** [all] Error 2

I found that the generated winsup/utils/Makefile has
MINGW_CXX      := i686-w64-mingw32-g++
even though I am building on 64-bit.

I'm not deeply familiar with autoconf but something about the configuring seems 
wrong.  configure.ac checks for the existence of ${target_cpu}-w64-mingw32-g++ 
but config.status shows target_cpu isn't initialized until after MINGW_CXX is 
initialized.  I have compilers for both arches installed, if that matters.


Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list