public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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: <19990609041411.1632.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990608204932.E7246@cygnus.com>

   Date: Tue, 8 Jun 1999 20:49:32 -0700
   From: Richard Henderson <rth@cygnus.com>

   On Tue, Jun 08, 1999 at 05:31:44PM -0400, Ian Lance Taylor wrote:
   > 2) I don't understand why it's needed.  Changing the default search
   >    path, as is done by the first half of the patch, sounds like the
   >    right approach to me.  Irix faces these exact issues with its
   >    multiple ABIs, yet it does not need this option.

   That works for system directories, but not /usr/local/lib and other
   such places under user control.  One could argue that we simply need
   to teach old users new tricks.

I don't see how it works for /usr/local/lib anyhow.  If you expect to
find the library in /usr/local/lib, but the wrong library is there,
then as far as I can see you won't find the library at all.  If you
need to find it in some other directory, you will need to add a -L
option, and if you do that it will work anyhow.

Perhaps we can make gcc's multilib feature handle this somehow?

   > I don't think the option name --skip-mismatch is quite right.  That
   > seems too general for this.  How about something like
   > --skip-incompatible-archives?

   We already have --[no-]warn-mismatch that's tangentially related.
   That's presumably where Jakub got the name.

That makes sense.  I was thinking that --skip-mismatch was just for
archives, but technically it is for any file for which the linker
searches, so I suppose it is reasonable.

Ian

  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     ` Richard Henderson
1999-07-01  0:00     ` Ian Lance Taylor
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         ` 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
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=19990609041411.1632.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).