From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] install uClibc daily snapshot failes
Date: Fri, 19 Jan 2007 20:44:53 +0100 [thread overview]
Message-ID: <20070119194453.GB19990@aon.at> (raw)
In-Reply-To: <200701191651.07462.claus.klein@arcormail.de>
On Fri, Jan 19, 2007 at 04:51:07PM +0100, Claus Klein wrote:
>On Thursday 18 January 2007 11:29, Bernhard Fischer wrote:
>> >> What is your echo $LD_LIBRARY_PATH ?
>> >>
>> >>
>> >claus at P3linux:~/src/buildroot> echo $LD_LIBRARY_PATH
>> >/usr/lib/qt3/lib:/usr/lib/qt3/lib:/usr/lib/qt3/lib:/usr/lib/qt3/lib:
>> --------------------------------------------------------------------^
>>
>> fix your LD_LIBRARY_PATH, no patch needed.
>>
>> HTH,
>>
>>
>Hi,
>
>thanks for your help, you are right.
>
>I din't know that the tailing ':' is the same as ':.'
^: == :$ == :: == :.:
Same for PATH.
>
>I'm working with OpenSuse 10.1 and I can't find the config file, which writes this LD_LIBRARY_PATH.
>While about 2 years working with buildrout I had no problem with my LD_LIBRARY_PATH!
.profile, .bashrc and /etc/sysconfig come to mind.
IMO it is hazardous to have CWD in PATH and the same holds true for the
ld lib path. If you can convince anybody else to apply your patch, then
ok, but i will not apply it since this just means that you risk breakage
anywhere else that may trigger trouble like the one you experienced.
>
>I would like to hear that the Makefile will be changed to my version.
>This works always!
>
>
>PS: There is no note about LD_LIBRARY_PATH in the buildroot docu!
I've added checks to dependencies.sh as you may have seen.
Please fix your pathes. Thanks for your understanding and kind regards,
prev parent reply other threads:[~2007-01-19 19:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 7:33 [Buildroot] install uClibc daily snapshot failes Claus Klein
2007-01-17 18:13 ` Bernhard Fischer
2007-01-17 20:14 ` Claus Klein
2007-01-18 10:29 ` Bernhard Fischer
2007-01-19 15:51 ` Claus Klein
2007-01-19 19:44 ` Bernhard Fischer [this message]
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=20070119194453.GB19990@aon.at \
--to=rep.dot.nop@gmail.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