Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Caspari <arne.caspari@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] perl XS modules
Date: Tue, 12 Jul 2016 11:04:38 +0200	[thread overview]
Message-ID: <20160712110438.62d56296@gmail.com> (raw)
In-Reply-To: <20160712105624.58817034@free-electrons.com>

Am Tue, 12 Jul 2016 10:56:24 +0200
schrieb Thomas Petazzoni <thomas.petazzoni@free-electrons.com>:
> 
> Again, could you give a Buildroot configuration, and a test scenario
> that allows us to reproduce the issue ?
> 

Thomas, 

for me the following steps reproduce the issue: 

support/scripts/scancpan XML-Parser
[Enable the perl-xml-parser module in the config]
make

Then on the target: 

perl -e "require XML::Parser"


The buildroot configuration should not matter as long as the target has
a different architecture (eg: ARM ). If it is the same architecture as
the host, it could produce binary compatible modules by accident. 

You could even verify the presence of this issue by just compiling the
perl-xml-parser module (any architecture): If you look at the build
output, you will see that the Makefile uses the configuration and
destination paths of the host perl. 

/Arne

  reply	other threads:[~2016-07-12  9:04 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
2016-07-12  8:15     ` Arne Caspari
2016-07-12  8:56       ` Thomas Petazzoni
2016-07-12  9:04         ` Arne Caspari [this message]
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=20160712110438.62d56296@gmail.com \
    --to=arne.caspari@gmail.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