This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How do I link to a shared lib without having that lib'sdependencies (the way MS link does)

From: David Wuertele <dave-gnus at bfnet dot com>
To: binutils at sources dot redhat dot com
Date: Tue, 12 Aug 2003 10:48:39 -0700
Subject: Re: How do I link to a shared lib without having that lib'sdependencies (the way MS link does)
Cancel-lock: sha1:tM7JH1qHwa44+uy+jvQ30Fbimmk=
Organization: Berkeley Fluent Network
References: <m38ypz1udy.fsf@bfnet.com> <m38ypybzbn.fsf@gossamer.airs.com><20030812173950.GA24280@lucon.org>

ILT> I think this is a bug.  The GNU linker is reporting an error where it
ILT> should report a warning.
ILT> 
ILT> Any comments on this patch?

HJL> I prefer something like this.

<snipped out undefined_symbol warning code>

Why does this even have to be a warning?  The 'link' program in
Windows doesn't print a warning.

Dave

Follow-Ups:
- Re: How do I link to a shared lib without having that lib's dependencies (the way MS link does)
  - From: Ian Lance Taylor

References:
- How do I link to a shared lib without having that lib'sdependencies (the way MS link does)
  - From: David Wuertele
- Re: How do I link to a shared lib without having that lib's dependencies (the way MS link does)
  - From: Ian Lance Taylor
- Re: How do I link to a shared lib without having that lib's dependencies (the way MS link does)
  - From: H. J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]