From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: [PATCH 2/2] Default to x86_64 build on non-Cygwin hosts
Date: Sat, 3 Dec 2022 17:14:07 +0100 [thread overview]
Message-ID: <20221203161407.2337644-2-corinna-cygwin@cygwin.com> (raw)
In-Reply-To: <20221203161407.2337644-1-corinna-cygwin@cygwin.com>
From: Corinna Vinschen <corinna@vinschen.de>
Given x86 has been deprecated, we only have a single target for
the time being. Default to this target for now, basically to
safe my lazy ass when building on Linux.
Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
---
NEWS | 3 +++
lib/compilers.cygpart | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 976237d88d54..e3dc83c3f5a4 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,6 @@
+0.35.5:
+ * Default to x86_64-pc-cygwin target on Linux.
+
0.35.4:
* Replace 'egrep' with 'grep -E' throughout
* xorg: Default LICENSE to 'MIT'
diff --git a/lib/compilers.cygpart b/lib/compilers.cygpart
index f9b8c69532e2..35e6fe2886f9 100644
--- a/lib/compilers.cygpart
+++ b/lib/compilers.cygpart
@@ -213,7 +213,7 @@ case ${CBUILD} in
# https://sourceware.org/legacy-ml/cygwin-developers/2013-02/msg00132.html
x86_64-unknown-cygwin) CBUILD="x86_64-pc-cygwin" ;&
*-cygwin) CHOST="${_host_arch:-${CBUILD%%-*}}-pc-cygwin" ;;
-*) defined _host_arch || error "Either --32 or --64 flags MUST be passed to cygport"
+*) defined _host_arch || _host_arch="x86_64"
CHOST="${_host_arch}-pc-cygwin" ;;
esac
unset _host_arch
--
2.38.1
next prev parent reply other threads:[~2022-12-03 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 16:14 [PATCH 1/2] Filter newlines from BUILD_REQUIRES Corinna Vinschen
2022-12-03 16:14 ` Corinna Vinschen [this message]
2022-12-03 18:08 ` [PATCH 2/2] Default to x86_64 build on non-Cygwin hosts Jon Turney
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=20221203161407.2337644-2-corinna-cygwin@cygwin.com \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@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).