From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] intltool: Use nativeperl binary for PERL instead of 'perl'
Date: Wed, 10 Aug 2011 16:05:35 +0100 [thread overview]
Message-ID: <1312988748.6733.70.camel@phil-desktop> (raw)
In-Reply-To: <4E429CD3.8050002@gmail.com>
On Wed, 2011-08-10 at 07:59 -0700, Khem Raj wrote:
> On 08/10/2011 04:30 AM, Phil Blundell wrote:
> > On Tue, 2011-08-09 at 20:15 -0700, Khem Raj wrote:
> >> +-AC_PATH_PROG(INTLTOOL_PERL, perl) ++AC_PATH_PROG(INTLTOOL_PERL,
> >> nativeperl)
> >
> > I don't think you want to do that for the copy of intltool.m4 that's
> > going to be installed on the target, only for the one that goes into
> > the sysroot.
> >
>
> ah right. I will resubmit
It turns out there are various other things wrong with the installed
intltool as well (not caused by your patch). The copy of
intltool-extract that goes into the rootfs starts with:
#!/home/pb/oe/build-epia/tmp-eglibc/sysroots/x86_64-linux/bin/perl-native/perl
# -*- Mode: perl; indent-tabs-mode: nil; c-basic-offset: 4 -*-
which is clearly no good, and the intltool package which contains this
script doesn't Depend on perl. Also, the output package is
Architecture: i586 when I think it should probably be all. Also the
intltool.m4 file is getting shipped in intltool-dev but I think it
should probably be in intltool.
p.
next prev parent reply other threads:[~2011-08-10 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 3:15 [PATCH] intltool: Use nativeperl binary for PERL instead of 'perl' Khem Raj
2011-08-10 11:30 ` Phil Blundell
2011-08-10 14:59 ` Khem Raj
2011-08-10 15:05 ` Phil Blundell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-12 15:31 Khem Raj
2011-08-15 17:04 ` 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=1312988748.6733.70.camel@phil-desktop \
--to=philb@gnu.org \
--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