All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <saul.wold@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/4] crownbay: remove custom BASE_PACKAGE_ARCH and	PACKAGE_EXTRA_ARCHS
Date: Mon, 16 May 2011 09:36:03 +0100	[thread overview]
Message-ID: <1305534963.3424.13.camel@rex> (raw)
In-Reply-To: <4DCF53FC.9060109@intel.com>

On Sat, 2011-05-14 at 21:18 -0700, Saul Wold wrote:
> On 05/14/2011 08:36 PM, Tom Zanussi wrote:
> > From: Tom Zanussi<tom.zanussi@intel.com>
> >
> > PACKAGE_EXTRA_ARCHS in the conf file gets overwritten by the tune-atom
> > include following it, preventing the atom BASE_PACKAGE_ARCH from being
> > included in the final PACKAGE_ARCHS and causing do_rootfs to fail.
> > Remove the atom BASE_PACKAGE_ARCH and PACKAGE_EXTRA_ARCHS in the conf
> > file and allow the values in tune-atom to be used as intended.
> >
> I think we may still want to change the tune-atom PACKAGE_EXTRA_ARCHS to ?=.

No, we really don't want to do that ;-). 

The whole point behind the tune-* include files is they are the one
correct place where these architecture specific flags get setup
correctly. Experience shows people trying to do it in each machine file
get it wrong more often than right, this machine file being a perfect
example.

If some different flags are needed, we create a new tune-xxx file which
can either inherit another and customise or set the correct values
itself.

Cheers,

Richard

> > Fixes [BUGID #986].
> >
> Should be [YOCTO #986]
> 
> > Signed-off-by: Tom Zanussi<tom.zanussi@intel.com>
> > ---
> >   meta-crownbay/conf/machine/crownbay.conf |    3 ---
> >   1 files changed, 0 insertions(+), 3 deletions(-)
> >
> > diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf
> > index b8f107b..bc09ada 100644
> > --- a/meta-crownbay/conf/machine/crownbay.conf
> > +++ b/meta-crownbay/conf/machine/crownbay.conf
> > @@ -5,12 +5,9 @@
> >   # i.e. E660 + EG20T
> >
> >   TARGET_ARCH = "i586"
> > -PACKAGE_EXTRA_ARCHS = "x86 atom"
> >
> >   include conf/machine/include/tune-atom.inc
> >
> > -BASE_PACKAGE_ARCH="atom"
> > -
> >   MACHINE_FEATURES = "kernel26 screen keyboard pci usbhost ext2 ext3 x86 \
> >                       acpi serial usbgadget"
> >
> 
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky




  parent reply	other threads:[~2011-05-16  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15  3:36 [PATCH 0/4] crownbay fixes Tom Zanussi
2011-05-15  3:36 ` [PATCH 1/4] crownbay: remove custom BASE_PACKAGE_ARCH and PACKAGE_EXTRA_ARCHS Tom Zanussi
2011-05-15  4:18   ` Saul Wold
2011-05-15  5:13     ` Tom Zanussi
2011-05-16  8:37       ` Richard Purdie
2011-05-16 14:17         ` Tom Zanussi
2011-05-17 17:25           ` Richard Purdie
2011-05-17 17:59             ` Tom Zanussi
2011-05-16  8:36     ` Richard Purdie [this message]
2011-05-15  3:36 ` [PATCH 2/4] crownbay-noemgd: " Tom Zanussi
2011-05-15  3:36 ` [PATCH 3/4] fishriver: " Tom Zanussi
2011-05-15  3:36 ` [PATCH 4/4] crownbay-noemgd: add crownbay-noemgd as COMPATIBLE_MACHINE to linux-yocto bbappend Tom Zanussi

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=1305534963.3424.13.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@intel.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.