All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dietze <di@fh-wedel.de>
To: openembedded-devel@lists.openembedded.org
Subject: Thread-support in perl-native often breaks libintl-perl
Date: Thu, 8 Feb 2007 12:31:36 +0100	[thread overview]
Message-ID: <20070208113136.GA1408@fh-wedel.de> (raw)

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?

BTW, where is bugs.openembedded.org - it has not been up for a 
longer while...

Cheers,

Martin

-- 
-------------- Martin Dietze --------------- / -- 4G Systeme GmbH Hamburg ---
-- martin@the-little-red-haired-girl.org -- / ---- dietze@4g-systems.com ----
------------- / http://herbert.the-little-red-haired-girl.org / -------------
=+= 
- Are you attempting to tell me my duty, sir?
- No. Just having fun trying to guess what they are.



             reply	other threads:[~2007-02-08 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 11:31 Martin Dietze [this message]
2007-02-14  1:34 ` Thread-support in perl-native often breaks libintl-perl Jamie Lenehan
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=20070208113136.GA1408@fh-wedel.de \
    --to=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 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.