From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: perl-native, why again?
Date: Wed, 16 Jun 2010 09:13:03 +0200 [thread overview]
Message-ID: <hv9thv$u7$1@dough.gmane.org> (raw)
In-Reply-To: <4C17FB97.1080505@mentor.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16-06-10 00:15, Tom Rini wrote:
> Hey all,
>
> I was wondering, is there a reason for perl native aside from cpan? If
> no, have we tried setting things up such that system perl uses a local
> to $TMPDIR cpan install spot?
>
> I ask since once perl-native exist, stuff can get very unfun (too long
> #!/path/to/perl isn't fun at all).
You can only crosscompile $version of perl if your host is the same
$version. You will get very strange bugs otherwise. That was for perl
5.6 or something, dunno if perl and/or our recipes have improved since.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMGHl+MkyGM64RGpERAuHwAJ9Qf5GMehbwV77J6FgzXtcfPJakKQCfXPtq
RzS3M5uXziEONOj/ctt5QKw=
=EgK8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-16 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 22:15 perl-native, why again? Tom Rini
2010-06-16 7:13 ` Koen Kooi [this message]
2010-06-16 15:15 ` 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='hv9thv$u7$1@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