* [PATCH 0/1] Fix MakeMaker's finding of perl.real
@ 2011-09-07 5:09 Saul Wold
2011-09-07 5:09 ` [PATCH 1/1] cpan.bbclass: fix native perl issue Saul Wold
2011-09-07 6:38 ` [PATCH 0/1] Fix MakeMaker's finding of perl.real Eric Bénard
0 siblings, 2 replies; 5+ messages in thread
From: Saul Wold @ 2011-09-07 5:09 UTC (permalink / raw)
To: openembedded-core
When configuring cpan packages, the directories passed to MakeMaker
are the target directories. There was a patch that was applied to the
native perl to find perl.real and convert that to perl. This does not
apply for the target perl modules and therefore MakeMaker find perl.real.
This patch to cpan configure modifies the Makefile after configure and
changes the perl.real to just straight perl so we have the correct paths
and shared state info in usable.
Sau!
The following changes since commit 41b7c955cfdc7b4d5c667c8a8742237d5edaca4f:
icu-3.6: fix building with big make -j (2011-09-05 20:38:50 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/fix2
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/fix2
Saul Wold (1):
cpan.bbclass: fix native perl issue
meta/classes/cpan.bbclass | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
--
1.7.6
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 1/1] cpan.bbclass: fix native perl issue
2011-09-07 5:09 [PATCH 0/1] Fix MakeMaker's finding of perl.real Saul Wold
@ 2011-09-07 5:09 ` Saul Wold
2011-09-07 6:38 ` [PATCH 0/1] Fix MakeMaker's finding of perl.real Eric Bénard
1 sibling, 0 replies; 5+ messages in thread
From: Saul Wold @ 2011-09-07 5:09 UTC (permalink / raw)
To: openembedded-core
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/classes/cpan.bbclass | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/classes/cpan.bbclass b/meta/classes/cpan.bbclass
index cb1c2f4..587e688 100644
--- a/meta/classes/cpan.bbclass
+++ b/meta/classes/cpan.bbclass
@@ -24,7 +24,8 @@ cpan_do_configure () {
for f in `find -name Makefile.PL`; do
f2=`echo $f | sed -e 's/.PL//'`
sed -i -e "s:\(PERL_ARCHLIB = \).*:\1${PERL_ARCHLIB}:" \
- $f2
+ -e 's/perl.real/perl/' \
+ $f2
done
fi
}
--
1.7.6
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH 0/1] Fix MakeMaker's finding of perl.real
2011-09-07 5:09 [PATCH 0/1] Fix MakeMaker's finding of perl.real Saul Wold
2011-09-07 5:09 ` [PATCH 1/1] cpan.bbclass: fix native perl issue Saul Wold
@ 2011-09-07 6:38 ` Eric Bénard
2011-09-07 9:07 ` Anders Darander
1 sibling, 1 reply; 5+ messages in thread
From: Eric Bénard @ 2011-09-07 6:38 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Hi,
Le 07/09/2011 07:09, Saul Wold a écrit :
> When configuring cpan packages, the directories passed to MakeMaker are the
> target directories. There was a patch that was applied to the native perl
> to find perl.real and convert that to perl. This does not apply for the
> target perl modules and therefore MakeMaker find perl.real.
>
> This patch to cpan configure modifies the Makefile after configure and
> changes the perl.real to just straight perl so we have the correct paths
> and shared state info in usable.
>
when sending 1 patch, is it possible to not use cover letter in order to have
the explanation in the patch commit ?
That's easier to understand what the patch is doing when browsing log.
Eric
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 0/1] Fix MakeMaker's finding of perl.real
2011-09-07 6:38 ` [PATCH 0/1] Fix MakeMaker's finding of perl.real Eric Bénard
@ 2011-09-07 9:07 ` Anders Darander
2011-09-07 22:42 ` Richard Purdie
0 siblings, 1 reply; 5+ messages in thread
From: Anders Darander @ 2011-09-07 9:07 UTC (permalink / raw)
To: openembedded-core
* Eric Bénard <eric@eukrea.com> [110907 08:41]:
> Le 07/09/2011 07:09, Saul Wold a écrit :
> > When configuring cpan packages, the directories passed to MakeMaker are the
> > target directories. There was a patch that was applied to the native perl
> > to find perl.real and convert that to perl. This does not apply for the
> > target perl modules and therefore MakeMaker find perl.real.
> >
> > This patch to cpan configure modifies the Makefile after configure and
> > changes the perl.real to just straight perl so we have the correct paths
> > and shared state info in usable.
> >
> when sending 1 patch, is it possible to not use cover letter in order to have
> the explanation in the patch commit ?
> That's easier to understand what the patch is doing when browsing log.
Cover letter or not, the patch should include a commit message that
explains the patch. It doesn't really matter if there is only one patch
or a large patch series.
For a single patch, the cover letter can be usefull to provide some
extra information and discussion. In other cases, it can be pretty
useless IMHO.
Regards,
Anders
--
Anders Darander
ChargeStorm AB
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 0/1] Fix MakeMaker's finding of perl.real
2011-09-07 9:07 ` Anders Darander
@ 2011-09-07 22:42 ` Richard Purdie
0 siblings, 0 replies; 5+ messages in thread
From: Richard Purdie @ 2011-09-07 22:42 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Wed, 2011-09-07 at 11:07 +0200, Anders Darander wrote:
> * Eric Bénard <eric@eukrea.com> [110907 08:41]:
> > Le 07/09/2011 07:09, Saul Wold a écrit :
> > > When configuring cpan packages, the directories passed to MakeMaker are the
> > > target directories. There was a patch that was applied to the native perl
> > > to find perl.real and convert that to perl. This does not apply for the
> > > target perl modules and therefore MakeMaker find perl.real.
> > >
> > > This patch to cpan configure modifies the Makefile after configure and
> > > changes the perl.real to just straight perl so we have the correct paths
> > > and shared state info in usable.
> > >
> > when sending 1 patch, is it possible to not use cover letter in order to have
> > the explanation in the patch commit ?
> > That's easier to understand what the patch is doing when browsing log.
>
> Cover letter or not, the patch should include a commit message that
> explains the patch. It doesn't really matter if there is only one patch
> or a large patch series.
>
> For a single patch, the cover letter can be usefull to provide some
> extra information and discussion. In other cases, it can be pretty
> useless IMHO.
This commit has slipped into the tree this time but I agree in future
more explanation of a commit is needed...
Cheers,
Richard
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-09-07 22:47 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-09-07 5:09 [PATCH 0/1] Fix MakeMaker's finding of perl.real Saul Wold
2011-09-07 5:09 ` [PATCH 1/1] cpan.bbclass: fix native perl issue Saul Wold
2011-09-07 6:38 ` [PATCH 0/1] Fix MakeMaker's finding of perl.real Eric Bénard
2011-09-07 9:07 ` Anders Darander
2011-09-07 22:42 ` Richard Purdie
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.