From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 1 Jul 2014 22:07:03 +0200 Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error In-Reply-To: <53B2F9E1.7080609@mind.be> References: <20140628000126.4bfd6329@free-electrons.com> <20140628083612.167f7b88@free-electrons.com> <20140628162843.41a203d7@free-electrons.com> <20140628174420.2fd3ed86@free-electrons.com> <53B2F9E1.7080609@mind.be> Message-ID: <20140701220703.0fa13b8a@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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