From: Ian Lance Taylor <ian@airs.com>
To: rth@cygnus.com
Cc: jj@sunsite.ms.mff.cuni.cz, binutils@sourceware.cygnus.com
Subject: Re: [RFC] Adding --skip-mismatch option to ld
Date: Thu, 01 Jul 1999 00:00:00 -0000 [thread overview]
Message-ID: <19990609234359.3086.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990609162034.A16899@cygnus.com>
Date: Wed, 9 Jun 1999 16:20:34 -0700
From: Richard Henderson <rth@cygnus.com>
On Wed, Jun 09, 1999 at 06:52:46PM -0400, Ian Lance Taylor wrote:
> If --skip-mismatch is the default, the linker finds an entirely
> different libfoo.a later in the search path. The link succeeds, but
> I'm using the wrong code. My changes aren't in there, and I can't
> figure out why. I have a serious debugging problem ahead of me.
Perhaps --skip-mismatch, while the default, also warns by default,
to be supressed by --no-warn-mismatch (for masochists)?
I could accept such a patch.
However, I continue to believe that it is better to avoid increasing
the confusion. Making the linker smarter often seems like a sensible
approach, but my experience is that it tends to lead to unanticipated
trouble. It's always better to have simple tools with transparent
behaviour. There is a place for smart programs that try to guess what
you mean, but not in the binutils.
Ian
next prev parent reply other threads:[~1999-07-01 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 0:00 Jakub Jelinek
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Jakub Jelinek
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Jakub Jelinek
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Jakub Jelinek
1999-07-01 0:00 ` Ian Lance Taylor
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor [this message]
1999-07-01 0:00 ` H.J. Lu
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=19990609234359.3086.qmail@daffy.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
--cc=rth@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).