All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/1] sandbox: allow cross-compiling sandbox
Date: Tue, 16 Mar 2021 05:58:26 +0000	[thread overview]
Message-ID: <CAPnjgZ2wYs67be3a8yd5x4g+sKtz5crzuBgR9x_jnVP0q4bJaw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ22UfzG=MVsUxXzGhE5E7ynmHLmFPsoduOPcON13i5huw@mail.gmail.com>

HI Heinrich,

On Thu, 11 Feb 2021 at 10:34, Simon Glass <sjg@chromium.org> wrote:
>
> On Wed, 10 Feb 2021 at 10:59, Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> >
> > UEFI test files like helloworld.efi require an architecture specific
> > PE-COFF header.
> >
> > Currently this does not work for cross compiling. If $CROSS_COMPILE is set,
> > use the first part of the architecture triplet from the variable to
> > choose the PE-COFF header.
> >
> > Now we can cross-compile the sandbox, e.g.
> >
> >     make sandbox_defconfig NO_SDL=1
> >     CROSS_COMPILE=/opt/bin/aarch64-linux-gnu- NO_SDL=1 MK_ARCH=aarch64 make
> >
> > Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> > ---
> > v2:
> >         use $CROSS_COMPILE instead of an extra environment variable
> > ---
> >  Makefile | 10 +++++++---
> >  1 file changed, 7 insertions(+), 3 deletions(-)
>

With this patch if I try to build sandbox with CROSS_COMPILE=/bin/ it fails.

In fact 'buildman -A sandbox' will return '/bin/' so I'd like your
thoughts on what to do about this. Should we modify your patch or
perhaps make buildman return something else with -A sandbox?

Regards,
Simon

> Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot-dm/next, thanks!

      parent reply	other threads:[~2021-03-16  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 17:54 [PATCH v2 1/1] sandbox: allow cross-compiling sandbox Heinrich Schuchardt
2021-02-10 18:20 ` Sean Anderson
2021-02-10 18:30   ` Sean Anderson
2021-02-10 21:34 ` Simon Glass
2021-03-15  7:25   ` Simon Glass
2021-03-16  5:58   ` Simon Glass [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=CAPnjgZ2wYs67be3a8yd5x4g+sKtz5crzuBgR9x_jnVP0q4bJaw@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.