Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] ldconfig Support on Target
Date: Sun, 29 Oct 2017 08:56:06 +0100	[thread overview]
Message-ID: <20171029075606.GC2899@scaer> (raw)
In-Reply-To: <30ab70ac842c48ef8e6035cbc2c49cd4@PGHPRDEXCH02.corp.bbns.com>

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.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2017-10-29  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 12:20 [Buildroot] ldconfig Support on Target John O'Sullivan
2017-10-29  7:56 ` Yann E. MORIN [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=20171029075606.GC2899@scaer \
    --to=yann.morin.1998@free.fr \
    --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