From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 12278E00347 for ; Tue, 28 Aug 2012 15:22:11 -0700 (PDT) Received: by obbtb18 with SMTP id tb18so10996683obb.35 for ; Tue, 28 Aug 2012 15:22:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=rVdsf/wHGeRbcqODjgZIBQUtsgdoU1dUmoR4pRgYJPE=; b=zz36hHu9NSehlnf05UGUM35TfQQkuoAmTwZ1Wl7Gx9lMM6LaoWG901WL3AhL36JrK2 lkmNA/AgwyyzioR5JOV7vMeoNXA3mYeLUrI8eDGA3JPAwHUhQmxxCLjNLV+Kjbanuz1e 3k34Aa/0hZUpPfS+uHPiWn7ERjk9qzu+RTorESLSxkqlZUdgZ9GkmxUThHjUk5FEGhhU tpq7So8j0yrmL/8B2teExzyHE85/GHZ7MaivY0Sej8QhJ/fcQh9msSPEZwSJTWATXkuu 2PRWy8Niw6QCxyWrnyI2NvzWagCoLn81u+U8J1FGEZBNjYao4zdbFJ+Q8oZC/l3/KxXw UUJw== MIME-Version: 1.0 Received: by 10.182.78.228 with SMTP id e4mr13809165obx.77.1346192528103; Tue, 28 Aug 2012 15:22:08 -0700 (PDT) Received: by 10.76.77.1 with HTTP; Tue, 28 Aug 2012 15:22:08 -0700 (PDT) Date: Tue, 28 Aug 2012 18:22:08 -0400 Message-ID: From: =?ISO-8859-1?Q?Sebasti=E1n_Bas_Kana?= To: meta-ti@yoctoproject.org X-Mailman-Approved-At: Thu, 30 Aug 2012 10:35:05 -0700 Subject: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Aug 2012 22:22:11 -0000 Content-Type: multipart/alternative; boundary=f46d0445170d6fd7f604c85adffc --f46d0445170d6fd7f604c85adffc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I'm using Yocto/Poky and I'm trying to build an image for my Gumstix Overo. I added the meta-gumstix layer and I can build the minimal image. The issue is with the core-image-base. I get errors regarding the license of the image recipes, so I used BBMASK to solve that. Then, an issue with netbase appears, so I added it to BBMASK too. Then I get an error that says: Nothing RPROVIDES 'fbset' (but /home/sebastian/poky/meta-ti/recipes-graphics/libgles/ libgles-omap3_4.05.00.03.bb RDEPENDS on or otherwise requires it) I tried to remove that error but then other failures arise and I just can't get it to build. Any help will be really appreciated. Thanks in advance! Sebasti=E1n --f46d0445170d6fd7f604c85adffc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm using Yocto/Poky and I'm trying to build= an image for my Gumstix Overo. I added the meta-gumstix layer and I can bu= ild the minimal image. The issue is with the core-image-base. I get errors = regarding the license of the image recipes, so I used BBMASK to solve that.= Then, an issue with netbase appears, so I added it to BBMASK too. Then I g= et an error that says:=A0

Nothing RPROVIDES 'fbset' (but /home/sebastian/= poky/meta-ti/recipes-graphics/libgles/libgles-omap3_4.05.00.03.bb RDEPENDS on or otherwise requires= it)

I tried to remove that error but then other failures ar= ise and I just can't get it to build. Any help will be really appreciat= ed.

Thanks in advance!

Sebasti=E1n=A0
--f46d0445170d6fd7f604c85adffc-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A42D2E0027E for ; Thu, 30 Aug 2012 10:48:15 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id q7UHm8qh024632; Thu, 30 Aug 2012 12:48:08 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7UHm802015781; Thu, 30 Aug 2012 12:48:08 -0500 Received: from dlelxv22.itg.ti.com (172.17.1.197) by dfle73.ent.ti.com (128.247.5.110) with Microsoft SMTP Server id 14.1.323.3; Thu, 30 Aug 2012 12:48:08 -0500 Received: from localhost ([158.218.102.158]) by dlelxv22.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7UHm8in016709; Thu, 30 Aug 2012 12:48:08 -0500 Date: Thu, 30 Aug 2012 13:48:08 -0400 From: Denys Dmytriyenko To: Sebasti?n Bas Kana Message-ID: <20120830174807.GB26145@edge> References: MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: meta-ti@yoctoproject.org Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 17:48:15 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Tue, Aug 28, 2012 at 06:22:08PM -0400, Sebasti?n Bas Kana wrote: > Hi, > > I'm using Yocto/Poky and I'm trying to build an image for my Gumstix Overo. > I added the meta-gumstix layer and I can build the minimal image. The issue > is with the core-image-base. I get errors regarding the license of the > image recipes, so I used BBMASK to solve that. Then, an issue with netbase > appears, so I added it to BBMASK too. Then I get an error that says: > > Nothing RPROVIDES 'fbset' (but > /home/sebastian/poky/meta-ti/recipes-graphics/libgles/ > libgles-omap3_4.05.00.03.bb RDEPENDS on or otherwise requires it) > > I tried to remove that error but then other failures arise and I just can't > get it to build. Any help will be really appreciated. > > Thanks in advance! Apparently, your first email was held for moderation - please subscribe to the mailing list in order to post to it. Your problem is that you are trying to build a raher complete image (core-image-base), which pulls lots of dependencies and some of them are from additional layers, such as meta-openembedded. For example, here's the reason for fbset from libgles-omap3 recipe: > # The initscript calls fbset, cputype calls devmem2 > RDEPENDS_${PN} += "fbset devmem2" Both fbset and devmem2 are available from meta-openembedded. Not sure what was the problem with netbase, as it's quite self contained. Are you sure you are using matching branches? Either way, you may be better off composing your own image recipe, if you don't want to enable additional layers. -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from r-finger.com (r-finger.com [178.79.160.5]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1ABE1E002AC for ; Thu, 30 Aug 2012 12:54:37 -0700 (PDT) Received: from [192.168.0.2] (host81-153-114-228.range81-153.btcentralplus.com [81.153.114.228]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id 4B69C9ADE for ; Thu, 30 Aug 2012 20:54:33 +0100 (BST) Message-ID: <503FC4F8.9020509@r-finger.com> Date: Thu, 30 Aug 2012 20:54:32 +0100 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 MIME-Version: 1.0 To: meta-ti@yoctoproject.org References: <20120830174807.GB26145@edge> In-Reply-To: <20120830174807.GB26145@edge> Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 19:54:37 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, On 30/08/12 18:48, Denys Dmytriyenko wrote: > On Tue, Aug 28, 2012 at 06:22:08PM -0400, Sebasti?n Bas Kana wrote: >> I'm using Yocto/Poky and I'm trying to build an image for my Gumstix Overo. Worth noting that meta-ti is not compatible with Yocto in numerous subtle ways that you will have to work around; for example, in addition to the things you noted, you might, want to add 'TOOLCHAIN_PATH="${STAGING_BINDIR_TOOLCHAIN}"' to your local.conf, or some other suitable config location, as various meta-ti packages will fail to compile without it. > Not sure what was the problem with netbase, as it's quite self contained. Are > you sure you are using matching branches? The problem is that meta-ti seems to be an endlessly moving target tracking the master of oe core, while people using Yocto tend to use its stable releases. meta-ti would really benefit from some formal release process/schedule, but I guess as long as TI considers it to be a community project only, this is unlikely to happen. > Either way, you may be better off composing your own image recipe, if you > don't want to enable additional layers. You don't have much of a choice here; you will need to pick some of these packages from meta-openembedded into a layer of your own as for now combining meta-openembedded with Yocto does not work; hopefully this will be resolved at some point. Tomas From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-f48.google.com (mail-ee0-f48.google.com [74.125.83.48]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 195C7E002AC for ; Thu, 30 Aug 2012 13:04:55 -0700 (PDT) Received: by eekd41 with SMTP id d41so977963eek.35 for ; Thu, 30 Aug 2012 13:04:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=EcQtBb/iwuK3EG3XVcNI52qn/VLKJpE+d435hAP69i8=; b=SZz+TG4QDQBpvakoqdzrfKnzIxh+aLA7jP3mmsWafXAxBgNa2g61KKPaBD/UuJ+S+2 HWVd+aJbuC56Q1igI3kxAimKmoRC7A+l6JWXyuTrP3/Ar01yw1vKh2TzSjSdvIDa+dzR afd2/aT/tkCucBihYmAZtZ0R5Ntw0zecoLGap0Vxvai7bL3csSxLgHTA0GFzgu3/5WVk HhDY7oVV+3NqU45aaslbkIVxsYlNhl8AoUi3WVKv8YnZIm2ts9KAuFO4bI+4CZE7uugO LbJQ1V63uLoMqC0igMhad6GfqSeYO99DUNbvamT4bxHsuF+7pHMNaEpqBrTIav+1oO3w FpZw== Received: by 10.14.223.9 with SMTP id u9mr8167133eep.10.1346357094793; Thu, 30 Aug 2012 13:04:54 -0700 (PDT) Received: from ?IPv6:2001:610:612::45c9:4dbe:38c8:fb8c? ([2001:610:612:0:45c9:4dbe:38c8:fb8c]) by mx.google.com with ESMTPS id e7sm7661137eep.2.2012.08.30.13.04.52 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 30 Aug 2012 13:04:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\)) From: Koen Kooi In-Reply-To: <503FC4F8.9020509@r-finger.com> Date: Thu, 30 Aug 2012 22:04:52 +0200 Message-Id: <2738A779-5C39-4A97-84B0-DF6876997C5D@dominion.thruhere.net> References: <20120830174807.GB26145@edge> <503FC4F8.9020509@r-finger.com> To: Tomas Frydrych X-Mailer: Apple Mail (2.1486) X-Gm-Message-State: ALoCoQlPzEscfptlq33Z2Lh+UY1pF0v/rOSt0mXRRJ2Azf2YJJjAr34m/Xfkp2fXLNg9TtbLrR7x Cc: meta-ti@yoctoproject.org Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 20:04:56 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Op 30 aug. 2012, om 21:54 heeft Tomas Frydrych = het volgende geschreven: >=20 >> Not sure what was the problem with netbase, as it's quite self = contained. Are=20 >> you sure you are using matching branches? >=20 > The problem is that meta-ti seems to be an endlessly moving target > tracking the master of oe core, while people using Yocto tend to use = its > stable releases. meta-ti would really benefit from some formal release > process/schedule, You mean the 'denzil' branch that tracks denzil is not enough?!?!?!= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E3C14E002AC for ; Thu, 30 Aug 2012 13:08:40 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id q7UK8awT011933; Thu, 30 Aug 2012 15:08:36 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7UK8ZsL024114; Thu, 30 Aug 2012 15:08:35 -0500 Received: from dlelxv22.itg.ti.com (172.17.1.197) by dfle73.ent.ti.com (128.247.5.110) with Microsoft SMTP Server id 14.1.323.3; Thu, 30 Aug 2012 15:08:35 -0500 Received: from localhost ([158.218.102.158]) by dlelxv22.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7UK8YBx024073; Thu, 30 Aug 2012 15:08:35 -0500 Date: Thu, 30 Aug 2012 16:08:34 -0400 From: Denys Dmytriyenko To: Tomas Frydrych Message-ID: <20120830200833.GE26145@edge> References: <20120830174807.GB26145@edge> <503FC4F8.9020509@r-finger.com> MIME-Version: 1.0 In-Reply-To: <503FC4F8.9020509@r-finger.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: meta-ti@yoctoproject.org Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 20:08:41 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Thu, Aug 30, 2012 at 08:54:32PM +0100, Tomas Frydrych wrote: > Hi, > > On 30/08/12 18:48, Denys Dmytriyenko wrote: > > On Tue, Aug 28, 2012 at 06:22:08PM -0400, Sebasti?n Bas Kana wrote: > >> I'm using Yocto/Poky and I'm trying to build an image for my Gumstix Overo. > > Worth noting that meta-ti is not compatible with Yocto in numerous > subtle ways that you will have to work around; for example, in addition > to the things you noted, you might, want to add > 'TOOLCHAIN_PATH="${STAGING_BINDIR_TOOLCHAIN}"' to your local.conf, or > some other suitable config location, as various meta-ti packages will > fail to compile without it. Ah, correct, DSP components still use the old TOOLCHAIN_PATH variable that is no longer available from oe-core/yocto. Or rather it was never ported to oe-core from Classic OE as part of my updated external toolchain framework... Most of that still lives in CSL and Linaro recipes, but TOOLCHAIN_PATH got lost in the process, I guess. This needs to be fixed once we get to work on DSP components again... > > Not sure what was the problem with netbase, as it's quite self contained. Are > > you sure you are using matching branches? > > The problem is that meta-ti seems to be an endlessly moving target > tracking the master of oe core, while people using Yocto tend to use its > stable releases. meta-ti would really benefit from some formal release > process/schedule, but I guess as long as TI considers it to be a > community project only, this is unlikely to happen. FYI, there is a "denzil" branch in meta-ti, that corresponds to the same in yocto, as well as most of the other layers, including meta-oe... For our TI SDK products and the new Arago "distribution", we are using said "denzil" branch of meta-ti. Other distributions, like Angstrom, use the same concept of stable releases based on Yocto Project 1.2 and denzil maintenance branches. > > Either way, you may be better off composing your own image recipe, if you > > don't want to enable additional layers. > > You don't have much of a choice here; you will need to pick some of > these packages from meta-openembedded into a layer of your own as for > now combining meta-openembedded with Yocto does not work; hopefully this > will be resolved at some point. There are some conflicts between them, but I don't think it's correct to say they don't work in combination at all... -- Denys From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from r-finger.com (r-finger.com [178.79.160.5]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DD995E002AC for ; Thu, 30 Aug 2012 13:56:26 -0700 (PDT) Received: from [192.168.0.2] (host81-153-114-228.range81-153.btcentralplus.com [81.153.114.228]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id B4B399ADE for ; Thu, 30 Aug 2012 21:56:25 +0100 (BST) Message-ID: <503FD378.9020003@r-finger.com> Date: Thu, 30 Aug 2012 21:56:24 +0100 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 MIME-Version: 1.0 CC: meta-ti@yoctoproject.org References: <20120830174807.GB26145@edge> <503FC4F8.9020509@r-finger.com> <20120830200833.GE26145@edge> In-Reply-To: <20120830200833.GE26145@edge> Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 20:56:27 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, On 30/08/12 21:08, Denys Dmytriyenko wrote: > For our TI SDK products and the new Arago "distribution", we are using said > "denzil" branch of meta-ti. Having a branch is great, but 'branch' and 'release' are very different things; branch is a moving target, a release is a fixed point in time that was tested and approved, and consequently one can have a reasonable expectation (dare I say, a guarantee?), that it works. The current denzil release is 7.0.1; there isn't a meta-ti commit that works with this without jumping through hoops, is there? I think a BSP layer really needs to have formal releases. Tomas From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from comal.ext.ti.com (comal.ext.ti.com [198.47.26.152]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 6926CE002AC for ; Thu, 30 Aug 2012 14:15:40 -0700 (PDT) Received: from dlelxv30.itg.ti.com ([172.17.2.17]) by comal.ext.ti.com (8.13.7/8.13.7) with ESMTP id q7ULFbnn016489; Thu, 30 Aug 2012 16:15:37 -0500 Received: from DFLE73.ent.ti.com (dfle73.ent.ti.com [128.247.5.110]) by dlelxv30.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7ULFb7e019089; Thu, 30 Aug 2012 16:15:37 -0500 Received: from dlelxv22.itg.ti.com (172.17.1.197) by dfle73.ent.ti.com (128.247.5.110) with Microsoft SMTP Server id 14.1.323.3; Thu, 30 Aug 2012 16:15:37 -0500 Received: from localhost ([158.218.102.158]) by dlelxv22.itg.ti.com (8.13.8/8.13.8) with ESMTP id q7ULFbHw008147; Thu, 30 Aug 2012 16:15:37 -0500 Date: Thu, 30 Aug 2012 17:15:37 -0400 From: Denys Dmytriyenko To: Tomas Frydrych Message-ID: <20120830211536.GA20931@edge> References: <20120830174807.GB26145@edge> <503FC4F8.9020509@r-finger.com> <20120830200833.GE26145@edge> <503FD378.9020003@r-finger.com> MIME-Version: 1.0 In-Reply-To: <503FD378.9020003@r-finger.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: meta-ti@yoctoproject.org Subject: Re: Building a core-image-base X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2012 21:15:40 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Thu, Aug 30, 2012 at 09:56:24PM +0100, Tomas Frydrych wrote: > Hi, > > On 30/08/12 21:08, Denys Dmytriyenko wrote: > > For our TI SDK products and the new Arago "distribution", we are using said > > "denzil" branch of meta-ti. > > Having a branch is great, but 'branch' and 'release' are very different > things; branch is a moving target, a release is a fixed point in time > that was tested and approved, and consequently one can have a reasonable > expectation (dare I say, a guarantee?), that it works. The current > denzil release is 7.0.1; there isn't a meta-ti commit that works with > this without jumping through hoops, is there? I think a BSP layer really > needs to have formal releases. There was a tag applied at the time of the Yocto Project release: v2012.05-yocto1.2 [BTW, I'm not sure what 7.0.1 is - is it Poky versioning?] That said, meta-ti was not ready to have a formal release at the time. Moreover, testing with Yocto/Poky release was not done - it was meant to be used with oe-core and possibly meta-oe and be Yocto-compatible. This may sound confusing, but since there's no better terminology available, that would do. Hopefully, by the next Yocto Project 1.3 release, we'll do better testing with just Yocto/Poky, but right now my focus is on bringing up the new Arago distro for our SDKs, while Koen is mostly interested in Angstrom. I do understand that we are getting more and more newcomers from a pure Yocto/Poky environment and making sure we have a smooth experience for them with meta-ti is important, but it will take some time... -- Denys