From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: ml@communistcode.co.uk
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Build Failures
Date: Fri, 12 Oct 2012 13:57:11 +0100 [thread overview]
Message-ID: <1350046631.25627.5.camel@ted> (raw)
In-Reply-To: <5077FEA8.5080308@communistcode.co.uk>
On Fri, 2012-10-12 at 12:27 +0100, Jack Mitchell wrote:
> On my git pull and build today I ran into some compile errors. As
> mentioned before I would usually just -c cleansstate and retry, which
> 99% of the time sorts the issue. However, I was informed this was not
> meant to happen and logs would be appreciated, so please find them below.
>
> pkgconfig-native
> http://ix.io/38G
>
> binutils-crosssdk
> http://ix.io/38I
>
> Possibly looks like something doesn't have a 'sed' dependency when it
> should?
See the libtool patch I recently sent out...
Cheers,
Richard
prev parent reply other threads:[~2012-10-12 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 11:27 Build Failures Jack Mitchell
2012-10-12 11:30 ` Jack Mitchell
2012-10-12 11:37 ` Jack Mitchell
2012-10-12 11:41 ` Jack Mitchell
2012-10-12 12:57 ` Richard Purdie [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=1350046631.25627.5.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=ml@communistcode.co.uk \
--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