All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: "Khem Raj (raj.khem@gmail.com)" <raj.khem@gmail.com>
Cc: "OE Core \(openembedded-core@lists.openembedded.org\)"
	<openembedded-core@lists.openembedded.org>
Subject: Can't build product that uses DEFAULTTUNE="arm926ejs"
Date: Mon, 11 Mar 2019 04:20:27 +0000	[thread overview]
Message-ID: <d33eaa8904924405a9a5870faac183e0@XBOX04.axis.com> (raw)

I'm trying to build with master of OE-core and one of our products now 
fails with:

ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker 
    (see sanity.conf). Following is the list of potential problems / advisories:

    Error, the PACKAGE_ARCHS variable (all any noarch arm armv4 armv4t armv5 
    armv5t armv5e armv5te arm926ejste arm926ejse <BSP name withheld>) for 
    DEFAULTTUNE (arm926ejs) does not contain TUNE_PKGARCH (arm926ejst).

I believe this is due to commit ac83d22e (arm-tunes: Remove -march option if 
mcpu is already added). If I build with Thud, TUNE_PKGARCH is "arm926ejste".
The  lack of the "e" at the end when building with master seems to be due to 
the definition of ARMPKGSFX_DSP as 
"${@bb.utils.contains('TUNE_FEATURES', [ 'armv5', 'dsp' ], 'e', '', d)}" and 
the fact that after commit ac83d22e, TUNE_FEATURES no longer contains 'armv5'.

//Peter



             reply	other threads:[~2019-03-11  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  4:20 Peter Kjellerstedt [this message]
2019-03-11  4:23 ` Can't build product that uses DEFAULTTUNE="arm926ejs" Khem Raj
2019-03-11 13:49   ` Peter Kjellerstedt
2019-03-15  5:08     ` Khem Raj
2019-03-16  9:21       ` Peter Kjellerstedt
2019-03-16 10:45         ` Adrian Bunk

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=d33eaa8904924405a9a5870faac183e0@XBOX04.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.