From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross@burtonini.com>,
openembedded-core@lists.openembedded.org
Cc: Alejandro Hernandez <alhe@linux.microsoft.com>
Subject: Re: [OE-core] [PATCH 1/3] syslinux: rewrite recipe so only target code is x86-specific
Date: Mon, 14 Dec 2020 13:38:38 +0000 [thread overview]
Message-ID: <005e33e150decf8db347a58325a6fd4446acdb6c.camel@linuxfoundation.org> (raw)
In-Reply-To: <20201210150211.1505531-1-ross.burton@arm.com>
On Thu, 2020-12-10 at 15:02 +0000, Ross Burton wrote:
> Currently the syslinux recipe set COMPATIBLE_HOST to 32/64-bit x86.
> Whilst this makes sense for the target binaries as syslinux is
> x86-specific, this also affects the native recipe which should be able
> to be built on non-x86 build hosts (for example, arm64 build host,
> qemux86 target).
>
> syslinux itself has a somewhat fragile build system but with care it is
> possible to build the installer for native/nativesdk, and the bootloader
> for target. Despite claims the documentation to the contrary, not all
> of the bootloader is shipped precompiled in the tarball which does
> complicate matters.
>
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
> .../syslinux/syslinux_6.04-pre2.bb | 80 ++++++++++---------
> 1 file changed, 43 insertions(+), 37 deletions(-)
Something isn't quite right in this series:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1654/steps/14/logs/stdio
(and all the other selftests in that build)
Cheers,
Richard
prev parent reply other threads:[~2020-12-14 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 15:02 [PATCH 1/3] syslinux: rewrite recipe so only target code is x86-specific Ross Burton
2020-12-10 15:02 ` [PATCH 2/3] wic-image-minimal: only depend on syslinux on x86 targets Ross Burton
2020-12-10 15:02 ` [PATCH 3/3] wic-tools: don't build syslinux-native for targets without syslinux Ross Burton
2020-12-14 13:38 ` Richard Purdie [this message]
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=005e33e150decf8db347a58325a6fd4446acdb6c.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alhe@linux.microsoft.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross@burtonini.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