Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Patch "Don't inherit siteinfo in base.bbclass" breaks SlugOS
Date: Fri, 19 Mar 2010 22:00:40 -0500	[thread overview]
Message-ID: <4BA43A58.905@mwester.net> (raw)

The following commit breaks SlugOS.  I apologize for starting a new
thread on this, but I am unable to find the original discussion on the
OE ml (but I probably missed it in the several hundred that piled up in
my inbox this week).

------------
commit a215c2f283476776567506c2e3f969c48f7e5e3d
Author: Chris Larson <chris_larson@mentor.com>
Date:   Tue Mar 9 16:54:57 2010 -0700

    Don't inherit siteinfo in base.bbclass

    Acked-by: Richard Purdie <rpurdie@linux.intel.com>
    Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
    Signed-off-by: Chris Larson <chris_larson@mentor.com>
------------

In a nutshell, the ixp4xx can run in either endianess, and SlugOS builds
both a BE and an LE image.  Removing "inherit siteinfo" from
base.bbclass causes parsing failures in every recipe.

As an example of the issue, consider this lines in
conf/distro/include/slugos.conf:

IMAGE_BASENAME = "${@['slugos${SITEINFO_ENDIANESS}',
'ucslugc'][bb.data.getVar('TARGET_OS', d, 1) == 'linux-uclibc']}"

and

DISTRO_NAME ?=
"INVALID-${SITEINFO_ENDIANESS}-${ARM_INSTRUCTION_SET}-${TARGET_OS}"

There may be other locations (such as recipes, etc) where this problem
may exist, these were just the two locations I found easily.

Any ideas how to address this?

-Mike (mwester)





             reply	other threads:[~2010-03-20  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  3:00 Mike Westerhof [this message]
2010-03-20  3:16 ` Patch "Don't inherit siteinfo in base.bbclass" breaks SlugOS Chris Larson
2010-03-20  3:20   ` Chris Larson

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=4BA43A58.905@mwester.net \
    --to=mike@mwester.net \
    --cc=openembedded-devel@lists.openembedded.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