From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] skeleton: ld.so.conf include ld.so.conf.d/*.conf
Date: Tue, 14 Oct 2014 10:52:54 +0200 [thread overview]
Message-ID: <1496567.mjGe8T9Pom@sagittea> (raw)
In-Reply-To: <CAHXCMMLnGmthd4HwEsGGvxjfgfNs_RZHE-ZBWb9-1mBF1_VTXg@mail.gmail.com>
On Tuesday 14 October 2014 10:44:48 Samuel Martin wrote:
> On Tue, Oct 14, 2014 at 10:40 AM, J?r?me Pouiller <jezz@sysmic.org> wrote:
> > On Tuesday 14 October 2014 10:33:16 Samuel Martin wrote:
> >> On Tue, Oct 14, 2014 at 10:24 AM, J?r?me Pouiller <jezz@sysmic.org>
wrote:
> >> > On Tuesday 14 October 2014 10:03:41 Yann E. MORIN wrote:
> >> >> J?r?me, All,
> >> >>
> >> >> On 2014-10-13 09:55 +0200, J?r?me Pouiller spake thusly:
> >> >> > Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
> >> >> > ---
> >> >> >
> >> >> > system/skeleton/etc/ld.so.conf | 1 +
> >> >> > 1 file changed, 1 insertion(+)
> >> >> > create mode 100644 system/skeleton/etc/ld.so.conf
> >> >> >
> >> >> > diff --git a/system/skeleton/etc/ld.so.conf
> >> >> > b/system/skeleton/etc/ld.so.conf new file mode 100644
> >> >> > index 0000000..83327c0
> >> >> > --- /dev/null
> >> >> > +++ b/system/skeleton/etc/ld.so.conf
> >> >> > @@ -0,0 +1 @@
> >> >> > +include /etc/ld.so.conf.d/*.conf
> >> >>
> >> >> Are you sure this works with uClibc? Looking at the code of ldconfig
> >> >> from uClibc seems to imply it does not support including files.
> >> >
> >> > I admit I have not tested with uclibc.
> >> >
> >> > hmm... Suddenly, it is more complex to implement. I see two options:
> >> > * Provide /etc/ld.so.conf during toolchain build depending of libc.
> >> > * Add extra library paths directly in /etc/ld.so.conf instead of
> >> > adding
> >> > a
> >> >
> >> > file in /etc/ld.so.conf.d. However, modifying files during install step
> >> > is
> >> > error prone.
> >>
> >> or add a post-build hook for uclibc, which does:
> >> cat <target>/etc/ld.conf.d/* >> <target>/etc/ld.conf
> >
> > This will not been executed if an external toolchain is used.
>
> Why not?
> In case of external toolchain, we have to select what libc is used in
> the toolchain; so it should be ok.
Ok. I understood a "package post build hook", but you mean a "target finalize
hook".
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2014-10-14 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 7:55 [Buildroot] [PATCH 1/2] skeleton: ld.so.conf include ld.so.conf.d/*.conf Jérôme Pouiller
2014-10-13 7:55 ` [Buildroot] [PATCH 2/2] gst-fsl-plugins: fix plugin loading Jérôme Pouiller
2014-10-14 8:40 ` Yann E. MORIN
2014-10-14 8:03 ` [Buildroot] [PATCH 1/2] skeleton: ld.so.conf include ld.so.conf.d/*.conf Yann E. MORIN
2014-10-14 8:24 ` Jérôme Pouiller
2014-10-14 8:33 ` Samuel Martin
2014-10-14 8:40 ` Jérôme Pouiller
2014-10-14 8:44 ` Samuel Martin
2014-10-14 8:52 ` Jérôme Pouiller [this message]
2014-10-14 9:00 ` Samuel Martin
2014-10-14 8:37 ` Yann E. MORIN
2014-10-24 23:53 ` Yann E. MORIN
2014-10-25 16:23 ` Jérôme Pouiller
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=1496567.mjGe8T9Pom@sagittea \
--to=jezz@sysmic.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