Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] perl: Allow perl to cross build and native build in a directory named "t"
Date: Tue, 05 Jun 2012 23:05:43 +0100	[thread overview]
Message-ID: <1338933943.20169.280.camel@ted> (raw)
In-Reply-To: <1338835664-27699-1-git-send-email-jason.wessel@windriver.com>

On Mon, 2012-06-04 at 13:47 -0500, Jason Wessel wrote:
> If any directory in leading up to your tmp directory has the name "t"
> perl will fail to build with a very cryptic error shown below:
> 
> pod/buildtoc: no pods at pod/buildtoc line 305.
> make[1]: *** [pod/perltoc.pod] Error 255
> 
> This is a result of the perl file checking making an assumption
> that it is only looking at files and directories with in the perl
> source directory.  This assumption fails with the way bitbake
> sets up perl to properly cross compile.
> 
> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> ---
>  .../perl/perl-5.14.2/perl-build-in-t-dir.patch     |   42 ++++++++++++++++++++
>  meta/recipes-devtools/perl/perl-native_5.14.2.bb   |    5 ++-
>  meta/recipes-devtools/perl/perl_5.14.2.bb          |    3 +-
>  3 files changed, 47 insertions(+), 3 deletions(-)
>  create mode 100644 meta/recipes-devtools/perl/perl-5.14.2/perl-build-in-t-dir.patch

Merged to master, thanks.

Richard




      parent reply	other threads:[~2012-06-05 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 18:47 [PATCH v2] perl: Allow perl to cross build and native build in a directory named "t" Jason Wessel
2012-06-05 20:25 ` Flanagan, Elizabeth
2012-06-05 20:51   ` Darren Hart
2012-06-05 20:58   ` Jason Wessel
2012-06-05 21:03     ` Darren Hart
2012-06-05 21:13     ` Flanagan, Elizabeth
2012-06-05 22:05 ` Richard Purdie [this message]

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=1338933943.20169.280.camel@ted \
    --to=richard.purdie@linuxfoundation.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