All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: Rolf Leggewie <no2spam@nospam.arcornews.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: perl 5.8.8 is ready
Date: Sun, 29 Apr 2007 22:59:09 +1000	[thread overview]
Message-ID: <20070429125909.GB8230@twibble.org> (raw)
In-Reply-To: <f0vs5r$6pm$1@sea.gmane.org>

On Sat, Apr 28, 2007 at 06:19:04PM +0200, Rolf Leggewie wrote:
> Jamie Lenehan wrote:
> 
> > You need to build perl-native 5.8.8 and then perl 5.8.8.
> 
> I tried DISTRO=sharprom-compatible.  perl-native-5.8-8 builds fine, but
> unfortunately, perl itself still has issues.  Bug 1700 is not yet resolved.

That uses an old out-of-tree toolchain doesn't it?

I suspect that the gcc_s linking issue would be fixed. The other
issue looks to be related to the compiler version being used. Can you
attach the configure and compile logs for perl 5.8.8 builds using the
sharprom toolchain to the bug? I'll then take a look at it and see if
it can be fixed.

Thanks.

-- 
 Jamie Lenehan <lenehan@twibble.org>



  reply	other threads:[~2007-04-29 13:08 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 [this message]
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
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=20070429125909.GB8230@twibble.org \
    --to=lenehan@twibble.org \
    --cc=no2spam@nospam.arcornews.de \
    --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.