yocto.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Luiz Balloti" <luiz.balloti@timpelmedical.com>
To: yocto@lists.yoctoproject.org
Subject: Machine overrides for x86 and x86-64
Date: Thu, 07 Oct 2021 11:29:26 -0700	[thread overview]
Message-ID: <JbES.1633631366549333859.AamO@lists.yoctoproject.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]

Hi everyone. I'm not a Yocto/bitbake expert, so please forgive me for the possibily confusing message.

Our current Yocto setup uses sumo (we're stuck with that right now, don't know if it matters). It has one shared layer, an ARM layer with one machine and a "x86" layer with two 32-bit machines. A few recipes in shared our layer use a "x86" override to restrict functionality to these machines (bbappends were causing trouble, so I went the override route).

We now have a requirement to migrate one of the x86-32 machines to a 64-bit system. My first step was to use "genericx86-64" as a test machine and inspect a few variables. I was surprised to find out that MACHINEOVERRIDES does not list "x86" anymore, just the machine's name. I'd expect that a common override for x86 machines would be defined, regardless of the bitness, but repeating this with "genericx86" tells me this is not the case. We have meta-intel, but it seems our x86 machine variables come from meta-yocto-bsp (I wonder now if this is a layer priority issue).

Is this not a common use case or is our setup fundamentally wrong?

Thanks in advance for any help.

[-- Attachment #2: Type: text/html, Size: 1183 bytes --]

             reply	other threads:[~2021-10-07 18:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 18:29 Luiz Balloti [this message]
2021-10-07 23:28 ` [yocto] Machine overrides for x86 and x86-64 Khem Raj

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=JbES.1633631366549333859.AamO@lists.yoctoproject.org \
    --to=luiz.balloti@timpelmedical.com \
    --cc=yocto@lists.yoctoproject.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;
as well as URLs for NNTP newsgroup(s).