From: "b.n." <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "prelink" a dynamic library
Date: Fri, 03 Oct 2008 19:49:43 +0200 [thread overview]
Message-ID: <48E65B37.1080708@gmail.com> (raw)
In-Reply-To: <tkrat.1ac456949e063396@igpm.rwth-aachen.de>
Helmut Jarausch ha scritto:
> On 2 Oct, bzk0711@aim.com wrote:
>> On Wed, 01 Oct 2008 18:53:04 +0200 (CEST)
>> Helmut Jarausch <jarausch@igpm.rwth-aachen.de> wrote:
>>
>>> Hi,
>> Hello Helmut,
>>
>>> I want to create a shared library, say libULIB.so,
>>> which needs additional shared libraries, e.g. libmpfr.so and
>>> libgmp.so .
>>>
>>> My users only use the functions provided by libULIB.so.
>>>
>>> Is there a means to "prelink" libULIB.so, so that the libraries
>>> libmpfr.so and libgmp.so are not needed by the user?
>> You should be able to just provide the libraries to the linker when
>> linking your shared object. When *running* the application, your shared
>> object (i.e. the loader) should transitively pull in the libs on which
>> yours depends. You can check those dependencies using ldd <your-lib>.
>>
>> Hope this helps,
>> Patric
>
> Thanks Patric, but unfortunately that's not what I want.
> In this case, these "secondary" libraries (e.g. libmpfr.so and
> libgmp.so) have to be present on the target machines together
> with an 'rpath' if they are in non-standard directories.
>
> My aim was to let the linker generate a big library which
> obseletes the secondary libraries.
If I understand correctly, you want them to be statically linked.
m.
next prev parent reply other threads:[~2008-10-03 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 16:53 [gentoo-user] "prelink" a dynamic library Helmut Jarausch
2008-10-02 12:19 ` bzk0711
2008-10-03 10:21 ` Helmut Jarausch
2008-10-03 17:49 ` b.n. [this message]
2008-10-03 18:24 ` Paul Hartman
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=48E65B37.1080708@gmail.com \
--to=brullonulla@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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