From: Saul Wold <sgw@linux.intel.com>
To: Diego Sueiro <diego.sueiro@gmail.com>, Khem Raj <raj.khem@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 11:00:04 -0700 [thread overview]
Message-ID: <538775A4.9060908@linux.intel.com> (raw)
In-Reply-To: <CAMCfZKHFGk2myN0R9LXNY1ZoWFd+WQLx5r98BpnC7-0R3XrASg@mail.gmail.com>
On 05/29/2014 10:50 AM, Diego Sueiro wrote:
> Khem,
>
> On Thu, May 29, 2014 at 2:48 PM, Khem Raj <raj.khem@gmail.com> wrote:
>
>> On Thu, May 29, 2014 at 10:23 AM, Diego Sueiro <diego.sueiro@gmail.com>
>> wrote:
>>> For now these are the recipes:
>>>
>>> shared-mime-info_1.2.bb
>>> gconf_3.2.6.bb
>>> libsoup-2.4_2.45.3.bb
>>> gconf_3.2.6.bb
>>> avahi_0.6.31.bb
>>> xkeyboard-config_2.11.bb
>>> libfm_1.1.2.2.bb
>>> glib-networking_2.38.0.bb
>>> connman-gnome_0.7.bb
>>>
>>>
>>> Find attached the config.log for shared-mime-info-native.
>>>
>>> I had recently update my Ubuntu from 12.10 to 14.04. Do you think it can
>>> cause this error?
>>>
>>
>> Do you have intltool-update binary on your host ? outside sys root ?
>>
>> and if yes then whats the version of it.
>
>
> $ intltool-update --version
> intltool-update (intltool) 0.50.2
> Written by Kenneth Christiansen, Maciej Stachowiak, and Darin Adler.
>
> Copyright (C) 2000-2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
Looking at the log file, seems to have some output about the nativeperl,
I missed the output of this initially:
/<snip>/tmp/sysroots/x86_64-linux/usr/bin/nativeperl found
seems you have some additional output that is confusing things
If you run bitbake shared-mime-info -c devshell and then within the
devshell run intltool-update --version, what happens? It seems that the
nativeperl is getting getting printed out.
any chance you are available on IRC freenode #yocto, I am sgw_ there,
maybe we can work this realtime
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 18:00 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
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 [this message]
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=538775A4.9060908@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=diego.sueiro@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.