From: Scott Garman <scott.a.garman@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [for-denzil][PATCH] libtool: Add missing DEPENDS on libtool-cross
Date: Wed, 03 Oct 2012 16:10:08 -0700 [thread overview]
Message-ID: <506CC5D0.9040107@intel.com> (raw)
In-Reply-To: <1349302889.18301.61.camel@ted>
On 10/03/2012 03:21 PM, Richard Purdie wrote:
> On Wed, 2012-10-03 at 10:17 -0700, Scott Garman wrote:
>> On 10/02/2012 02:30 PM, Chase Maupin wrote:
>>> * When building with 24 bitbake threads on my system I observed
>>> errors like the following:
>>> | configure.ac:199: error: LT_LANG: unsupported language: "Go"
>>> | <tmpdir>/work/armv7a-vfp-neon-oe-linux-gnueabi/libtool-2.4.2-r3.0/libtool-2.4.2/aclocal-copy/libtool.m4:768: LT_LANG is expanded from...
>>> | configure.ac:199: the top level
>>> | autom4te: m4 failed with exit status: 1
>>> * This could be found by doing a clean build. If a build had
>>> already been performed then often just cleaning the libtool
>>> package and rebuilding it would resolve the issue.
>>> * Adding a DEPENDS on libtool-cross resolves this issue with a
>>> clean build.
>>> * Bump the PR
>>>
>>> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
>>
>> Thanks for this, I've merged it into my sgarman/denzil-next testing
>> branches.
>
> This isn't even in master yet and I have some concerns about why its
> necessary. I've not had a chance to look into it properly yet though :/.
Yeah, sorry I'm jumping the gun a bit. I'm trying to merge commits
quickly so I can test the branch soon on the autobuilder and get another
pull request in before the patchset gets too large (last time it was a
bit unwieldy).
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-10-03 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:30 [for-denzil][PATCH] libtool: Add missing DEPENDS on libtool-cross Chase Maupin
2012-10-03 17:17 ` Scott Garman
2012-10-03 22:21 ` Richard Purdie
2012-10-03 23:10 ` Scott Garman [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=506CC5D0.9040107@intel.com \
--to=scott.a.garman@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.