From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18194 invoked by alias); 10 Mar 2005 15:34:31 -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 18115 invoked from network); 10 Mar 2005 15:34:24 -0000 Received: from unknown (HELO relay2.seleniacomms.com) (81.120.201.9) by sourceware.org with SMTP; 10 Mar 2005 15:34:24 -0000 Received: from gesss008 ([10.31.237.14]) by relay2.seleniacomms.com (8.12.11/8.12.11) with ESMTP id j2AFY0Kp007679 for ; Thu, 10 Mar 2005 16:34:01 +0100 (CET) Subject: Linking against shared library linked to another shared one, please help To: binutils@sources.redhat.com Message-ID: From: matteo.pampolini@seleniacomms.com Date: Thu, 10 Mar 2005 15:34:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-SW-Source: 2005-03/txt/msg00301.txt.bz2 Hi there, I know this topic was already discussed on this mailing list, but the answers I found didn't satisfy my issue. 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. Could please someone help me? Many thanks in advance, Matteo.