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 2CA0A65CBC for ; Mon, 28 Mar 2016 22:18:37 +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 u2SMIYXH021827; Mon, 28 Mar 2016 23:18:34 +0100 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 EvrCDH4VoXjT; Mon, 28 Mar 2016 23:18:34 +0100 (BST) 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 u2SMISFW021822 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 28 Mar 2016 23:18:29 +0100 Message-ID: <1459203508.21672.9.camel@linuxfoundation.org> From: Richard Purdie To: Christopher Larson , Mariano Lopez , openembedded-core@lists.openembedded.org Date: Mon, 28 Mar 2016 23:18:28 +0100 In-Reply-To: References: <34e4b28e8c8e665b38fd82d59ecaf8d486de6193.1458803813.git.mariano.lopez@linux.intel.com> <56F97344.9040204@linux.intel.com> X-Mailer: Evolution 3.16.5-1ubuntu3.1 Mime-Version: 1.0 Subject: Re: [PATCH 1/1] archiver.bbclass: Just archive gcc-source for all gcc recipes 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, 28 Mar 2016 22:18:40 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Mon, 2016-03-28 at 18:43 +0000, Christopher Larson wrote: > Fair enough, thanks for the clarification! Its worth noting we did kill the concept of "shared stamps" from bitbake since it turned out to be a huge pain which could be solved in other ways which whilst ugly, are more reliable and work better. It was only ever used by gcc and didn't work with the kernel as the semantics were different. I'd love a clean solution but have yet to see something that can work better than what we have today without invasive changes to bitbake. Cheers, Richard