From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error
Date: Sat, 28 Jun 2014 00:01:26 +0200 [thread overview]
Message-ID: <20140628000126.4bfd6329@free-electrons.com> (raw)
In-Reply-To: <CAMhj5sakLa9ROf4RVO2N1rhRx+4du=j3X8OL5rLVRAUQRnFS+Q@mail.gmail.com>
Dear Panahi Parsa,
On Sat, 28 Jun 2014 00:58:31 +0430, Panahi Parsa wrote:
> *** These auxiliary programs are missing or incompatible versions: makeinfo
> autoconf
> *** some features will be disabled.
> *** Check the INSTALL file for required versions.
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the environment variable
> *** and run configure again.
> make: ***
> [/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/.stamp_configured]
> Error 1
>
> parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$
>
> It seems that I should change LD_LIBARAY_PATH to include glibc environment
> variables !! Since I'm new to buildroot I don't know how I should do this.
>
> Is there some one who can tell me the steps to solve this problem ?
Can you post the output of the "env" command in the terminal you used
Buildroot?
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-06-27 22:01 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 [this message]
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
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=20140628000126.4bfd6329@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.