From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] microperl: install host-microperl in $(HOST_DIR)/opt/perl
Date: Wed, 28 Mar 2012 09:55:32 +0200 [thread overview]
Message-ID: <20120328095532.71abc612@skate> (raw)
In-Reply-To: <87fwctb4gn.fsf@macbook.be.48ers.dk>
Hello Peter,
Le Wed, 28 Mar 2012 08:54:32 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Thanks, but I have fixed it a bit differently instead:
>
> commit d0e5eb281f0e3b323ecb3446c1b16baf7f3baa69
> Author: Peter Korsgaard <jacmet@sunsite.dk>
> Date: Tue Mar 27 17:11:36 2012 +0200
Thanks, yes. As discussed on IRC, I haven't tested your change, but I
agree on the principle.
However, I am worried by the case reported by Will Newton in:
From: Will Newton <will.newton@gmail.com>
To: buildroot at busybox.net
Subject: [Buildroot] Host libxml-parser-perl build issue
Date: Mon, 26 Mar 2012 17:35:29 +0100
In his case, the microperl for the target was not selected, so the
host-microperl was not built, and still he was having issues.
Apparently, the problem is that host-libxml-parser-perl didn't pick up
the libexpat from the $(HOST_DIR). Normally, we build all binaries with
a rpath set to $(HOST_DIR)/usr/lib, but in the specific case of Perl
modules that use a native library such as libexpat, I am not sure how
we are supposed to tell Perl to build such modules with an rpath set.
The current workaround of Will is to pass the LD_LIBRARY_PATH
environment variable in TARGET_CONFIGURE_OPTS and TARGET_MAKE_ENV, but
I don't think this would work for all packages (I remember libtool
being confused by a LD_LIBRARY_PATH being set).
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-28 7:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 7:06 [Buildroot] [pull request] Pull request for branch for-2012.05/perl Thomas Petazzoni
2012-03-27 7:06 ` [Buildroot] [PATCH 1/2] microperl: fix MICROPERL_INSTALL_TARGET_CMDS Thomas Petazzoni
2012-03-28 6:28 ` Peter Korsgaard
2012-03-27 7:06 ` [Buildroot] [PATCH 2/2] microperl: install host-microperl in $(HOST_DIR)/opt/perl Thomas Petazzoni
2012-03-27 7:12 ` Thomas Petazzoni
2012-03-28 6:54 ` Peter Korsgaard
2012-03-28 7:55 ` Thomas Petazzoni [this message]
2012-03-28 9:32 ` Peter Korsgaard
2012-03-28 10:40 ` Will Newton
2012-03-28 10:55 ` Thomas Petazzoni
2012-03-28 12:47 ` Will Newton
2012-03-28 12:52 ` Thomas Petazzoni
2012-03-28 13:01 ` Will Newton
2012-03-28 13:10 ` Will Newton
2012-03-28 13:18 ` Thomas Petazzoni
2012-03-28 14:00 ` Will Newton
2012-03-28 15:46 ` 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=20120328095532.71abc612@skate \
--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