From: "noloader at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/30001] Port to autoconf build system (maybe use sbrabec's patch?)
Date: Sun, 12 Feb 2023 19:22:06 +0000 [thread overview]
Message-ID: <bug-30001-11876-mprz1iUTc3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30001-11876@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30001
Jeffrey Walton <noloader at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |noloader at gmail dot com
--- Comment #3 from Jeffrey Walton <noloader at gmail dot com> ---
(In reply to Eli Schwartz from comment #2)
> In general my understanding is that autoconfiscation patch you linked was
> explicitly rejected several times due to the "Incompatible changes" section.
>
> My patch series solves this problem and a number of other problems. It
> should also still work fine with cross-compilation, just specify
> `./configure --host=<triplet>` and it will set up e.g. `$CC` correctly.
One comment... To cross-compile, you should specify both --build and --host.
--build is easy. config.guess gives that triplet:
$ find /usr/share -name config.guess
...
/usr/share/autoconf/build-aux/config.guess
$ /usr/share/autoconf/build-aux/config.guess
x86_64-pc-linux-gnu
--host is the trickier one. There is no list of cross-compile triplets.
Also see
https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Hosts-and-Cross_002dCompilation.html
.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-12 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 11:47 [Bug bzip2/30001] New: " slyich at gmail dot com
2023-01-14 16:49 ` [Bug bzip2/30001] " sam at gentoo dot org
2023-02-12 17:13 ` eschwartz at archlinux dot org
2023-02-12 19:22 ` noloader at gmail dot com [this message]
2024-04-20 7:44 ` sam at gentoo dot org
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=bug-30001-11876-mprz1iUTc3@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bzip2-devel@sourceware.org \
/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).