From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by mail.openembedded.org (Postfix) with ESMTP id D707D75C93 for ; Tue, 30 Jun 2015 15:45:59 +0000 (UTC) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id 87E75F811DB; Tue, 30 Jun 2015 09:46:00 -0600 (MDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hermes.chez-thomas.org X-Spam-Level: X-Spam-Status: No, score=0.8 required=10.0 tests=ALL_TRUSTED,BAYES_00, DNS_FROM_AHBL_RHSBL autolearn=no version=3.3.2 Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id 28820F811D7; Tue, 30 Jun 2015 09:46:00 -0600 (MDT) Message-ID: <5592B9E5.5000402@mlbassoc.com> Date: Tue, 30 Jun 2015 09:46:45 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <5592B122.4020208@mlbassoc.com> In-Reply-To: Subject: Re: [meta-browser] New chromium warnings X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2015 15:46:00 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2015-06-30 09:32, Burton, Ross wrote: > On 30 June 2015 at 16:09, Gary Thomas wrote: > >> I'm now seeing these warnings with the latest OE-core: >> WARNING: chromium: invalid PACKAGECONFIG: component-build >> WARNING: chromium: invalid PACKAGECONFIG: use-gl >> WARNING: chromium: invalid PACKAGECONFIG: ignore-lost-context >> >> I looked at the recipes and those config strings are not mentioned >> in the PACKAGECONFIG setup which is what is triggering the error. >> > > Can you verify this with bitbake -e? Maybe a conf file is adding them. They are coming from meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium-imx.inc and my local.conf. The chromium recipe checks the PACKAGECONFIG variable for these settings, but is not using PACKAGECONFIG the normal way. It's just the warnings that are new. I suspect the chromium recipe(s) need to be rewritten to play nice with PACKAGECONFIG... -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------