From: Scott Garman <scott.a.garman@intel.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Libtoo sysrootl issue when testing machine specific sysroot
Date: Tue, 11 Jan 2011 10:57:25 -0800 [thread overview]
Message-ID: <4D2CA815.6060205@intel.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A31B6E903@shsmsx501.ccr.corp.intel.com>
On 01/10/2011 07:15 PM, Xu, Dongxiao wrote:
> Hi Richard,
>
> When testing the machine specific sysroot patchset for atom-pc and
> emenlow machines, it exposed a libtool issue that, after the built of
> "Machine A", and then try to build "Machine B" of the same
> architecture, those "-L" paths generated by libtool still points to
> the "Machine A" sysroot, which is definitely not correct and may have
> issues.
Thanks Donxiao for the info. I will make sure to test this scenario
before submitting my libtool 2.4 sysroot support to ensure it is resolved.
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
next prev parent reply other threads:[~2011-01-11 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 3:15 Libtoo sysrootl issue when testing machine specific sysroot Xu, Dongxiao
2011-01-11 18:57 ` Scott Garman [this message]
2011-01-12 0:31 ` Xu, Dongxiao
2011-01-12 11:38 ` Richard Purdie
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=4D2CA815.6060205@intel.com \
--to=scott.a.garman@intel.com \
--cc=dongxiao.xu@intel.com \
--cc=richard.purdie@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.