From: Saul Wold <sgw@linux.intel.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: intltool version check errors
Date: Thu, 29 May 2014 09:50:20 -0700 [thread overview]
Message-ID: <5387654C.5090309@linux.intel.com> (raw)
In-Reply-To: <CAMCfZKGHKjGrNLbumUXCex8=mc3RmamOu-uRv3Rc2R=7Sq+r6w@mail.gmail.com>
On 05/29/2014 09:36 AM, Diego Sueiro wrote:
> Hi Sau!,
>
> On Thu, May 29, 2014 at 12:20 PM, Saul Wold <sgw@linux.intel.com> wrote:
>
>> On 05/29/2014 06:17 AM, Diego Sueiro wrote:
>>
>>> Folks,
>>>
>>> I'm facing with a strange error on daisy branch.
>>> Some native recipes are failing on do_configure step with this message:
>>>
>>> checking for intltool >= 0.35.0...
>>> /<snip>/tmp/sysroots/x86_64-linux/usr/bin/nativeperl found
>>> configure: error: Your intltool is too old. You need intltool 0.35.0 or
>>> later.
>>> Configure failed. The contents of all config.log files follows to aid
>>> debugging
>>>
>>>
>>> But intltool-native version is 0.50.2.
>>> What am I missing?
>>>
>>>
>>> What is your Host OS in this case, it seems like you might be having
>> somekind of host contamination issue.
>>
>
> Ubuntu 14.04 x86_64. I have installed intltools (0.50.2) on host too.
>
>
>> Can you also look at your config.log and see what it was actually testing
>> for.
>>
>
> Do you mean the recipe's log.do_configure?
>
No I mean the actual config.log file from the configure process. Also,
I forgot to ask what's the recipe (if it's public). It's also possible
that the package's configure is looking for a more precise match and we
are actually too new!
Sau!
>
>>
>> Or attach your config.log for us to review
>>
>> Thanks
>>
>> Sau!
>>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/
>
next prev parent reply other threads:[~2014-05-29 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 13:17 intltool version check errors Diego Sueiro
2014-05-29 15:20 ` Saul Wold
2014-05-29 16:36 ` Diego Sueiro
2014-05-29 16:50 ` Saul Wold [this message]
2014-05-29 17:23 ` Diego Sueiro
2014-05-29 17:48 ` Khem Raj
2014-05-29 17:50 ` Diego Sueiro
2014-05-29 18:00 ` Saul Wold
2014-05-29 18:22 ` Diego Sueiro
2014-05-29 18:33 ` Saul Wold
2014-05-29 18:47 ` Diego Sueiro
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=5387654C.5090309@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=diego.sueiro@gmail.com \
--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