From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3271 invoked by alias); 10 Mar 2005 16:00:47 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 2160 invoked from network); 10 Mar 2005 16:00:02 -0000 Received: from unknown (205.217.158.180) by sourceware.org with QMTP; 10 Mar 2005 16:00:02 -0000 Received: (qmail 25682 invoked by uid 10); 10 Mar 2005 16:00:01 -0000 Received: (qmail 12000 invoked by uid 500); 10 Mar 2005 15:59:52 -0000 Mail-Followup-To: binutils@sources.redhat.com, matteo.pampolini@seleniacomms.com To: matteo.pampolini@seleniacomms.com Cc: binutils@sources.redhat.com Subject: Re: Linking against shared library linked to another shared one, please help References: From: Ian Lance Taylor Date: Thu, 10 Mar 2005 16:00:00 -0000 In-Reply-To: Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-03/txt/msg00303.txt.bz2 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