From: "Jérémy Rosen" <jeremy.rosen@smile.fr>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 7/8] [sanity] fix hardcoded references to gcc
Date: Wed, 24 Aug 2016 09:47:17 +0200 [thread overview]
Message-ID: <d4eee64e-d5aa-938a-8d42-c47bb4953efb@smile.fr> (raw)
In-Reply-To: <b68ccb89-5f9c-f84d-cd1c-de63f41ab99f@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On 23/08/2016 17:40, Jérémy Rosen wrote:
>
>
>
> On 23/08/2016 17:11, Burton, Ross wrote:
>>
>> On 23 August 2016 at 15:53, Burton, Ross <ross.burton@intel.com
>> <mailto:ross.burton@intel.com>> wrote:
>>
>> I think this is because BUILD_CC by default contains whitespace,
>> and bb.utils.which looks for "gcc ". I added a strip() to
>> check_app_exists and it passed, so can you please verify that
>> your series doesn't regress when BUILD_CC isn't overridden?
>>
>>
>> Patch sent to fix check_app_exists(). It currently just strips
>> whitespace and doesn't handle someone passing "foo --bar" to
>> check_app_exists but this is still a step in the right direction.
>>
> will do, but rebuilding from scratch is always long... so not right
> away :)
and... done. I do indeed need your patch to get this working, but it
works correctly.
since I need to get a patch upstream in glibc V2 of this serie won't be
here right away. Hopefully your patch will be accepted at that point
(I'll check that before sending V2)
>> Ross
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3071 bytes --]
next prev parent reply other threads:[~2016-08-24 7:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 7:25 [PATCH 0/8] Fix BUILD_* family of variables Jérémy Rosen
2016-08-23 7:25 ` [PATCH 1/8] [autotools] export CCLD_FOR_BUILD Jérémy Rosen
2016-08-24 0:50 ` Khem Raj
2016-08-24 11:05 ` Jérémy Rosen
2016-08-24 11:28 ` Jérémy Rosen
2016-08-24 19:56 ` Burton, Ross
2016-08-25 12:40 ` Jérémy Rosen
2016-08-25 13:27 ` Burton, Ross
2016-08-23 7:25 ` [PATCH 2/8] [cross] export CC family from BUILD_* for cross compilers Jérémy Rosen
2016-08-23 13:34 ` Peter Kjellerstedt
2016-08-23 14:46 ` Burton, Ross
2016-08-23 14:49 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 3/8] [rpm] force a configure before make distclean Jérémy Rosen
2016-08-23 16:54 ` Burton, Ross
2016-08-23 17:16 ` Mark Hatle
2016-08-24 7:44 ` Jérémy Rosen
2016-08-24 14:13 ` Mark Hatle
2016-08-24 14:17 ` Jérémy Rosen
2016-08-24 14:42 ` Mark Hatle
2016-08-23 7:25 ` [PATCH 4/8] [linux-yocto] allow overriding compiler name in KConfig Jérémy Rosen
2016-08-23 13:36 ` Bruce Ashfield
2016-08-23 13:41 ` Bruce Ashfield
2016-08-23 13:48 ` Jérémy Rosen
2016-08-23 13:43 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 5/8] [linux-libc-headers] " Jérémy Rosen
2016-08-23 13:39 ` Bruce Ashfield
2016-08-24 1:06 ` Khem Raj
2016-08-24 7:45 ` Jérémy Rosen
2016-08-23 7:25 ` [PATCH 6/8] [busybox] " Jérémy Rosen
2016-08-23 7:25 ` [PATCH 7/8] [sanity] fix hardcoded references to gcc Jérémy Rosen
2016-08-23 14:53 ` Burton, Ross
2016-08-23 15:11 ` Burton, Ross
2016-08-23 15:40 ` Jérémy Rosen
2016-08-24 7:47 ` Jérémy Rosen [this message]
2016-08-23 7:25 ` [PATCH 8/8] [glibc] remove hard-coded reference to gcc -E Jérémy Rosen
2016-08-23 14:03 ` Burton, Ross
2016-08-23 14:04 ` Jérémy Rosen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4eee64e-d5aa-938a-8d42-c47bb4953efb@smile.fr \
--to=jeremy.rosen@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox