From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.11
Date: Tue, 05 Apr 2016 05:54:00 -0000 [thread overview]
Message-ID: <5703531D.9070004@maxrnd.com> (raw)
In-Reply-To: <announce.5702DCA7.60605@cygwin.com>
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
/oss/src/winsup/utils/cygwin-console-helper.cc
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.
..mark
--
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
next prev parent reply other threads:[~2016-04-05 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 21:31 Yaakov Selkowitz
2016-04-05 5:54 ` Mark Geisert [this message]
2016-04-05 6:24 ` Yaakov Selkowitz
2016-04-05 6:42 ` Mark Geisert
2016-04-05 7:18 ` Mark Geisert
2016-04-05 9:57 ` Corinna Vinschen
2016-04-05 17:07 ` Mark Geisert
2016-04-05 7:51 ` Ismail Donmez
2016-04-05 8:32 ` Corinna Vinschen
2016-04-05 8:07 ` Thorsten Kampe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5703531D.9070004@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).