Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] arch-x86: Add x86-x32 to MACHINEOVERRIDES
Date: Mon, 25 Sep 2017 17:46:12 -0700	[thread overview]
Message-ID: <1506386772.24844.45.camel@linux.intel.com> (raw)
In-Reply-To: <1505981757.18640.155.camel@linuxfoundation.org>

On Thu, 2017-09-21 at 09:15 +0100, Richard Purdie wrote:
> On Tue, 2017-09-19 at 11:27 -0700, Saul Wold wrote:
> > This is needed as an x32 more generic x32 override later in the
> > OVERRIDES, currently linux-gnux32 is the first override, but we
> > need a stronger (later in the list) x32 override to deal with some
> > needed x32 dependency overrides.
> > 
> > Signed-off-by: Saul Wold <sgw@linux.intel.com>
> > ---
> >  meta/conf/machine/include/x86/arch-x86.inc | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/meta/conf/machine/include/x86/arch-x86.inc
> > b/meta/conf/machine/include/x86/arch-x86.inc
> > index e51d595f74..31d30b3304 100644
> > --- a/meta/conf/machine/include/x86/arch-x86.inc
> > +++ b/meta/conf/machine/include/x86/arch-x86.inc
> > @@ -26,6 +26,7 @@ TUNE_LDARGS += "${@bb.utils.contains('TUNE_FEATUR
> > ES', 'mx32', '-m elf32_x86_64',
> >  TUNE_ASARGS += "${@bb.utils.contains('TUNE_FEATURES', 'mx32', '-
> > x32', '', d)}"
> >  # user mode qemu doesn't support x32
> >  MACHINE_FEATURES_BACKFILL_CONSIDERED_append = " ${@bb.utils.contai
> > ns('TUNE_FEATURES', 'mx32', 'qemu-usermode', '', d)}"
> > +MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'mx32',
> > 'x86_x32:', '' ,d)}"
> >  
> >  # ELF64 ABI
> >  TUNEVALID[m64] = "IA32e (x86_64) ELF64 standard ABI"
> 
> I was ok with this until I realised the patch does not do what it
> says
> in the commit message, it adds "x86_x32", not "x86-x32". Since "_" is
> the override modifier, I worry about how this reacts with the rest of
> the system and I suspect its a bad idea. Is there a reason you didn't
> use "x86-x32" (following the example of x86-64)?
> 
Typo, possibly or had not considered the override issue.

v2 in flight shortly.

Sau!

> Cheers,
> 
> Richard


  reply	other threads:[~2017-09-26  0:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 18:27 [PATCH 0/3] Disable systemd-boot from building with x32 IA Machine Saul Wold
2017-09-19 18:27 ` [PATCH 1/3] arch-x86: Add x86-x32 to MACHINEOVERRIDES Saul Wold
2017-09-21  8:15   ` Richard Purdie
2017-09-26  0:46     ` Saul Wold [this message]
2017-09-19 18:27 ` [PATCH 2/3] wic: remove systemd-boot for x32 Saul Wold
2017-09-21  8:17   ` Richard Purdie
2017-09-21 14:22   ` Khem Raj
2017-09-19 18:27 ` [PATCH 3/3] systemd-boot: Should not build x32 Saul Wold

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=1506386772.24844.45.camel@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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