From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Diego Sueiro <diego.sueiro@gmail.com>,
Mike Lewis <mikelewis@alphalem.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Custom defconfig is not used
Date: Mon, 28 Oct 2013 16:58:27 -0400 [thread overview]
Message-ID: <526ECFF3.4060207@windriver.com> (raw)
In-Reply-To: <CAMCfZKHuH4egX=Sid-fSaEscGBr_mX-3PC492syD1hD3+fY+rQ@mail.gmail.com>
On 13-10-26 06:57 AM, Diego Sueiro wrote:
> Bruce,
>
> We have two scenarios here:
>
> 1. bbapend with full defconfig replacement
> 2. bbapend with config fragments
>
> The first scenario just worked when using FILESPATH_prepend. For me it
> does not make sense, since on YP manual says that
> FILESEXTRAPATHS_prepend must be use [1].
>
> The second scenario did not worked even changing to FILESPATH_prepend.
I ran tests today, using the layers Mike indicated, since it was
a bit easier for me to set up on top of my existing builds.
I'm using dylan for my yocto checkout (not oe-core standalone, since
this is a yocto list/question),
My build shows:
meta
meta-yocto
meta-yocto-bsp = "dylan:3dc4505f0e744177ae4ddff1e1ce8b31b95dfaa6"
meta-ti = "master:c14c386946e1ea341faeea292580e37d538d645d"
meta-alphalem = "master:a5c0e8ff51297a4090cd47d669b4fc9c94696908"
meta-alphalem-bsp = "master:56086e4dc618e975c9a46491793041f0d18e47a2"
Mike indicated that he was using dylan for meta-ti, but that doesn't
make a difference either, since for our purposed. It's kernel.bbclass
and the yocto kernel processing that matters.
In meta-alphalem-bsp, I have linux-mainline_3.2.bbappend, with the
following content:
> cat linux-mainline_3.2.bbappend
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-3.2:"
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
COMPATIBLE_MACHINE = "(beagleboard)"
SRC_URI_append = " file://defconfig"
SRC_URI_append = " file://my_frag.cfg"
And I added a fragment which has:
> cat my_frag.cfg
CONFIG_WATCHDOG_NOWAYOUT=y
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
When both are applied to the kernel build, we should see CONFIG_NTFS_FS
transition from =m to =y:
> grep CONFIG_NTFS_FS *
defconfig:CONFIG_NTFS_FS=m
my_frag.cfg:CONFIG_NTFS_FS=y
After invoking linux-mainline's configure task, I see the following:
> grep CONFIG_NTFS_FS linux-beagleboard-standard-build/.config
CONFIG_NTFS_FS=y
And other elements of the defconfig and fragment are properly applied
to the configuration phase.
I'm also seeing good results on master, which means that I'm at a
standstill to reproduce any problems.
Diego: can you confirm for me what triggers you are seeing that shows
the defconfig and fragment are not used. I assume the config options
are not present, but I just want to be sure.
Mike: what were you initially seeing that was different from my results ?
Cheers,
Bruce
>
>
> [1] -
> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-FILESEXTRAPATHS
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/25 Mike Lewis <mikelewis@alphalem.com
> <mailto:mikelewis@alphalem.com>>
>
> Bruce: yep, fixed my issue. Sorry for the bother!
>
> Diego: thanks for the solution!
>
> - Mike
>
>
> On 10/25/2013 11:44 AM, Bruce Ashfield wrote:
>
> On Fri, Oct 25, 2013 at 7:43 AM, Diego Sueiro
> <diego.sueiro@gmail.com <mailto:diego.sueiro@gmail.com>> wrote:
>
> Bruce,
>
> Regarding the defconfig not used, I've found this thread on
> Angstrom devel
> ML:
> http://www.mail-archive.com/__angstrom-distro-devel@__linuxtogo.org/msg06721.html
> <http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg06721.html>
>
> I've replaced "FILESEXTRAPATHS_prepend" with
> "FILESPATH_prepend" and removed
> the custom "do_configure_prepend" function and bitbake is
> now using my
> defconfig.
> So, it seems that there is an issue with FILESEXTRAPATHS
> variable.
>
> Aha. That does make sense.
>
> Mike: does that same change fix your issues ?
>
> Bruce
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> 2013/10/23 Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>>
>
> On 13-10-22 12 <tel:13-10-22%2012>:23 PM, Mike Lewis wrote:
>
> Hi Bruce,
>
> I'm trying to accomplish the nearly the same thing
> (i.e. adding config
> fragment) and I'm having the same issue at the
> do_patch step. Were you
> able to reproduce this on your end?
>
>
> Mike,
>
> Is you config/layer somewhere than I can have a look at
> it ? I was trying
> some builds here, and my tests are working. But I'd like
> to try it
> with your config as well.
>
> Bruce
>
>
> Thanks,
> Mike
>
> On 10/18/2013 01:17 PM, Bruce Ashfield wrote:
>
> On 13-10-18 05 <tel:13-10-18%2005>:17 AM, Diego
> Sueiro wrote:
>
>
> 2013/10/18 Bruce Ashfield
> <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>
> <mailto:bruce.ashfield@__windriver.com
> <mailto:bruce.ashfield@windriver.com>>>
>
> I fell behind today .. i had 2300
> unread email to start this
> morning :)
> Is there a way that I can get a copy
> of your recipes and layers ?
> If
> I can do a build myself, I can easily
> debug and fix this ..
> otherwise, we'll
> go back and forth many times debugging.
>
> Cheers,
>
> Bruce
>
>
> I'm using the environment provided by
> Angstrom from it's github setup
> scripts.
> If you want to exactly reproduce it you need to:
>
> git clone
> https://github.com/Angstrom-__distribution/setup-scripts.git
> <https://github.com/Angstrom-distribution/setup-scripts.git>
> cd setup-scripts
> git checkout angstrom-v2013.06-yocto1.4
> MACHINE=beaglebone ./oebb.sh config
> beaglebone
>
> Here is the setup and files for meta-mine:
>
> bblayers.conf:
>
> BBLAYERS = \"
>
> ...
> ${TOPDIR}/sources/meta-mine \
> "
>
> meta-mine/conf/layer.conf:
>
> # We have a conf and classes
> directory, append to BBPATH
> BBPATH .= ":${LAYERDIR}"
> # We have a recipes directory, add to
> BBFILES
> BBFILES += "${LAYERDIR}/recipes*/*/*.bb
> ${LAYERDIR}/recipes*/*/*.__bbappend"
> BBFILE_COLLECTIONS += "mine-layer"
> BBFILE_PATTERN_mine-layer :=
> "^${LAYERDIR}/"
> BBFILE_PRIORITY_mine-layer = "10"
> LAYERDEPENDS_mine-layer = "angstrom-layer"
>
> meta-mine/recipes-kernel/__linux/linux-mainline_3.8.__bbappend:
>
> FILESEXTRAPATHS_prepend :=
> "${THISDIR}/${PN}-3.8:"
> inherit kernel
> require
> recipes-kernel/linux/linux-__yocto.inc
> COMPATIBLE_MACHINE_beaglebone =
> "(beaglebone)"
> SRC_URI += " file://config-addons.cfg "
>
> meta-mine/recipes-kernel/__linux/linux-mainline-3.8/__config-addons.cfg:
>
> CONFIG_WATCHDOG_NOWAYOUT=y
> CONFIG_NTFS_FS=y
> CONFIG_NTFS_RW=y
>
>
>
> But I think that instead of using the whole
> Angstrom you can just use
> poky and meta-beagleboard/common-bsp on
> dylan branch.
>
>
> Great. I'll launch some test builds and see what
> breaks (or works) :)
>
> Bruce
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> /*long live rock 'n roll*/
>
>
> _________________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.__org/listinfo/yocto
> <https://lists.yoctoproject.org/listinfo/yocto>
>
>
> _________________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.__org/listinfo/yocto
> <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
> _________________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.__org/listinfo/yocto
> <https://lists.yoctoproject.org/listinfo/yocto>
>
>
>
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-10-28 20:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 21:07 Custom defconfig is not used Diego Sueiro
2013-10-15 21:29 ` Katu Txakur
2013-10-15 21:49 ` Rudolf Streif
2013-10-15 21:55 ` Andrea Adami
2013-10-16 17:25 ` Diego Sueiro
2013-10-16 18:19 ` Diego Sueiro
2013-10-17 3:56 ` Bruce Ashfield
2013-10-17 10:39 ` Diego Sueiro
2013-10-17 12:50 ` Bruce Ashfield
2013-10-17 13:15 ` Diego Sueiro
2013-10-17 13:19 ` Bruce Ashfield
2013-10-17 13:51 ` Andrea Adami
2013-10-17 15:47 ` Diego Sueiro
2013-10-18 4:48 ` Bruce Ashfield
2013-10-18 9:17 ` Diego Sueiro
2013-10-18 20:17 ` Bruce Ashfield
2013-10-22 16:23 ` Mike Lewis
2013-10-22 22:10 ` Bruce Ashfield
2013-10-24 0:17 ` Bruce Ashfield
2013-10-25 11:43 ` Diego Sueiro
2013-10-25 18:44 ` Bruce Ashfield
2013-10-26 1:19 ` Mike Lewis
2013-10-26 10:57 ` Diego Sueiro
2013-10-26 14:54 ` Bruce Ashfield
2013-10-28 20:58 ` Bruce Ashfield [this message]
2013-10-28 21:41 ` Mike Lewis
2013-10-29 10:33 ` Diego Sueiro
2013-10-29 11:00 ` Andrea Adami
2013-10-29 14:55 ` Diego Sueiro
2013-10-29 15:31 ` Diego Sueiro
2013-10-30 13:04 ` Bruce Ashfield
2013-10-30 13:54 ` Bruce Ashfield
2013-10-30 14:08 ` Diego Sueiro
2013-10-30 14:26 ` Bruce Ashfield
2013-11-04 3:14 ` Bruce Ashfield
2013-11-28 15:37 ` Diego Sueiro
2013-11-28 15:49 ` Bruce Ashfield
2013-11-28 16:26 ` Diego Sueiro
2013-11-28 16:28 ` Bruce Ashfield
2013-11-28 16:41 ` Paul Eggleton
2013-11-28 17:26 ` Bruce Ashfield
2013-10-30 7:57 ` Jukka Rissanen
2013-10-30 12:27 ` Bruce Ashfield
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=526ECFF3.4060207@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=diego.sueiro@gmail.com \
--cc=mikelewis@alphalem.com \
--cc=yocto@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 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.