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: <19990608213144.561.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990607120530.A13793@cygnus.com>
Date: Mon, 7 Jun 1999 12:05:30 -0700
From: Richard Henderson <rth@cygnus.com>
On Fri, Jun 04, 1999 at 05:12:07PM +0200, Jakub Jelinek wrote:
> Now Solaris linker apparently skips a library in the search path if it is
> for the wrong architecture (=emulation) which makes a lot of sense to me,
> that's why I wrote the second part of this patch. I've made it optional and
> not default because it differs from the standard library path searching, on
> the other side without this any compilation with some wrong arch library in
> the search path before the correct arch one would die in error.
I don't see any need to make this optional. My preferred solution
would be to skip the library with a note written to the map file
to aid diagnosing user's problems.
Other comments?
I think it should be optional.
1) I think it's surprising. You can predict which files the linker is
going to happen based exclusively on the file name. Anything which
changes that can lead to confusion (e.g., the great confusion
surrounding the GNU/Linux /etc/ld.so.cache file).
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.
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?
Note that the patch changes ldfile_open_file_search. That routine is
used for anything which appears in an INPUT statement in a linker
script, which includes files which are not archives. I believe the
patch code in the case where the file is not an archive, because it
expects the architecture to be set before bfd_check_format is called
successfully.
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 ` H.J. Lu
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` Ian Lance Taylor [this message]
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
1999-07-01 0:00 ` Jakub Jelinek
1999-07-01 0:00 ` Richard Henderson
1999-07-01 0:00 ` 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=19990608213144.561.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).