Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] perl XS modules
Date: Tue, 12 Jul 2016 10:09:21 +0200	[thread overview]
Message-ID: <20160712100921.1bdbf364@free-electrons.com> (raw)
In-Reply-To: <CAGhdn55xFz6+4f46w3OLMwqUGvGv-mVgDLQzg8o07vWMcRQ3Pw@mail.gmail.com>

Hello,

On Tue, 12 Jul 2016 10:00:41 +0200, Fran?ois Perrad wrote:

> The BR package libxml-parser-perl is a very specific host package which
> works only with the the system perl.
> (The reason is : this packge is heavy used, and we don't want the cost|time
> of the host-perl build)

The question from Arne was not about the host variant of
libxml-parser-perl, but about he target variant.

> All Perl modules (XS or Pure Perl) use the naming scheme :
> perl-module-name.
> For example, the wrapper for libxml2 is perl-xml-libxml.
> All these packages use the BR infrastructure perl-package.

Right, but Arne seems to indicate that when you build a *target* Perl
modules with cross-compiled C code (i.e not a pure Perl module), there
is an ABI compatibility issue, because the host perl and the target
perl don't use the same ABI.

Arne: can you give a specific Buildroot configuration and commands to
test that exhibit the problem?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-07-12  8:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08  7:59 [Buildroot] perl XS modules Arne Caspari
2016-07-08 15:40 ` Thomas Petazzoni
2016-07-12  8:00   ` François Perrad
2016-07-12  8:09     ` Thomas Petazzoni [this message]
2016-07-12  8:15     ` Arne Caspari
2016-07-12  8:56       ` Thomas Petazzoni
2016-07-12  9:04         ` Arne Caspari
2016-07-12  9:43           ` François Perrad
2016-07-12 10:16             ` Thomas Petazzoni
2016-07-12 11:05               ` François Perrad
2016-07-12 11:08                 ` Thomas Petazzoni

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=20160712100921.1bdbf364@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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