From: Ian Lance Taylor <ian@airs.com>
To: matteo.pampolini@seleniacomms.com
Cc: binutils@sources.redhat.com
Subject: Re: Linking against shared library linked to another shared one, please help
Date: Thu, 10 Mar 2005 16:00:00 -0000 [thread overview]
Message-ID: <m38y4vv6dj.fsf@gossamer.airs.com> (raw)
In-Reply-To: <OF94DF21A7.7DE1B456-ONC1256FC0.0054A820-C1256FC0.005587B0@SeleniaComms.com>
matteo.pampolini@seleniacomms.com writes:
> Ok, suppose a C app links against shared libAAA that in turns links against
> libBBB:
> why should I tell app of libBBB presence?
>
> If I want to hide the implementation of libAAA and eventually later change
> it, I should be
> able to avoid putting this information inside app compilation process,
> isn't it?
>
> I had a look at ld man page in -rpath-link section, but it seems to me that
> it doesn't
> fit my needs.
Why not?
Ian
next prev parent reply other threads:[~2005-03-10 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 15:34 matteo.pampolini
2005-03-10 16:00 ` Ian Lance Taylor [this message]
2005-03-10 16:22 matteo.pampolini
2005-03-10 22:39 ` Ian Lance Taylor
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=m38y4vv6dj.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=binutils@sources.redhat.com \
--cc=matteo.pampolini@seleniacomms.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).