[Buildroot] ldconfig Support on Target

[Buildroot] ldconfig Support on Target

[John O'Sullivan]

Hi,
I have a buildroot 2017.02.4 based system. I have a number of binary only applications that I am trying to accommodate which have dynamic linkage.  I believe I would need ldconfig and associated environment to assist resolving the dependencies. I cannot see any options for ldconfig for target. Could someone clarify the situation.

Regards


________________________________

This email and any files transmitted with it are confidential and are intended for the sole use of the individual to whom they are addressed. Black Box Corporation reserves the right to scan all e-mail traffic for restricted content and to monitor all e-mail in general. If you are not the intended recipient or you have received this email in error, any use, dissemination or forwarding of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20171027/3a960428/attachment.html>

[Buildroot] ldconfig Support on Target

[Yann E. MORIN]

John, All,

On 2017-10-27 12:20 +0000, John O'Sullivan spake thusly:
> I have a buildroot 2017.02.4 based system. I have a number of binary
> only applications that I am trying to accommodate which have dynamic
> linkage.  I believe I would need ldconfig and associated environment
> to assist resolving the dependencies.

Then you believe wrongly. ;-)

> I cannot see any
> options for ldconfig for target. Could someone clarify the situation.

No, there is no ldconfig on the target, because it is not needed:
Buildroot onoly ever installs libraries in /lib and /usr/lib, both of
whioch are standard search paths for the dynamic linker, so it will
always find the libraries. So we need not create the ld cache at all.

Now, to see what libraries your binaries need, you can very easily do so
on your build machine:

    readelf -d your-binary |grep NEEDED

which will give you the list of libraries needed for that executable.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'