From: Junqian Gordon Xu <xjqian@gmail.com>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@lists.openembedded.org>
Subject: Re: perl 5.8.8 is ready
Date: Sun, 29 Apr 2007 05:51:37 -0500 [thread overview]
Message-ID: <463478B9.3010602@gmail.com> (raw)
In-Reply-To: <20070427105722.GA4340@twibble.org>
Jamie Lenehan wrote:
> Hi,
>
> I think I've got perl 5.8.8 to the stage where it is ready for use.
> As this is a pretty big and complex system and I've made some rather
> large changes to the way the build happens I'd like to get some
> reports from other people that it works for them before removing the
> DEFAULT_PREFERENCE = "-1".
>
> You need to build perl-native 5.8.8 and then perl 5.8.8. (You always
> have to build the matching -native version of perl first.)
>
> So far I've tested sh4/glibc (build & run), i486/glibc (build only)
> and sh4/uclibc (build only) using gcc 3.4.4 for sh4 and gcc 4.1.2 for
> i486.
>
> The main visible changes are:
>
> - Per-arch configurations and now gone, it should build for any
> target now without change.
>
> - Installation paths have all been change to be match the debian
> style (which also happens to be FHS compliant).
>
> - All configurations match (including native) and all configurations
> include threading and shared library support.
>
> The build should also be a lot more reliable and it should resolve
> nearly all of the perl related bugzilla entries (yes, even the
> /bin/sh is dash one ;)
>
> (Note that if you have any cpan modules they all need to rebuilt as
> well when changing to 5.8.8 in order to get installed into the new
> locations.)
>
>
Machine=Tosa
Distro=Angstrom
perl-native-5.8.8 builds fine. But when I run bitbake perl-5.8.8,
it alway try to build perl-native-5.8.7 and perl-5.8.7 first. Am I
missing something?
Gordon
next prev parent reply other threads:[~2007-04-29 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 10:57 perl 5.8.8 is ready Jamie Lenehan
2007-04-28 16:19 ` Rolf Leggewie
2007-04-29 12:59 ` Jamie Lenehan
2007-04-29 15:36 ` Rolf Leggewie
2007-04-29 10:51 ` Junqian Gordon Xu [this message]
2007-04-29 11:43 ` Stelios Koroneos
2007-04-29 11:45 ` CPAN module naming Stelios Koroneos
2007-04-29 12:55 ` Jamie Lenehan
2007-04-29 13:05 ` perl 5.8.8 is ready Jamie Lenehan
2007-04-29 19:40 ` Junqian Gordon Xu
2007-04-30 7:00 ` Junqian Gordon Xu
2007-04-30 8:00 ` Jamie Lenehan
2007-05-01 5:14 ` Junqian Gordon Xu
2007-05-02 0:36 ` Jamie Lenehan
2007-05-02 4:05 ` Junqian Gordon Xu
2007-05-07 18:38 ` Rolf Leggewie
2007-05-08 1:22 ` Jamie Lenehan
-- strict thread matches above, loose matches on Subject: below --
2007-04-28 10:28 Rolf Leggewie
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=463478B9.3010602@gmail.com \
--to=xjqian@gmail.com \
--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 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.