From: Junqian Gordon Xu <xjqian@gmail.com>
To: Jamie Lenehan <lenehan@twibble.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: perl 5.8.8 is ready
Date: Tue, 01 May 2007 23:05:58 -0500 [thread overview]
Message-ID: <46380E26.6070303@gmail.com> (raw)
In-Reply-To: <20070502003641.GA5189@twibble.org>
Jamie Lenehan wrote:
> On Tue, May 01, 2007 at 12:14:40AM -0500, Junqian Gordon Xu wrote:
>
> This turns out to be an error on my part in perl 5.8.8 - I didn't
> tell bitbake that perl 5.8.8 was providing all the perl modules. So
> when something needed perl-modules (because of a DEPEND or RDEPEND)
> it found that perl 5.8.8 provided them while 5.8.8 didn't.
>
> If you had perl 5.8.7 already compiled and lying around you didn't
> notice this issue. Since I've been building and testing changes for
> both version I had 5.8.7 and 5.8.8 always compiled.
>
> Anyway, I just checked in a fix for this so it should be ok now.
>
>
I can confirm with the latest mtn pull, perl-5.8.8 builds fine for me
here except for some warning signs:
NOTE: package perl-5.8.8: started
NOTE: package perl-5.8.8-r10: task do_package: started
NOTE: perl-lib contains dangling symlink to /usr/lib/perl/5.8.8
NOTE: perl-lib contains dangling symlink to /usr/share/perl/5.8.8
NOTE: Couldn't find shared library provider for libgcc_s.so.1
NOTE: Couldn't find shared library provider for libgcc_s.so.1
>> Besides, I noticed another issue:
>> I had linux-libc-headers-2.6.15.99 compiled (I think it's determined
>> Machine and Distro) . But perl-5.8.8 wants linux-libc-headers-2.6.20.
>> Will that cause problem?
>>
>
> Perl shouldn't care about linux-libc-headers, I use 2.6.15.99 here at
> the moment.
However, this issue is still outstanding. I'm trying to understand where
the 2.6.20 dependency is coming from. Is this a bitbake issue?
bitbake perl:
OE Build Configuration:
BB_VERSION = "1.8.3"
OE_REVISION = "3ea77972dcf422ed70f1a083c412f43ab519f474"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "tosa"
DISTRO = "angstrom"
DISTRO_VERSION = "test-20070502"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: preferred version 2.5 of glibc not available (for item
virtual/arm-angstrom-linux-gnueabi-libc-for-gcc)
NOTE: Preparing Runqueue
NOTE: Executing runqueue
NOTE: Running task 115 of 294 (ID: 131,
/home/OE/org.openembedded.dev/packages/linux-libc-headers/linux-libc-headers_2.6.20.bb,
do_fetch)
NOTE: package linux-libc-headers-2.6.20: started
next prev parent reply other threads:[~2007-05-02 4:16 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
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 [this message]
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=46380E26.6070303@gmail.com \
--to=xjqian@gmail.com \
--cc=lenehan@twibble.org \
--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