From: Richard Henderson <rth@cygnus.com>
To: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
Cc: 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: <19990607163551.B11123@cygnus.com> (raw)
In-Reply-To: <19990608001452.O949@mff.cuni.cz>
On Tue, Jun 08, 1999 at 12:14:52AM +0200, Jakub Jelinek wrote:
> In such a case, what would it do if --no-warn-mismatch is specified?
> Should it stop skipping the libraries and choose the first one in the search
> path, or should it continue skipping incompatible libraries, in which case
> if the user wanted to link against an incompatible library, he'd have to
> specify its full name including path?
My thinking is that the only way to link against an incompatible
library is to include it explicitly instead of by `-l'.
> I don't know much about what are people using --no-warn-mismatch for and
> what tasks are they solving by it, so I cannot come to conclusion about the
> above question easily myself.
The only thing that even remotely comes to mind is a hetrogenous
multi-cpu embedded system thing, wherein you're linking code for
each of the processors into a single rom image. I have no idea
whether this would actually work or not with just --no-warn-mismatch.
> I'd be very happy if this skipping on mismatch was the default mode of
> operation, just thought it would have lower chance of getting accepted.
I have no problem with it. I'm interested in hearing Ian's thoughts.
r~
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 [this message]
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
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=19990607163551.B11123@cygnus.com \
--to=rth@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=jj@sunsite.ms.mff.cuni.cz \
/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).