[Buildroot] [PATCH 1/2] skeleton: ld.so.conf include ld.so.conf.d/*.conf

Samuel Martin s.martin49 at gmail.com
Tue Oct 14 09:00:05 UTC 2014


On Tue, Oct 14, 2014 at 10:52 AM, Jérôme Pouiller <jezz at sysmic.org> wrote:
> 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 at 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 at 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 at 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".

Yes exactly.
Sorry for the confusion.

>
>
> --
> Jérôme Pouiller, Sysmic
> Embedded Linux specialist
> http://www.sysmic.fr



-- 
Samuel


More information about the buildroot mailing list