From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error
Date: Sat, 28 Jun 2014 16:28:43 +0200 [thread overview]
Message-ID: <20140628162843.41a203d7@free-electrons.com> (raw)
In-Reply-To: <CAMhj5sbiKrQ7PkbrxXr=CK34x2LA2bFu95asfCv8iKS5UtEMiQ@mail.gmail.com>
Dear Panahi Parsa,
On Sat, 28 Jun 2014 18:55:53 +0430, Panahi Parsa wrote:
> I looked at my LD_LIBRARY_PATH variable which I've set in /etc/bash.bashrc
> and it is:
>
> export PYLON_ROOT=/opt/pylon3
> export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
> export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
>
> export
> LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic
>
> export LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib
If you really have this code, then LD_LIBRARY_PATH would be equal to
just /home/parsa/Softwares/OPENCV/build/lib, because this last command
overrides any previous value of LD_LIBRARY_PATH. So clearly, you have
other pieces of code that are touching LD_LIBRARY_PATH.
Can you try, within the Buildroot source directory:
unset LD_LIBRARY_PATH
make clean all
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-28 14:28 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 [this message]
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
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=20140628162843.41a203d7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox