From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <binutils-return-28399-listarch-binutils=sources.redhat.com@sources.redhat.com>
Received: (qmail 1460 invoked by alias); 13 Aug 2003 16:35:47 -0000
Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:binutils-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/binutils/>
List-Post: <mailto:binutils@sources.redhat.com>
List-Help: <mailto:binutils-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: binutils-owner@sources.redhat.com
Received: (qmail 1451 invoked from network); 13 Aug 2003 16:35:46 -0000
Received: from unknown (63.201.54.26)
  by sources.redhat.com with QMTP; 13 Aug 2003 16:35:46 -0000
Received: (qmail 13233 invoked by uid 10); 13 Aug 2003 16:35:45 -0000
Received: (qmail 29045 invoked by uid 500); 13 Aug 2003 16:35:41 -0000
Mail-Followup-To: dave-gnus@bfnet.com,
  binutils@sources.redhat.com,
  nickc@redhat.com
To: Nick Clifton <nickc@redhat.com>
Cc: dave-gnus@bfnet.com, binutils@sources.redhat.com
Subject: Re: How do I link to a shared lib without having that lib's dependencies (the way MS link does)
References: <m38ypz1udy.fsf@bfnet.com> <m38ypybzbn.fsf@gossamer.airs.com>
	<20030812173950.GA24280@lucon.org> <m3ekzqah87.fsf@gossamer.airs.com>
	<20030812183514.GA25209@lucon.org> <20030812190614.GA25910@lucon.org>
	<m3y8xxmt6h.fsf@redhat.com>
From: Ian Lance Taylor <ian@airs.com>
Date: Wed, 13 Aug 2003 16:35:00 -0000
In-Reply-To: <m3y8xxmt6h.fsf@redhat.com>
Message-ID: <m38ypxseg2.fsf@gossamer.airs.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2003-08/txt/msg00207.txt.bz2

Nick Clifton <nickc@redhat.com> writes:

>   It seems to me however that having three different switches to
>   control the linker's behaviour with undefined references is a bit
>   much.

Take a look at the Solaris linker.  I think it supports something like
-Bundefined and maybe some other -B options along these lines.  Or it
might be -z something--I can't remember.

>   So for example we could have one switch, say,
>   --ignore-unresolved-symbols=<setting> which could take a number of
>   different values:
> 
>     all                  [ignore any unresolved reference]
>     none                 [do not ignore any unresolved reference]
>     in-shared-libraries  [references from one shared library to another]
>     in-object-files      [references in object files]

An orthogonal choice is whether the message should be a warning or an
error.  In a case of static linking, it should clearly be an error.
In other cases, it is less clear.

Ian