Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Disable packaged-staging for perl-native
Date: Wed, 28 Jul 2010 09:09:07 +0200	[thread overview]
Message-ID: <i2ol2j$6j7$2@dough.gmane.org> (raw)
In-Reply-To: <4C4F6F91.8000902@mentor.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28-07-10 01:45, Tom Rini wrote:
> I'd like to disable packaged-staging for perl-native.  The problem here
> comes from a number of things that happen.  Some of these can only
> happen in combination with packaged-staging but others I believe could
> happen today.  The problem itself is that if we have perl-native
> available from packaged-staging it can suddenly exist very early.  What
> this means in practical terms is that now we're trying to generate say
> pod2man.pl from pod2man.pl.in and @perl@ is expanded to something beyond
> the "#!" mechanic length limit and recipes start failing to build
> (fixable by changing pod2man.pl.in to use /usr/bin/env perl (and if it
> had a -w changing to Use warnings: or whatever the perl is)).
> 
> There may have been other rats nests I ran into but can't fully confirm
> weren't due to other crazy rats nests I made.  But we hit the above many
> times.
> 
> perl-native: Disable packaged-staging
> 
> Having perl-native come from packaged-staging can expose other issues.
> Disable so we get the normal (potential) behavior here.

In the past 'perl-native' was actually 'perl-cross', you needed to
rebuild it when changing archs. Dunno if that still is the case.

regards,

Koen

> 
> Signed-off-by: Tom Rini <tom_rini@mentor.com>
> 
> diff --git a/recipes/perl/perl-native_5.10.1.bb
> b/recipes/perl/perl-native_5.10.1.bb
> index 0e0854b..98c2c3c 100644
> --- a/recipes/perl/perl-native_5.10.1.bb
> +++ b/recipes/perl/perl-native_5.10.1.bb
> @@ -9,6 +9,9 @@ NATIVE_INSTALL_WORKS = "1"
>  # Not tested enough
>  DEFAULT_PREFERENCE = "-1"
> 
> +# Introduces issues when re-used too early.
> +PSTAGING_DISABLED = "1"
> +
>  FILESDIR = "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/perl-${PV}"
> 
>  SRC_URI =
> "http://ftp.funet.fi/pub/CPAN/src/perl-${PV}.tar.gz;name=perl-${PV} \
> diff --git a/recipes/perl/perl-native_5.8.8.bb
> b/recipes/perl/perl-native_5.8.8.bb
> index fe1bc84..b966eeb 100644
> --- a/recipes/perl/perl-native_5.8.8.bb
> +++ b/recipes/perl/perl-native_5.8.8.bb
> @@ -6,6 +6,9 @@ DEPENDS = "virtual/db-native gdbm-native"
>  PR = "r20"
>  NATIVE_INSTALL_WORKS = "1"
> 
> +# Introduces issues when re-used too early.
> +PSTAGING_DISABLED = "1"
> +
>  FILESDIR = "${@os.path.dirname(bb.data.getVar('FILE',d,1))}/perl-${PV}"
> 
>  SRC_URI = "http://ftp.funet.fi/pub/CPAN/src/5.0/perl-${PV}.tar.gz \
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMT9eTMkyGM64RGpERAuaEAJ9kzPdQLHDcX/GfqTNWFTzMngqzuwCgr3nc
eHEzHXwGeLNBlf6PKpfvRcE=
=roO2
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-07-28  7:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 23:45 [RFC] Disable packaged-staging for perl-native Tom Rini
2010-07-28  7:09 ` Koen Kooi [this message]
2010-07-28  7:28 ` Roman I Khimov
2010-07-28 15:45   ` Tom Rini
2010-08-12 17:12     ` Tom Rini
2010-08-12 17:29       ` Roman I Khimov
2010-08-12 19:00         ` Tom Rini

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='i2ol2j$6j7$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@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