From: Saul Wold <sgw@linux.intel.com>
To: Hans Beckerus <hans.beckerus@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v4] libtool: fix resolve of lt_sysroot
Date: Fri, 13 Sep 2013 13:36:06 -0700 [thread overview]
Message-ID: <52337736.1070906@linux.intel.com> (raw)
In-Reply-To: <523367D6.4050604@gmail.com>
On 09/13/2013 12:30 PM, Hans Beckerus wrote:
> On 2013-09-13 8:03, Hans Beckerus wrote:
>> On 2013-09-13 7:49, Saul Wold wrote:
>>> On 09/13/2013 06:29 AM, Hans Beckérus wrote:
<<SNIP>>
>>>>>>
>>>>> Agree. Since all my patch did initially was to make sure gcc was
>>>>> queried when --with-libtool-sysroot was not specified this is the only
>>>>> possible reason I can think of that causes it to break like this. And
>>>>> there is only one side on this coin. The result before the patch if a
>>>>> sysroot *was* specified is the same now also after the patch. I will
>>>>> get back later with a status update on my world build. Will probably
>>>>> take all weekend since it is a simple dual-core ARM mini-server :(
>>>>> I am not really concerned about what release this is targeting. I
>>>>> consider this a workaround until I can dig deeper into what is
>>>>> actually going wrong. My primary goal is to make sure that the SDK
>>>>> does not break as it did before when installed in different paths. Of
>>>>> course that must not affect legacy features so hopefully this
>>>>> workaround eliminates that.
>>>>>
> The current patch looks good so far. I am still running a world build on
> my "failing" host and no errors as of yet. The packages that failed
> before has now passed. Should I make a v5 out of this and then someone
> else (Saul?) can give it an extra spin?
>
Sure, I will give it a local test and if it passes here I can throw it
on the Autobuilder over the weekend and see what happens.
Sau!
>>>>> Thanks.
>>>>> Hans
>>>>>
>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>>
>>>>
>>>>
>>
>
prev parent reply other threads:[~2013-09-13 20:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 14:56 [PATCH v4] libtool: fix resolve of lt_sysroot hans.beckerus
2013-09-10 21:33 ` Saul Wold
2013-09-11 8:15 ` Hans Beckérus
2013-09-11 16:05 ` Hans Beckérus
2013-09-12 17:09 ` Saul Wold
2013-09-12 18:02 ` Hans Beckérus
2013-09-12 21:09 ` Hans Beckerus
2013-09-12 21:50 ` Saul Wold
2013-09-12 23:07 ` Hans Beckerus
2013-09-13 8:06 ` Hans Beckérus
2013-09-13 8:52 ` Richard Purdie
2013-09-13 9:01 ` Hans Beckérus
2013-09-13 9:08 ` Hans Beckérus
2013-09-13 9:53 ` Hans Beckérus
2013-09-13 12:14 ` Hans Beckérus
2013-09-13 12:21 ` Richard Purdie
2013-09-13 13:08 ` Hans Beckérus
2013-09-13 13:29 ` Hans Beckérus
2013-09-13 17:49 ` Saul Wold
2013-09-13 18:03 ` Hans Beckerus
2013-09-13 19:30 ` Hans Beckerus
2013-09-13 20:36 ` Saul Wold [this message]
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=52337736.1070906@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=hans.beckerus@gmail.com \
--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