From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 4A46074197 for ; Mon, 13 Feb 2017 18:05:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1DI5Urr007678; Mon, 13 Feb 2017 18:05:30 GMT Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DYntSeDz1aQE; Mon, 13 Feb 2017 18:05:30 +0000 (GMT) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1DI5Iip007612 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 13 Feb 2017 18:05:24 GMT Message-ID: <1487009117.27753.14.camel@linuxfoundation.org> From: Richard Purdie To: Andreas =?ISO-8859-1?Q?M=FCller?= , Patrick Ohly Date: Mon, 13 Feb 2017 10:05:17 -0800 In-Reply-To: References: <1486999455.13854.241.camel@intel.com> X-Mailer: Evolution 3.18.5.2-0ubuntu3.1 Mime-Version: 1.0 Cc: Patches and discussions about the oe-core layer Subject: Re: Does recipe specific sysrooot (or whatelse in current oe) break native dependencies? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 18:05:35 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit On Mon, 2017-02-13 at 16:45 +0100, Andreas Müller wrote: > On Mon, Feb 13, 2017 at 4:24 PM, Patrick Ohly > wrote: > > On Mon, 2017-02-13 at 15:36 +0100, Martin Jansa wrote: > > > I think it's feature which was already there, but almost never > > > triggered (even in test-dependencies.sh tests), but with RSS it > > > fails > > > reliably. > > > > > > See: > > > http://lists.openembedded.org/pipermail/openembedded-core/2016-Ju > > > ly/124435.html > Richard wrote > > > > What it does mean is that any recipe needing a -native recipe to > > build > > should list it in DEPENDS directly, not rely on other dependencies > > to > > pull it in for them. This applies to pkgconfig-native, intltool- > > native > > and also to wayland-native. > This answers my question and leaves me unhappy - I am out for a > while.. To be clear, you can't depend on the build dependencies of some other recipe to be available to your recipe just because you DEPEND on it. The RDEPENDS issue that Patrick mentions is a different one, its a valid recipe markup problem we have processing RDEPENDS information in the native case. The kind of indirection that Andreas sounds like he's been relying on may have happened to work most of the time but I'd bet there were ways that a semi populated sstate cache could break it. With RSS, we encoded the sstate behaviour in a deterministic way so the races that might have happened now do happen all the time. The simple solution for repetitive dependencies and shortcuts is just to create a class, list all the things you need in there and then inherit the class in the recipes as appropriate. I'd hope that isn't too hard to sort out... Cheers, Richard