From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 2/2] waf-utils.eclass: Set up QEMU when cross-compiling
Date: Fri, 09 May 2025 19:23:39 +0100 [thread overview]
Message-ID: <1915bbe014f67ad4a793fb1adeb50d545d9d310b.camel@gentoo.org> (raw)
In-Reply-To: <20250509173114.504405-2-chewi@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 833 bytes --]
On Fri, 2025-05-09 at 18:31 +0100, James Le Cuirot wrote:
> waf supports executing binaries via a wrapper for cross-compiling. This
> may already be handled by a QEMU outside this environment if binfmt_misc
> has been used with the F flag, and we cannot add a cross-only dependency
> on QEMU. For these reasons, this sets the prefix using QEMU_LD_PREFIX
> rather adding QEMU's -L arg to the --cross-execute option, and it checks
> whether QEMU is present before trying to use it.
>
> I have used this to cross-compile Samba and its waf-based dependencies.
>
> Signed-off-by: James Le Cuirot <chewi@gentoo.org>
Actually, hold that thought. I've considered cases where the architecture is
the same but the libc is different. While we could still use QEMU in that
case, it would be better not to. Let me rethink this.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2025-05-09 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 17:31 [gentoo-dev] [PATCH 1/2] sysroot.eclass: New eclass for using a different sysroot James Le Cuirot
2025-05-09 17:31 ` [gentoo-dev] [PATCH 2/2] waf-utils.eclass: Set up QEMU when cross-compiling James Le Cuirot
2025-05-09 18:23 ` James Le Cuirot [this message]
2025-05-09 18:29 ` [gentoo-dev] [PATCH 1/2] sysroot.eclass: New eclass for using a different sysroot Ulrich Müller
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=1915bbe014f67ad4a793fb1adeb50d545d9d310b.camel@gentoo.org \
--to=chewi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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