From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error
Date: Sat, 28 Jun 2014 08:36:12 +0200 [thread overview]
Message-ID: <20140628083612.167f7b88@free-electrons.com> (raw)
In-Reply-To: <CAMhj5sZkdpe+mrTzvxqrwK=-tOoyG4nvobM48PJJpw3oFcb5CA@mail.gmail.com>
Dear Panahi Parsa,
On Sat, 28 Jun 2014 09:15:18 +0430, Panahi Parsa wrote:
> LD_LIBRARY_PATH=/opt/pylon3/lib64:/opt/pylon3/genicam/bin/Linux64_x64:/opt/pylon3/genicam/bin/Linux64_x64/GenApi/Generic::/home/parsa/Software/OPENCV/build/lib:/usr/local/lib:/home/parsa/Software/OPENCV/build/lib
This LD_LIBRARY_PATH value, which has an empty member (notice the
double : in the middle of the variable), is probably was confuses the
glibc build system. Can you adjust your LD_LIBRARY_PATH to remove this
empty member, and restart the build from scratch ("make clean all"),
and let us know if that solves the problem? If it does, we'll add a
check to warn users about this problem.
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 6:36 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 [this message]
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
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=20140628083612.167f7b88@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