From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dmzms99801.na.baesystems.com (dmzms99801.na.baesystems.com [149.32.232.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 026FAE01410 for ; Thu, 11 Apr 2013 14:05:44 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.87,458,1363132800"; d="scan'208,217";a="4572240" X-IronPort-AV: E=Sophos;i="4.87,458,1363132800"; d="scan'208,217";a="305120434" From: "Saridakis, Dean (US SSA)" To: "yocto@yoctoproject.org" Thread-Topic: Config fragment not being picked up Thread-Index: Ac4283YrptDn0IIISu2Zt+xYxRK9ow== Date: Thu, 11 Apr 2013 21:05:37 +0000 Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.37.161.240] MIME-Version: 1.0 Subject: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 21:05:45 -0000 Message-ID: Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B98BBFB67D89184E8E876F332BDBC3E0A233D7GLDMS85001goldlnk_" --_000_B98BBFB67D89184E8E876F332BDBC3E0A233D7GLDMS85001goldlnk_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Think I've followed the example in the manual correctly. My append file is = pretty simple: FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}" SRC_URI +=3D "file://can.cfg" I'm doing this in a layer on top of a yocto-based SDK. Don't think it shou= ld matter, but the underlying kernel recipe has: do_configure_prepend() { # copy desired defconfig so we pick it up for the real kern= el_do_configure cp ${KERNEL_DEFCONFIG} ${B}/.config } Wasn't able to make much sense of the log: lots of "DEBUG: Removing manifes= t ..." and then some kcfonig output? Any advice/suggestions? Thanks, Dean --_000_B98BBFB67D89184E8E876F332BDBC3E0A233D7GLDMS85001goldlnk_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Think I’ve followed the example in the manual = correctly. My append file is pretty simple:

 

FILESEXTRAPATHS_prepend := =3D "${THISDIR}/${PN}"

SRC_URI +=3D "fi= le://can.cfg"

 

I’m doing this in a layer on top of a yocto-ba= sed SDK.  Don’t think it should matter, but the underlying kerne= l recipe has:

 

do_configure_prepend() {<= o:p>

    &= nbsp;           # copy de= sired defconfig so we pick it up for the real kernel_do_configure

    &= nbsp;           cp ${KERN= EL_DEFCONFIG} ${B}/.config

}

 

Wasn’t able to make much sense of the log: lot= s of “DEBUG: Removing manifest …” and then some kcfonig o= utput?

Any advice/suggestions?

 

Thanks,

 

Dean=

 

--_000_B98BBFB67D89184E8E876F332BDBC3E0A233D7GLDMS85001goldlnk_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1378BE01410 for ; Thu, 11 Apr 2013 14:15:28 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 11 Apr 2013 14:15:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,458,1363158000"; d="scan'208";a="293697399" Received: from wrk.jf.intel.com (HELO localhost) ([10.7.202.72]) by orsmga001.jf.intel.com with ESMTP; 11 Apr 2013 14:15:27 -0700 Date: Thu, 11 Apr 2013 14:12:50 -0700 From: Kevin Strasser To: "Saridakis, Dean (US SSA)" Message-ID: <20130411211247.GA15702@wrk> References: <20130411210547.7F1C9E01496@yocto-www.yoctoproject.org> MIME-Version: 1.0 In-Reply-To: <20130411210547.7F1C9E01496@yocto-www.yoctoproject.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 21:15:28 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 11, 2013 at 09:05:37PM +0000, Saridakis, Dean (US SSA) wrote: > Think I've followed the example in the manual correctly. My append file is pretty simple: > > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}" It looks like you forgot the colon at the end of the path. Try this: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" -Kevin > SRC_URI += "file://can.cfg" > > I'm doing this in a layer on top of a yocto-based SDK. Don't think it should matter, but the underlying kernel recipe has: > > do_configure_prepend() { > # copy desired defconfig so we pick it up for the real kernel_do_configure > cp ${KERNEL_DEFCONFIG} ${B}/.config > } > > Wasn't able to make much sense of the log: lots of "DEBUG: Removing manifest ..." and then some kcfonig output? > Any advice/suggestions? > > Thanks, > > Dean > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dmzms99801.na.baesystems.com (dmzms99801.na.baesystems.com [149.32.232.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4D458E01410 for ; Thu, 11 Apr 2013 16:19:15 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.87,458,1363132800"; d="scan'208";a="4581749" X-IronPort-AV: E=Sophos;i="4.87,458,1363132800"; d="scan'208";a="9203259" From: "Saridakis, Dean (US SSA)" To: Kevin Strasser Thread-Topic: [yocto] Config fragment not being picked up Thread-Index: AQHONvnGciO3n1vSLEGHMocqsqv435jRpwKw Date: Thu, 11 Apr 2013 23:19:11 +0000 In-Reply-To: <20130411211247.GA15702@wrk> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.37.161.240] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 23:19:15 -0000 Message-ID: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > > Think I've followed the example in the manual correctly. My append file= is > pretty simple: > > > > FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}" >=20 > It looks like you forgot the colon at the end of the path. > Try this: > FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}:" >=20 > -Kevin Good eye, but afraid that didn't help (maybe the path was empty before???).= I think the files are getting picked up, since fetch will fail if change t= he file name to force a not found error. >=20 > > SRC_URI +=3D "file://can.cfg" > > > > I'm doing this in a layer on top of a yocto-based SDK. Don't think it = should > matter, but the underlying kernel recipe has: > > > > do_configure_prepend() { > > # copy desired defconfig so we pick it up for the real > kernel_do_configure > > cp ${KERNEL_DEFCONFIG} ${B}/.config } > > > > Wasn't able to make much sense of the log: lots of "DEBUG: Removing > manifest ..." and then some kcfonig output? > > Any advice/suggestions? > > > > Thanks, > > > > Dean From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 65C51E01410 for ; Thu, 11 Apr 2013 17:42:15 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r3C0g9AX025725 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 11 Apr 2013 17:42:09 -0700 (PDT) Received: from bruce-ashfields-macbook.local (128.224.23.114) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Thu, 11 Apr 2013 17:42:09 -0700 Message-ID: <51675860.3030204@windriver.com> Date: Thu, 11 Apr 2013 20:42:08 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: "Saridakis, Dean (US SSA)" References: <20130411231941.C175BE0146C@yocto-www.yoctoproject.org> In-Reply-To: <20130411231941.C175BE0146C@yocto-www.yoctoproject.org> Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2013 00:42:15 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-04-11 7:19 PM, Saridakis, Dean (US SSA) wrote: >>> Think I've followed the example in the manual correctly. My append file is >> pretty simple: >>> >>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}" >> >> It looks like you forgot the colon at the end of the path. >> Try this: >> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >> >> -Kevin > > Good eye, but afraid that didn't help (maybe the path was empty before???). I think the files are getting picked up, since fetch will fail if change the file name to force a not found error. > What release are you using ? I tested this just last night before the 1.4 release final RC .. so it definitely still works! How are you determining that it isn't being picked up? Cheers, Bruce >> >>> SRC_URI += "file://can.cfg" >>> >>> I'm doing this in a layer on top of a yocto-based SDK. Don't think it should >> matter, but the underlying kernel recipe has: >>> >>> do_configure_prepend() { >>> # copy desired defconfig so we pick it up for the real >> kernel_do_configure >>> cp ${KERNEL_DEFCONFIG} ${B}/.config } >>> >>> Wasn't able to make much sense of the log: lots of "DEBUG: Removing >> manifest ..." and then some kcfonig output? >>> Any advice/suggestions? >>> >>> Thanks, >>> >>> Dean > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dmzms99802.na.baesystems.com (dmzms99802.na.baesystems.com [149.32.232.66]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7A37BE00597 for ; Mon, 15 Apr 2013 07:54:32 -0700 (PDT) X-SENDER-IP: 10.37.225.65 X-SENDER-REPUTATION: None X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="5624188" Received: from rfc1918.na.baesystems.com (HELO cascms99801.na.baesystems.com) ([10.37.225.65]) by dmzms99802.na.baesystems.com with ESMTP/TLS/RC4-SHA; 15 Apr 2013 14:54:29 +0000 X-SENDER-IP: 10.37.194.19 X-SENDER-REPUTATION: None X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="180302894" X-IPAS-Result: AqAEAIsTbFEKJcIT/2dsb2JhbAAuIsRAgR10gh8BAQEBAgE6PxACAQgiFBAyJQIEDg2IBrtjjmYxB4JgYQOrIYIo Received: from GLDMS99983.goldlnk.rootlnka.net (10.37.199.132) by gldms99919.goldlnk.rootlnka.net (10.37.194.19) with Microsoft SMTP Server (TLS) id 8.3.279.5; Mon, 15 Apr 2013 10:53:54 -0400 Received: from GLDMS85003.goldlnk.rootlnka.net (10.37.161.195) by gldms99983.goldlnk.rootlnka.net (10.37.199.132) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 15 Apr 2013 10:53:54 -0400 Received: from GLDMS85001.goldlnk.rootlnka.net ([fe80::136:899e:bab0:2587]) by GLDMS85003.goldlnk.rootlnka.net ([172.16.0.147]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 10:53:53 -0400 From: "Saridakis, Dean (US SSA)" To: Bruce Ashfield Thread-Topic: [yocto] Config fragment not being picked up Thread-Index: AQHONxaPciO3n1vSLEGHMocqsqv435jXWHfA Date: Mon, 15 Apr 2013 14:53:53 +0000 Message-ID: References: <20130411231941.C175BE0146C@yocto-www.yoctoproject.org> <51675860.3030204@windriver.com> In-Reply-To: <51675860.3030204@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.37.161.240] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 14:54:32 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > >>> Think I've followed the example in the manual correctly. My append fi= le > is > >> pretty simple: > >>> > >>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}" > >> > >> It looks like you forgot the colon at the end of the path. > >> Try this: > >> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}:" > >> > >> -Kevin > > > > Good eye, but afraid that didn't help (maybe the path was empty > before???). I think the files are getting picked up, since fetch will fai= l if > change the file name to force a not found error. > > >=20 > What release are you using ? I tested this just last night before the > 1.4 release final RC .. so it definitely still works! >=20 > How are you determining that it isn't being picked up? I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2. kernel.bbclass kernel_do_configure() looks like it only does a make oldconf= ig on defconfig...? Should I expect to see the .cfg files being eppended there? The .config I end up with doesn't have the definitions from my .cfg fragmen= t files.=20 >=20 > Cheers, >=20 > Bruce From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F3257E00597 for ; Mon, 15 Apr 2013 07:58:52 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r3FEwo6g004839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Apr 2013 07:58:50 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Mon, 15 Apr 2013 07:58:50 -0700 Message-ID: <516C15A0.3080505@windriver.com> Date: Mon, 15 Apr 2013 10:58:40 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Saridakis, Dean (US SSA)" References: <20130411231941.C175BE0146C@yocto-www.yoctoproject.org> <51675860.3030204@windriver.com> In-Reply-To: Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 14:58:53 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-04-15 10:53 AM, Saridakis, Dean (US SSA) wrote: >>>>> Think I've followed the example in the manual correctly. My append file >> is >>>> pretty simple: >>>>> >>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}" >>>> >>>> It looks like you forgot the colon at the end of the path. >>>> Try this: >>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >>>> >>>> -Kevin >>> >>> Good eye, but afraid that didn't help (maybe the path was empty >> before???). I think the files are getting picked up, since fetch will fail if >> change the file name to force a not found error. >>> >> >> What release are you using ? I tested this just last night before the >> 1.4 release final RC .. so it definitely still works! >> >> How are you determining that it isn't being picked up? > > I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2. > kernel.bbclass kernel_do_configure() looks like it only does a make oldconfig on defconfig...? > Should I expect to see the .cfg files being eppended there? > > The .config I end up with doesn't have the definitions from my .cfg fragment files. Fragments are processed later in the build procedure. Assuming this is a linux-yocto based bbappend, they'll be added in the kernel_configme task, and will modify the base BSP configuration. That doesn't mean that all the settings will make it to the final .config, since normal LKC processing and missing dependencies would drop invalid/incorrect settings. Cheers, Bruce > >> >> Cheers, >> >> Bruce From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dmzms99801.na.baesystems.com (dmzms99801.na.baesystems.com [149.32.232.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B7180E00597 for ; Mon, 15 Apr 2013 08:17:32 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="4845601" X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="305480765" From: "Saridakis, Dean (US SSA)" To: Bruce Ashfield Thread-Topic: [yocto] Config fragment not being picked up Thread-Index: AQHONxaPciO3n1vSLEGHMocqsqv435jXWHfAgABP1wD//79pgA== Date: Mon, 15 Apr 2013 15:17:27 +0000 In-Reply-To: <516C15A0.3080505@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.37.161.240] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 15:17:32 -0000 Message-ID: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > >>>>> Think I've followed the example in the manual correctly. My append > >>>>> file > >> is > >>>> pretty simple: > >>>>> > >>>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}" > >>>> > >>>> It looks like you forgot the colon at the end of the path. > >>>> Try this: > >>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}:" > >>>> > >>>> -Kevin > >>> > >>> Good eye, but afraid that didn't help (maybe the path was empty > >> before???). I think the files are getting picked up, since fetch will > >> fail if change the file name to force a not found error. > >>> > >> > >> What release are you using ? I tested this just last night before the > >> 1.4 release final RC .. so it definitely still works! > >> > >> How are you determining that it isn't being picked up? > > > > I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2= . > > kernel.bbclass kernel_do_configure() looks like it only does a make > oldconfig on defconfig...? > > Should I expect to see the .cfg files being eppended there? > > > > The .config I end up with doesn't have the definitions from my .cfg > fragment files. >=20 > Fragments are processed later in the build procedure. Assuming this is a > linux-yocto based bbappend, they'll be added in the kernel_configme task, > and will modify the base BSP configuration. >=20 > That doesn't mean that all the settings will make it to the final .config= , since > normal LKC processing and missing dependencies would drop > invalid/incorrect settings. The SDK .bb inherits directly from kernel & doesn't use linux-yocto.bb. So = listtask doesn't show configme. I see an addtask for it in linux-yocto.inc, but am guessing that trying to = shoehorn that in on top of the SDK (in my append file) is probably more tro= uble than it's worth.=20 Guess I'm better off trying to figure out how to patch the defconfig? >=20 > Cheers, >=20 > Bruce >=20 > > > >> > >> Cheers, > >> > >> Bruce From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B1A61E00597 for ; Mon, 15 Apr 2013 08:21:10 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r3FFL7Z9009214 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Apr 2013 08:21:07 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Mon, 15 Apr 2013 08:21:07 -0700 Message-ID: <516C1ADA.8050908@windriver.com> Date: Mon, 15 Apr 2013 11:20:58 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Saridakis, Dean (US SSA)" References: <201304151517.r3FFHWcD018317@mr1.windriver.com> In-Reply-To: <201304151517.r3FFHWcD018317@mr1.windriver.com> Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 15:21:10 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-04-15 11:17 AM, Saridakis, Dean (US SSA) wrote: >>>>>>> Think I've followed the example in the manual correctly. My append >>>>>>> file >>>> is >>>>>> pretty simple: >>>>>>> >>>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}" >>>>>> >>>>>> It looks like you forgot the colon at the end of the path. >>>>>> Try this: >>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >>>>>> >>>>>> -Kevin >>>>> >>>>> Good eye, but afraid that didn't help (maybe the path was empty >>>> before???). I think the files are getting picked up, since fetch will >>>> fail if change the file name to force a not found error. >>>>> >>>> >>>> What release are you using ? I tested this just last night before the >>>> 1.4 release final RC .. so it definitely still works! >>>> >>>> How are you determining that it isn't being picked up? >>> >>> I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2. >>> kernel.bbclass kernel_do_configure() looks like it only does a make >> oldconfig on defconfig...? >>> Should I expect to see the .cfg files being eppended there? >>> >>> The .config I end up with doesn't have the definitions from my .cfg >> fragment files. >> >> Fragments are processed later in the build procedure. Assuming this is a >> linux-yocto based bbappend, they'll be added in the kernel_configme task, >> and will modify the base BSP configuration. >> >> That doesn't mean that all the settings will make it to the final .config, since >> normal LKC processing and missing dependencies would drop >> invalid/incorrect settings. > > The SDK .bb inherits directly from kernel & doesn't use linux-yocto.bb. So listtask doesn't show configme. > I see an addtask for it in linux-yocto.inc, but am guessing that trying to shoehorn that in on top of the SDK (in my append file) is probably more trouble than it's worth. > Guess I'm better off trying to figure out how to patch the defconfig? The ability to use fragments requires that you at least use the linux-yocto bbclass, it will work with non linux-yocto recipes, but you need to follow the example in meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb The 1.2 vintage fragments aren't as feature rich as 1.3 and 1.4, but they should work to add simple fragment modifications. I hate to see anyone hacking a defconfig unless nothing else works :) Bruce > > >> >> Cheers, >> >> Bruce >> >>> >>>> >>>> Cheers, >>>> >>>> Bruce > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dmzms99802.na.baesystems.com (dmzms99802.na.baesystems.com [149.32.232.66]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 0B3DDE013CA for ; Mon, 15 Apr 2013 10:36:48 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="5659975" X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="9528682" From: "Saridakis, Dean (US SSA)" To: Bruce Ashfield Thread-Topic: [yocto] Config fragment not being picked up Thread-Index: AQHOOezUciO3n1vSLEGHMocqsqv435jXh64Q Date: Mon, 15 Apr 2013 17:36:44 +0000 In-Reply-To: <516C1ADA.8050908@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.37.161.240] MIME-Version: 1.0 Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 17:36:49 -0000 Message-ID: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable > >>>>>>> Think I've followed the example in the manual correctly. My > >>>>>>> append file > >>>> is > >>>>>> pretty simple: > >>>>>>> > >>>>>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}" > >>>>>> > >>>>>> It looks like you forgot the colon at the end of the path. > >>>>>> Try this: > >>>>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}:" > >>>>>> > >>>>>> -Kevin > >>>>> > >>>>> Good eye, but afraid that didn't help (maybe the path was empty > >>>> before???). I think the files are getting picked up, since fetch > >>>> will fail if change the file name to force a not found error. > >>>>> > >>>> > >>>> What release are you using ? I tested this just last night before > >>>> the > >>>> 1.4 release final RC .. so it definitely still works! > >>>> > >>>> How are you determining that it isn't being picked up? > >>> > >>> I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15= .2. > >>> kernel.bbclass kernel_do_configure() looks like it only does a make > >> oldconfig on defconfig...? > >>> Should I expect to see the .cfg files being eppended there? > >>> > >>> The .config I end up with doesn't have the definitions from my .cfg > >> fragment files. > >> > >> Fragments are processed later in the build procedure. Assuming this > >> is a linux-yocto based bbappend, they'll be added in the > >> kernel_configme task, and will modify the base BSP configuration. > >> > >> That doesn't mean that all the settings will make it to the final > >> .config, since normal LKC processing and missing dependencies would > >> drop invalid/incorrect settings. > > > > The SDK .bb inherits directly from kernel & doesn't use linux-yocto.bb.= So > listtask doesn't show configme. > > I see an addtask for it in linux-yocto.inc, but am guessing that trying= to > shoehorn that in on top of the SDK (in my append file) is probably more > trouble than it's worth. > > Guess I'm better off trying to figure out how to patch the defconfig? >=20 > The ability to use fragments requires that you at least use the linux-yoc= to > bbclass, it will work with non linux-yocto recipes, but you need to follo= w the > example in meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb >=20 > The 1.2 vintage fragments aren't as feature rich as 1.3 and 1.4, but they > should work to add simple fragment modifications. >=20 > I hate to see anyone hacking a defconfig unless nothing else works :) Thanks for all the help. The skeleton example isn't in 1.2. Based on 1.3 I = tried adding=20 require recipes-kernel/linux/linux-yocto.inc to my append, but ran into other errors (looks like it adds 5 tasks includi= ng kernel_configme). Did a brute-force override of do_kernel_checkout() to = get around my 1st error, but then do_patch() failed, so think I'm going to = punt & hack defconfig. Thanks again for all the help. >=20 > Bruce >=20 > > > > > >> > >> Cheers, > >> > >> Bruce > >> > >>> > >>>> > >>>> Cheers, > >>>> > >>>> Bruce > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2A8CFE013CA for ; Mon, 15 Apr 2013 10:40:13 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r3FHdcer028679 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Apr 2013 10:39:38 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.342.3; Mon, 15 Apr 2013 10:39:38 -0700 Message-ID: <516C3B51.5030803@windriver.com> Date: Mon, 15 Apr 2013 13:39:29 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Saridakis, Dean (US SSA)" References: <201304151736.r3FHaW7N002460@mr1.windriver.com> In-Reply-To: <201304151736.r3FHaW7N002460@mr1.windriver.com> Cc: "yocto@yoctoproject.org" Subject: Re: Config fragment not being picked up X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Apr 2013 17:40:13 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-04-15 01:36 PM, Saridakis, Dean (US SSA) wrote: >>>>>>>>> Think I've followed the example in the manual correctly. My >>>>>>>>> append file >>>>>> is >>>>>>>> pretty simple: >>>>>>>>> >>>>>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}" >>>>>>>> >>>>>>>> It looks like you forgot the colon at the end of the path. >>>>>>>> Try this: >>>>>>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" >>>>>>>> >>>>>>>> -Kevin >>>>>>> >>>>>>> Good eye, but afraid that didn't help (maybe the path was empty >>>>>> before???). I think the files are getting picked up, since fetch >>>>>> will fail if change the file name to force a not found error. >>>>>>> >>>>>> >>>>>> What release are you using ? I tested this just last night before >>>>>> the >>>>>> 1.4 release final RC .. so it definitely still works! >>>>>> >>>>>> How are you determining that it isn't being picked up? >>>>> >>>>> I believe the SDK is based on Yocto 1.2 / Poky 7.0 -- bitbake is 1.15.2. >>>>> kernel.bbclass kernel_do_configure() looks like it only does a make >>>> oldconfig on defconfig...? >>>>> Should I expect to see the .cfg files being eppended there? >>>>> >>>>> The .config I end up with doesn't have the definitions from my .cfg >>>> fragment files. >>>> >>>> Fragments are processed later in the build procedure. Assuming this >>>> is a linux-yocto based bbappend, they'll be added in the >>>> kernel_configme task, and will modify the base BSP configuration. >>>> >>>> That doesn't mean that all the settings will make it to the final >>>> .config, since normal LKC processing and missing dependencies would >>>> drop invalid/incorrect settings. >>> >>> The SDK .bb inherits directly from kernel & doesn't use linux-yocto.bb. So >> listtask doesn't show configme. >>> I see an addtask for it in linux-yocto.inc, but am guessing that trying to >> shoehorn that in on top of the SDK (in my append file) is probably more >> trouble than it's worth. >>> Guess I'm better off trying to figure out how to patch the defconfig? >> >> The ability to use fragments requires that you at least use the linux-yocto >> bbclass, it will work with non linux-yocto recipes, but you need to follow the >> example in meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb >> >> The 1.2 vintage fragments aren't as feature rich as 1.3 and 1.4, but they >> should work to add simple fragment modifications. >> >> I hate to see anyone hacking a defconfig unless nothing else works :) > > Thanks for all the help. The skeleton example isn't in 1.2. Based on 1.3 I tried adding > > require recipes-kernel/linux/linux-yocto.inc > > to my append, but ran into other errors (looks like it adds 5 tasks including kernel_configme). Did a brute-force override of do_kernel_checkout() to get around my 1st error, but then do_patch() failed, so think I'm going to punt & hack defconfig. > Thanks again for all the help. Something to look forward to when you can upgrade :) Bruce > >> >> Bruce >> >>> >>> >>>> >>>> Cheers, >>>> >>>> Bruce >>>> >>>>> >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Bruce >>> >