From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 88BA7E01488 for ; Thu, 30 May 2013 05:07:31 -0700 (PDT) Received: from e6520eb (pac33-2-82-240-38-71.fbx.proxad.net [82.240.38.71]) (Authenticated sender: eukrea) by smtp2-g21.free.fr (Postfix) with ESMTPSA id 692BD4B01CC; Thu, 30 May 2013 14:07:25 +0200 (CEST) Date: Thu, 30 May 2013 14:07:23 +0200 From: Eric =?UTF-8?B?QsOpbmFyZA==?= To: Javier Viguera Message-ID: <20130530140723.5ac63349@e6520eb> In-Reply-To: <51A73FD9.7040308@digi.com> References: <1369850483-17206-1-git-send-email-eric@eukrea.com> <1369850483-17206-3-git-send-email-eric@eukrea.com> <51A720B8.2030002@digi.com> <20130530122926.42e03239@e6520eb> <51A73FD9.7040308@digi.com> Organization: =?UTF-8?B?RXVrcsOpYQ==?= Electromatique X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.18; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Cc: "meta-freescale@yoctoproject.org" Subject: Re: [PATCH v4 3/3] amd-gpu-bin-mx51: new recipe 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 May 2013 12:07:34 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Le Thu, 30 May 2013 14:02:33 +0200, Javier Viguera a =C3=A9crit : > Hi Eric, >=20 > On 30/05/13 12:29, Eric B=C3=A9nard wrote: > > This raise an other problem : > > - when x11 is not in DISTRO_FEATURES, we shouldn't have the x11-bin > > package. >=20 > Well, this probably is solved by something like: >=20 > amd-gpu-x11-bin-mx51: > COMPATIBLE_MACHINE =3D "${@base_contains('DISTRO_FEATURES', 'x11', '(mx5)= ', 'Invalid!', d)}" >=20 > If x11 is not in DISTRO_FEATURES, then COMPATIBLE_MACHINE becomes > 'Invalid!' and that does not match your machine (unless you have a > machine named "Invalid!" :-) ) >=20 yes that's the behaviour I expected by emptying the COMPATIBLE_MACHINE value. I have to check that more in detail to see if that works (and why my change allowed to get rid of the warnings). Eric