Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: Build Failures
Date: Fri, 12 Oct 2012 12:41:12 +0100	[thread overview]
Message-ID: <507801D8.30001@communistcode.co.uk> (raw)
In-Reply-To: <507800E4.3070305@communistcode.co.uk>

On 12/10/12 12:37, Jack Mitchell wrote:
> On 12/10/12 12:30, Jack Mitchell wrote:
>> On 12/10/12 12:27, 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?
>>>
>>> Cheers,
>>>
>>
>> On a re-run I get:
>>
>> http://ix.io/38J
>>
>> Next step is to try good old cleansstate which I believe will work as 
>> it seems to be an autoreconf which isn't being performed.
>>
>> Regards,
>>
>
> Ok, seems to be maybe a bit more serious that first thought. Pkgconfig 
> still fails to build with the following log:
>
> http://ix.io/38K
>
> Any ideas? Force a rebuild of libtool maybe?
>
> Cheers,
>

Ok, to fix:

bitbake -c cleansstate binutils-crosssdk
bitbake -c cleansstate pkgconfig
bitbake -c cleansstate pkgconfig-native

This got past the issue and it has now continued to build.


-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  reply	other threads:[~2012-10-12 11:52 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 [this message]
2012-10-12 12:57 ` 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=507801D8.30001@communistcode.co.uk \
    --to=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