All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:55:47 +0200	[thread overview]
Message-ID: <20120328125547.6873d986@skate> (raw)
In-Reply-To: <CAFbHwiQUZKJeD-F2z_EnPC=QE-FhuRDb3bZUenEjmprJE6MPGw@mail.gmail.com>

Le Wed, 28 Mar 2012 11:40:00 +0100,
Will Newton <will.newton@gmail.com> a ?crit :

> Do you think that setting LD_LIBRARY_PATH in the way I suggested is
> unsafe? I had some concerns that it might affect the search path for
> libraries but I believe this is not an issue with a cross linker
> (according to the ld man page, I haven't checked the code), and it
> does not break any of the test builds I have done.

In the past, we had the problem that when we were building target
packages that required host utilities installed in $(HOST_DIR)/usr/bin,
those utilities were not able to find their libraries in
$(HOST_DIR)/usr/lib. We tried using LD_LIBRARY_PATH, but libtool used
it as the search path for libraries when compiling target stuff. So, we
decided to hardcode the correct rpath in all binaries built and
installed in $(HOST_DIR)/usr/bin.

So, yes, I believe that adding LD_LIBRARY_PATH is going to cause
problems, unless those problems have disappeared for some other reason.

See:

 c1b6242fdcf2cff7ebf09fec4cc1be58963e8427
 0d1830b07db4ebfd14e77a258de6fb391e57e960
 6b939d40f6a29a43277566adc9d4312d49cb3abf

For a history of what we tried on this topic.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-28 10: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
2012-03-28  9:32       ` Peter Korsgaard
2012-03-28 10:40         ` Will Newton
2012-03-28 10:55           ` Thomas Petazzoni [this message]
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=20120328125547.6873d986@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 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.