From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id A1BBEE007B6; Thu, 30 Apr 2015 07:34:38 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3A4C6E0049A for ; Thu, 30 Apr 2015 07:34:36 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id B293C6002ACA; Thu, 30 Apr 2015 17:34:34 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1430404474; bh=83Tcs/35iDu9m8atuAWNbK7+3XHtOOWxuutI/6293bw=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=gyBu0LAFYdiA5fsTmhGbZ9Qhc1qenIoAuoQfzIUEVxErGVOIhpld+l4mNmJx5Fh+C 5iQetr3BuQAhoB48LfX2yN7opgMyJPOX8Ca7W/C4ueiAA/w2S6S4bUDjmtPoTBWFcP umRtI0MWaVsq6QBjdjgyg4m/ShvlHKTei0S4Brlg= Message-ID: <55423D7A.7090105@mail.bg> Date: Thu, 30 Apr 2015 17:34:34 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Otavio Salvador References: <1430343511-14563-1-git-send-email-picmaster@mail.bg> <55415F40.30700@mail.bg> <5541986A.6060607@mail.bg> <55419FF4.508@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: [meta-fsl-arm-extra][PATCH v2] riotboard: Fix broken image builds against linux-fslc 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: Thu, 30 Apr 2015 14:34:38 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Otavio, On 04/30/2015 01:52 PM, Otavio Salvador wrote: > On Thu, Apr 30, 2015 at 12:22 AM, Nikolay Dimitrov wrote: >> On 04/30/2015 05:50 AM, Nikolay Dimitrov wrote: >>> The obvious part is that someone is pulling-in imx-lib, which >>> shouldn't be built with linux-fslc. I'm still to figure out why. >>> >>> Regards, Nikolay >> >> >> It looks like packagegroup-fsl-gstreamer-full pulls-in, gst-plugins-gl, >> gst-fsl-plugin and finally imx-lib, which causes the build failure. >> >> Here's the source of the issue >> (meta-fsl-demos/recipes-fsl/packagegroups/packagegroup-fsl-gstreamer-full.bb): >> >> # FIXME: i.MX6SL cannot use mesa for Graphics and it lacks 3D support, >> # so skip it for now. >> RDEPENDS_${PN}_remove_mx6sl = "gst-plugins-gl" >> >> This fix prevents the build failure for warp (I already tested it). For >> imx6sl the situation is easy, as the both the hardware and kernel >> doesn't support gpu3d. But this is not the case for imx6dl and >> linux-fslc. We can't just remove gst-plugins-gl when building for imx6dl. >> >> Probably we need something like this: >> >> RDEPENDS_${PN}_remove_mx6dl = "${@bb.utils.contains('KERNEL_FEATURES', >> 'supports-gpu3d', '', 'gst-plugins-gl', d)}" >> >> Any ideas? > > https://github.com/Freescale/meta-fsl-arm-extra/blob/master/conf/machine/m53evk.conf#L25 > > This should fix this all (replace the machine name, of course). Can you be more specific, please? I don't see anything that helps, but I could be wrong. Regards, Nikolay