From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] libtool: upgrade to 2.4.4
Date: Wed, 14 Jan 2015 07:06:52 +0800 [thread overview]
Message-ID: <54B5A50C.8080206@windriver.com> (raw)
In-Reply-To: <CAJTo0LaPD+YE0V37reL7brdoE8HiL=5oHz4mDL_nCr3EG5DrTg@mail.gmail.com>
On 01/14/2015 01:44 AM, Burton, Ross wrote:
> On 7 January 2015 at 15:02, Robert Yang <liezhi.yang@windriver.com
> <mailto:liezhi.yang@windriver.com>> wrote:
>
> * The libtool config files are put in libtool/build-aux now, it was
> libtool/config in the past.
>
>
> This may be the cause for a pile of errors on the autobuilder:
>
> ross@flashheart /data/poky-master/tmp/sysroots/intel-corei7-64/usr/bin/crossscripts
> $ grep tmp/work libtoolize
> .
> "/data/poky-master/tmp/work/corei7-64-poky-linux/libtool-cross/2.4.4-r0/libtool-2.4.4/build-aux/funclib.sh"
> .
> "/data/poky-master/tmp/work/corei7-64-poky-linux/libtool-cross/2.4.4-r0/libtool-2.4.4/build-aux/options-parser"
> .
> "/data/poky-master/tmp/work/corei7-64-poky-linux/libtool-cross/2.4.4-r0/libtool-2.4.4/build-aux/extract-trace"
>
> The libtoolize in the sysroot's /usr/bin/crossscripts refers to files in the
> libtool-cross work directory. Hopefully this explains most of the failures this
> upgrade caused (between it and the kernel, my latest MUT run had 73 failures).
Sorry about this, I will look at it today.
// Robert
>
> Ross
next prev parent reply other threads:[~2015-01-13 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 15:02 [PATCH 0/4] Upgrade libtool, git and file Robert Yang
2015-01-07 15:02 ` [PATCH 1/4] file: upgrade to 5.22 Robert Yang
2015-01-07 15:02 ` [PATCH 2/4] git: upgrade to 2.2.1 Robert Yang
2015-01-07 15:02 ` [PATCH 3/4] libtool: upgrade to 2.4.4 Robert Yang
2015-01-13 17:44 ` Burton, Ross
2015-01-13 23:06 ` Robert Yang [this message]
2015-01-14 2:21 ` Robert Yang
2015-01-07 15:02 ` [PATCH 4/4] opkg: fix error for new libtoolize Robert Yang
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=54B5A50C.8080206@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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