From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1RUdAF-0005HU-OL for openembedded-core@lists.openembedded.org; Sun, 27 Nov 2011 12:44:57 +0100 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id pARBcIRh021515 for ; Sun, 27 Nov 2011 11:38:18 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21304-02 for ; Sun, 27 Nov 2011 11:38:14 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id pARBc9KQ021509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 27 Nov 2011 11:38:10 GMT Message-ID: <1322393898.4798.14.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Sun, 27 Nov 2011 11:38:18 +0000 In-Reply-To: References: <1322233577.22654.0.camel@ted> <1322302567.25382.6.camel@ted> X-Mailer: Evolution 3.2.1- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: [PATCH] ghostscript-native: Ensure the sys/time/h fix is applied for native builds X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Nov 2011 11:44:57 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Sat, 2011-11-26 at 13:50 -0800, Khem Raj wrote: > On Sat, Nov 26, 2011 at 2:16 AM, Richard Purdie > wrote: > > On Fri, 2011-11-25 at 18:39 -0800, Khem Raj wrote: > >> On Fri, Nov 25, 2011 at 7:06 AM, Richard Purdie > >> wrote: > >> > On my system, the sys/time.h header is in a subdir off /usr/include > >> > which causes a build failure. Apply the target CFLAGS fix to native > >> > builds as well to address this. > >> > >> hmmm I thought CFLAGS would be automtically translated with > >> BBCLASSEXTEND = "native" > > > > For native recipes, CFLAGS is replaced by BUILD_CFLAGS... > > yes I see. A little niggle I was thinking of is that at present for a > target recipe if something gets changed in CFLAGS or TARGET_CFLAGS > that makes to the compile phase as combined CFLAGS > > for native we rewrite CFLAGS = BUILD_CFLAGS > > So either CFLAGS += BUILD_FLAGS for native CFLAGS += TARGET_CFLAGS > will make it consistent or just override CFLAGS with BUILD_CFLAGS or > TARGET_CFLAGS depending on recipe type We could do with looking into addressing this inconsistency, yes. Cheers, Richard