From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Glibc LD_LIBRARAY_PATH error
Date: Wed, 2 Jul 2014 04:53:07 -0500 [thread overview]
Message-ID: <20140702045307.29f2719b@core2quad.morethan.org> (raw)
In-Reply-To: <53B3AB05.7050503@mind.be>
On Wed, 02 Jul 2014 08:47:33 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > Even a further out use case -
> > The applications requiring a LD_LIBRARY_PATH setting, where the
> > application(s) are used in a POST_**_SCRIPT, but the source isn't
> > available to build-in the appropriate DT_RUNPATH/DT_RPATH?
>
> To be honest, I think that use case is so far out that we don't need
> to consider it, and anyway the user has two easy solutions:
>
> - don't use a POST_**_SCRIPT but wrap something around the Makefile;
>
> - create a wrapper for the binaries that require LD_LIBRARY_PATH
> (like java apps typically do).
>
That all sounds reasonable to me.
Call this case "too far out" to consider,
or considered and tossed.
Mike
prev parent reply other threads:[~2014-07-02 9:53 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
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 [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=20140702045307.29f2719b@core2quad.morethan.org \
--to=minimod@morethan.org \
--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