From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error
Date: Tue, 1 Jul 2014 22:07:03 +0200 [thread overview]
Message-ID: <20140701220703.0fa13b8a@free-electrons.com> (raw)
In-Reply-To: <53B2F9E1.7080609@mind.be>
Dear Arnout Vandecappelle,
On Tue, 01 Jul 2014 20:11:45 +0200, Arnout Vandecappelle wrote:
> >> > my problem was solved by your solution I mean using "unset LD_LIBRARY_PATH"
> > Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH from our
> > main Makefile. Probably we should just do it.
>
> I could imagine an ancient build host where the developer has to build his own
> python2.7 or other buildroot-dependencies. Not really realistic, though, because
> then the executable should just set its DT_RPATH/DT_RUNPATH.
Yes.
> Also, we already have a check for LD_LIBRARY_PATH in dependencies.sh. It just
> doesn't check for empty path elements, only for . path elements.
Well, the idea would be to get rid of this check entirely, and replace
it by a simple unexport in the main Makefile.
What do you think?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-01 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 20:28 [Buildroot] Glibc LD_LIBRARAY_PATH error Panahi Parsa
2014-06-27 22:01 ` Thomas Petazzoni
2014-06-28 4:45 ` Panahi Parsa
2014-06-28 6:36 ` Thomas Petazzoni
2014-06-28 14:25 ` Panahi Parsa
2014-06-28 14:28 ` Thomas Petazzoni
2014-06-28 15:12 ` Panahi Parsa
2014-06-28 15:36 ` Panahi Parsa
2014-06-28 15:44 ` Thomas Petazzoni
2014-07-01 18:11 ` Arnout Vandecappelle
2014-07-01 20:07 ` Thomas Petazzoni [this message]
2014-07-01 21:09 ` Mike Zick
2014-07-02 6:47 ` Arnout Vandecappelle
2014-07-02 9:53 ` Mike Zick
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=20140701220703.0fa13b8a@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 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.