From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5 v5] package/meson: never try to run generated target binaries
Date: Fri, 28 Dec 2018 11:54:51 +0100 [thread overview]
Message-ID: <20181228115451.148b39ef@windsurf> (raw)
In-Reply-To: <898a91d14004c0149c8a6c4fcf85670d736ffe11.1545814334.git.yann.morin.1998@free.fr>
Hello,
On Wed, 26 Dec 2018 09:52:26 +0100, Yann E. MORIN wrote:
> From: James Hilliard <james.hilliard1@gmail.com>
>
> As explained in [0], meson will try on its own to decide whether it can
> run what it builds. If it happens that the host and target CPUs are
> "compatible", that test may fail and meson may believe it can run what
> it builds.
>
> Override that test by using needs_exe_wrapper=true, and not defining an
> actual exe_wrapper.
>
> [0] https://mesonbuild.com/Cross-compilation.html
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> [yann.morin.1998 at free.fr:
> - split in its own patch
> - improve commit log
> ]
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> package/meson/cross-compilation.conf.in | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-28 10:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 8:52 [Buildroot] [PATCH 0/5 v5] systemd-boot: new simple EFI bootloader replacing gummmiboot (branch yem/systemd-boot) Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 1/5 v5] package/meson: never try to run generated target binaries Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni [this message]
2018-12-26 8:52 ` [Buildroot] [PATCH 2/5 v5] package/meson: fix CPU familly Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 3/5 v5] core/pkg-infra: allow meson packages to specify custom build rules Yann E. MORIN
2018-12-26 11:36 ` James Hilliard
2018-12-26 12:06 ` Yann E. MORIN
2018-12-27 4:21 ` James Hilliard
2018-12-27 8:23 ` Yann E. MORIN
2018-12-28 10:54 ` Thomas Petazzoni
2018-12-26 8:52 ` [Buildroot] [PATCH 4/5 v5] package/systemd: enable building of systemd-boot Yann E. MORIN
2018-12-26 8:52 ` [Buildroot] [PATCH 5/5 v5] boot/systemd-boot: new package Yann E. MORIN
2018-12-26 9:33 ` Yann E. MORIN
2018-12-26 21:23 ` Thomas Petazzoni
2018-12-26 21:37 ` James Hilliard
2018-12-26 21:43 ` Thomas Petazzoni
2018-12-26 21:52 ` James Hilliard
2018-12-26 21:41 ` Yann E. MORIN
2018-12-26 22:07 ` James Hilliard
2018-12-26 22:12 ` James Hilliard
2018-12-26 22:52 ` James Hilliard
2018-12-27 1:27 ` James Hilliard
2018-12-27 8:49 ` Yann E. MORIN
2018-12-27 9:07 ` James Hilliard
2018-12-27 9:11 ` Yann E. MORIN
2018-12-27 9:13 ` James Hilliard
2018-12-27 10:40 ` Yann E. MORIN
2018-12-27 10:42 ` James Hilliard
2018-12-27 10:57 ` Yann E. MORIN
2018-12-27 11:01 ` James Hilliard
2018-12-29 9:35 ` Yann E. MORIN
2018-12-29 10:50 ` James Hilliard
2018-12-29 11:38 ` Yann E. MORIN
2018-12-29 11:43 ` James Hilliard
2018-12-30 8:44 ` James Hilliard
2018-12-31 10:16 ` Yann E. MORIN
2018-12-31 10:24 ` James Hilliard
2018-12-31 10:36 ` Yann E. MORIN
2018-12-31 12:43 ` Peter Korsgaard
2019-01-10 23:47 ` Arnout Vandecappelle
2019-01-11 5:59 ` Yann E. MORIN
2019-01-11 6:47 ` James Hilliard
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=20181228115451.148b39ef@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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