All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: Openembedded-core@lists.openembedded.org
Subject: linux-yocto (dylan 3.8) arm and recipe-space issues
Date: Fri, 09 Aug 2013 09:34:38 -0500	[thread overview]
Message-ID: <5204FDFE.1020100@pabigot.com> (raw)

I'm trying to use linux-yocto_3.8 under dylan (poky at 899e5cc) for 
gumstix overo as an experiment.  Since there are no overo files in the 
meta branch of the linux-yocto-3.8 repo, I'm using recipe-space 
metadata.  I've run into two anomalies.

First, in-tree metadata is still being found and referenced, which is 
good.  In my case $KARCH=arm which brings in arm.scc, and arm.cfg has:

   # Failure to use this on ARM results in lots of interesting runtime bugs.
   CONFIG_CC_OPTIMIZE_FOR_SIZE=y

But "bitbake linux-yocto -c kernel_configcheck" produces a merge_log.txt 
that has:

   Using meta/cfg/kernel-cache/ktypes/base/base.cfg.sanitized as base
   Merging meta/cfg/kernel-cache/features/kgdb/kgdb.cfg.sanitized
   ...
   Merging meta/cfg/kernel-cache/arch/arm/arm.cfg.sanitized
   ...
   Merging meta/cfg/kernel-cache/ktypes/standard/standard.cfg.sanitized
   Value of CONFIG_CC_OPTIMIZE_FOR_SIZE is redefined by fragment 
meta/cfg/kernel-cache/ktypes/standard/standard.cfg.sanitized:
   Previous value: CONFIG_CC_OPTIMIZE_FOR_SIZE=y
   New value: # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

and indeed CONFIG_CC_OPTIMIZE_FOR_SIZE is not set in the resulting 
config file.  This seems wrong, and I haven't been able to figure out 
how to fix it.  That it's not diagnosed by kernel_configcheck also seems 
wrong.

Second, seeing in that file that various features are being pulled in 
from in-tree meta/cfg/kernel-cache/features, in my recipe-space 
overo.scc I have:

   include features/spi/spi.scc

because the in-tree metadata has that fragment with the contents I 
want.  It seems that because the reference is from a file in 
recipe-space the existing metadata from in-tree isn't found in this 
case, and I have to copy it into recipe-space FILESEXTRAPATHS for it to 
be found.

Is there a way to reference in-tree metadata from a recipe-space scc 
file so I don't have to duplicate it?

Thanks.

Peter


             reply	other threads:[~2013-08-09 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 14:34 Peter A. Bigot [this message]
2013-08-09 15:10 ` linux-yocto (dylan 3.8) arm and recipe-space issues Bruce Ashfield
2013-08-09 16:29   ` Peter A. Bigot

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=5204FDFE.1020100@pabigot.com \
    --to=pab@pabigot.com \
    --cc=Openembedded-core@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 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.