From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/10] Small fixes
Date: Wed, 20 Jul 2011 19:03:47 -0700 [thread overview]
Message-ID: <4E278903.3020602@linux.intel.com> (raw)
In-Reply-To: <4E275071.9080600@mentor.com>
On 07/20/2011 03:02 PM, Tom Rini wrote:
> On 07/20/2011 02:06 PM, Martin Jansa wrote:
>> Fixes for recipes using intltool, distributions not having locales support in libc and distutils fix
>>
>> The following changes since commit 0d03800caffc2341b74190d38f7a372223c89f4c:
>>
>> lsbsetup_1.0.bb: Change the hardcoded /usr/lib to support multilib (2011-07-20 15:43:43 +0100)
>>
>> are available in the git repository at:
>> git://git.openembedded.org/openembedded-core-contrib jansa/pull
>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/pull
>>
>> Martin Jansa (10):
>> tcmode-default: set preferred version also for (e)glibc-locale
>> eglibc-package: don't fail without localedef/gconv
>> intltool: inherit perlnative
>> polkit: inherit perlnative
>> shared-mime-info: inherit perlnative
>> xkeyboard-config: inherit perlnative
>> avahi: inherit perlnative
>> vte: inherit perlnative
>> python: save Makefile.sysroot in do_compile
>> python: add patch to fix cross compilation on host with linux-3.0
>
> So, with the long path series I posted most of the perlnative's should
> be handled automatically with cpan having fixed up the tool in question.
> I suspect however that we have a few things like intltool that need
> perlnative but don't today.
>
Are they really still required after Tom's perlnative cpan fix goes in?
I guess I need a test case to try and duplicate the failure better since
I don't see it on any of my 3 build machines!
Sau!
next prev parent reply other threads:[~2011-07-21 2:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 21:06 [PATCH 00/10] Small fixes Martin Jansa
2011-07-20 21:06 ` [PATCH 01/10] tcmode-default: set preferred version also for (e)glibc-locale Martin Jansa
2011-07-20 21:06 ` [PATCH 02/10] eglibc-package: don't fail without localedef/gconv Martin Jansa
2011-08-26 10:12 ` Phil Blundell
2011-08-26 11:31 ` Martin Jansa
2011-08-26 11:41 ` [PATCH] eglibc: fix gconv packaging after 5486cac29db6e67051fff7637a0abc9aeab661e5 Martin Jansa
2011-08-29 13:09 ` Richard Purdie
2011-07-20 21:06 ` [PATCH 03/10] intltool: inherit perlnative Martin Jansa
2011-07-21 5:35 ` Frans Meulenbroeks
2011-07-20 21:06 ` [PATCH 04/10] polkit: " Martin Jansa
2011-07-20 21:14 ` Phil Blundell
2011-07-20 21:06 ` [PATCH 05/10] shared-mime-info: " Martin Jansa
2011-07-20 21:06 ` [PATCH 06/10] xkeyboard-config: " Martin Jansa
2011-07-20 21:06 ` [PATCH 07/10] avahi: " Martin Jansa
2011-07-20 21:06 ` [PATCH 08/10] vte: " Martin Jansa
2011-07-20 21:06 ` [PATCH 09/10] python: save Makefile.sysroot in do_compile Martin Jansa
2011-07-20 21:06 ` [PATCH 10/10] python: add patch to fix cross compilation on host with linux-3.0 Martin Jansa
2011-07-20 22:02 ` [PATCH 00/10] Small fixes Tom Rini
2011-07-21 2:03 ` Saul Wold [this message]
2011-07-21 0:18 ` Khem Raj
2011-07-21 0:54 ` Tom Rini
2011-07-21 6:11 ` Martin Jansa
2011-07-21 9:39 ` Richard Purdie
2011-07-21 16:44 ` Khem Raj
2011-07-21 21:54 ` Richard Purdie
2011-07-21 14:28 ` Tom Rini
2011-07-21 14:53 ` Martin Jansa
2011-07-21 15:35 ` Tom Rini
2011-07-22 15:32 ` Saul Wold
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=4E278903.3020602@linux.intel.com \
--to=sgw@linux.intel.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 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.