From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB
Date: Mon, 12 Mar 2012 12:33:22 +0100 [thread overview]
Message-ID: <20120312123322.230c968b@skate> (raw)
In-Reply-To: <3fb8fff01011dbe187d729419e8c6156@zacarias.com.ar>
Hello,
Le Mon, 12 Mar 2012 07:14:51 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> >> HOST_INTLTOOL_DEPENDENCIES = host-libxml-parser-perl
> >> -HOST_INTLTOOL_CONF_OPT = \
> >> - PERLLIB=$(HOST_DIR)/usr/lib/perl
> >
> > Has this been tested on a system where libxml-parser-perl is not
> > installed?
> >
> > Thomas
>
> That's easy to reproduce and yes, did so by doing "mv /usr/lib/perl5
> /usr/lib/perl5.oops"
> As long as your distro uses /usr/lib/perl5 and not /usr/lib/perl or
> some other directory of course, but the same thing applies anyway.
Yes, of course, I missed the fact that you were using a host-microperl,
which I guess it built to look in $(HOST_DIR)/usr/lib/perl by default.
This PERLLIB option is needed if you want to use the Perl provided by
the distro, and you need it to look into this specific place for Perl
modules.
As said in my other mail, I am not convinced we need host-microperl.
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-12 11:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 1:58 [Buildroot] microperl fixes and improvements Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB Gustavo Zacarias
2012-03-12 6:58 ` Thomas Petazzoni
2012-03-12 10:14 ` Gustavo Zacarias
2012-03-12 11:33 ` Thomas Petazzoni [this message]
2012-03-12 12:07 ` Gustavo Zacarias
2012-03-12 7:00 ` Thomas Petazzoni
2012-03-19 15:30 ` Thomas Petazzoni
2012-03-19 15:52 ` Gustavo Zacarias
2012-03-19 15:57 ` Thomas Petazzoni
2012-03-19 16:10 ` Gustavo Zacarias
2012-03-19 16:22 ` Peter Korsgaard
2012-03-19 16:38 ` Thomas Petazzoni
2012-03-12 1:58 ` [Buildroot] [PATCH 2/3] libxml-parser-perl: add missing dep and drop wrong paths Gustavo Zacarias
2012-03-12 7:01 ` Thomas Petazzoni
2012-03-12 9:49 ` Gustavo Zacarias
2012-03-12 7:46 ` Thomas Petazzoni
2012-03-12 10:07 ` Gustavo Zacarias
2012-03-12 11:31 ` Thomas Petazzoni
2012-03-12 11:46 ` Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 3/3] host-microperl: define module paths and other improvements Gustavo Zacarias
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=20120312123322.230c968b@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