From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4781EE017C1 for ; Wed, 6 Nov 2013 02:39:14 -0800 (PST) Received: from mail212-co9-R.bigfish.com (10.236.132.237) by CO9EHSOBE015.bigfish.com (10.236.130.78) with Microsoft SMTP Server id 14.1.225.22; Wed, 6 Nov 2013 10:39:14 +0000 Received: from mail212-co9 (localhost [127.0.0.1]) by mail212-co9-R.bigfish.com (Postfix) with ESMTP id F01A21801B4; Wed, 6 Nov 2013 10:39:13 +0000 (UTC) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: VS-3(z579ehz98dI936eI1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzzz2dh2a8h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h1ad9h1b0ah1b2fh2222h224fh1fb3h1d0ch1d2eh1d3fh1dfeh1dffh1f5fh1fe8h1ff5h209eh1155h) Received: from mail212-co9 (localhost.localdomain [127.0.0.1]) by mail212-co9 (MessageSwitch) id 1383734351956462_7172; Wed, 6 Nov 2013 10:39:11 +0000 (UTC) Received: from CO9EHSMHS018.bigfish.com (unknown [10.236.132.242]) by mail212-co9.bigfish.com (Postfix) with ESMTP id DB849220066; Wed, 6 Nov 2013 10:39:11 +0000 (UTC) Received: from mail.freescale.net (70.37.183.190) by CO9EHSMHS018.bigfish.com (10.236.130.28) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 6 Nov 2013 10:39:11 +0000 Received: from tx30smr01.am.freescale.net (10.81.153.31) by 039-SN1MMR1-002.039d.mgd.msft.net (10.84.1.15) with Microsoft SMTP Server (TLS) id 14.3.158.2; Wed, 6 Nov 2013 10:39:10 +0000 Received: from [10.29.244.25] ([10.29.244.25]) by tx30smr01.am.freescale.net (8.14.3/8.14.0) with ESMTP id rA6Ad8bh017540; Wed, 6 Nov 2013 03:39:09 -0700 Message-ID: <527A1B07.5020806@freescale.com> Date: Wed, 6 Nov 2013 08:33:43 -0200 From: Daiane Angolini Organization: Freescale Semiconductor User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Gonzalez, Alex" , "meta-freescale@yoctoproject.org" References: <42B840CE3606D94AAA0E228998676BD802028042871F@dor-sms-exch01.digi.com> In-Reply-To: <42B840CE3606D94AAA0E228998676BD802028042871F@dor-sms-exch01.digi.com> X-OriginatorOrg: freescale.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Subject: Re: meta-fsl-arm: master-next: fsl-image-gui build error X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 10:39:18 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 06-11-2013 07:13, Gonzalez, Alex wrote: > Hi, > > I am testing on a imx6qsabresd with the following setup: > > Build Configuration: > BB_VERSION = "1.21.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-12.04" > TARGET_SYS = "arm-poky-linux-gnueabi" > MACHINE = "imx6qsabresd" > DISTRO = "poky" > DISTRO_VERSION = "1.5+snapshot-20131105" > TUNE_FEATURES = "armv7a vfp neon callconvention-hard cortexa9" > TARGET_FPU = "vfp-neon" > meta > meta-yocto > meta-yocto-bsp = "master:57498cede4696526c121e0112b5dea3e6e8365ac" > meta-oe = "master:3cf6fd9961b290f6346be94a98b28a44508176e4" > meta-fsl-arm = "master-next:96ab7a12bf9e10ba1a66bc46d9c0a3205093368f" > meta-fsl-demos = "master:3aa554d5aacaab946013527e45ddbc3af8a25bba" > > My aim is to test the accelerated graphics and video on a 3.10 kernel with the newest user land components available. > > My first question is whether that's a supported build configuration or it's expected to work with the poky master-next branch too. There isn't a master-next branch for meta-oe, so I stuck with master in both. When I test meta-fsl-arm master-next, I use poky/meta-oe on master. > > I needed to make a couple of patches to make fsl-image-gui build. Not sure if anyone is working with the above setup, but here they go just in case. The first one just updates the bbappend recipe name for mesa, and the second one removes a patch for gst-fsl-plugin which apart from not applying does not seem to be needed any more as the package builds fine (apart from tons of warnings). Please, send your patches properly for review. (please, let me know if you don't know what is "properly") > > Is it worth to report problems with this setup or is it too bleeding edge to be worked on right now? I'm not sure if I understood. But, please, master-next is supposed to be tested and any issue reported. Because of that, it's not supposed to be used on your product/production, so, it's "too blending edge to be worked on". Don't base your work on master-next, however, please, work with master-next in order to be sure it's good enough to be merged on master. =D Daiane