public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: "Philippe De Muyter" <phdm@macqel.be>
To: dj@delorie.com (DJ Delorie)
Cc: gas2@cygnus.com
Subject: Re: why is an archive member linked in ?
Date: Mon, 29 Dec 1997 20:01:00 -0000	[thread overview]
Message-ID: <199712300401.FAA31778@mail.macqel.be> (raw)
In-Reply-To: <199712300324.WAA23012@delorie.com>

> 
> 
> > In the specific case I encountered, removing the module from the archive
> > made my link command succeed, while with the module in the archive my
> > link command failed because of some unresolved symbols in the module
> > that got linked in.
> 
> Sometimes, there might be more than one object that resolves a
> specific symbol.  If you take one out, the other gets used, and that
> changes everything.
> 
> For example, DJGPP has two math libraries.  One (libm.a) has a
> complete set of conforming (but slightly slower) functions, and the
> other (in libc.a) is smaller and faster, but less complete and less
> conforming.  If you link in libm.a, you get that set, but if you leave
> it out, the ones in libc.a get used.
> 

Thanks.  I already know that but that's the (slow and ugly) method I use
to find why an archive member causing a link error is linked in.  What I need
is a clean and fast method, e.g. a gld option or, better, a direct information
in the error message.

Philippe

  reply	other threads:[~1997-12-29 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-29 19:09 Philippe De Muyter
1997-12-29 19:24 ` DJ Delorie
1997-12-29 20:01   ` Philippe De Muyter [this message]
1997-12-29 20:09 ` 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=199712300401.FAA31778@mail.macqel.be \
    --to=phdm@macqel.be \
    --cc=dj@delorie.com \
    --cc=gas2@cygnus.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).