From: Jamie Lenehan <lenehan@twibble.org>
To: Martin Dietze <di@fh-wedel.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Thread-support in perl-native often breaks libintl-perl
Date: Wed, 14 Feb 2007 12:34:42 +1100 [thread overview]
Message-ID: <20070214013442.GA1347@twibble.org> (raw)
In-Reply-To: <20070208113136.GA1408@fh-wedel.de>
On Thu, Feb 08, 2007 at 12:31:36PM +0100, Martin Dietze wrote:
> Hi,
>
> on most platforms thread support is turned off for the
> cross-compiled perl packages. However it is always turned
> on in the perl-native package. Since libraries like
> libintl-perl depend on perl-native since they include their
> headers from staging/[my-platform]-linux/lib/perl5 we get
> an inconsistent configuration: the shared lib gettext_xs.so
> is cross-compiled with headers with thread support turned
> on while the actual (non-native) perl has it turned off. In
> the end libintl-perl will not work:
>
> | /var/bin/perl: relocation error: /var/lib/perl5/auto/Locale/gettext_xs/gettext_xs.so: undefined symbol: Perl_Gthr_key_ptr
>
> Removing the `-Dusethreads' from the perl-native recipe solves
> this problem, but will it cause problems for others?
For sh4 I turned on threading for perl which is probably why I didn't
have this issue. I can't remember if I turned it on because of this
issue or if I needed it for somethings else. It probably doesn't
matter much anymore for my situation because I've since rewrote the
perl management application I was working on in C, so I only use perl
a lot of simpler things now.
I agree that we probably need to make perl and perl-native agree on
this. If everything appears to be ok with it turned off in
perl-native then I'd be fine with that (and would turn it of for the
sh4 perl as well.)
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2007-02-14 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 11:31 Thread-support in perl-native often breaks libintl-perl Martin Dietze
2007-02-14 1:34 ` Jamie Lenehan [this message]
2007-02-19 11:27 ` Paul Sokolovsky
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=20070214013442.GA1347@twibble.org \
--to=lenehan@twibble.org \
--cc=di@fh-wedel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox