From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: brobecker@adacore.com, drow@false.org, mark.kettenis@xs4all.nl,
gdb-patches@sourceware.org
Subject: Re: [rfc] Clarify shared library warning
Date: Fri, 13 Oct 2006 15:10:00 -0000 [thread overview]
Message-ID: <uwt74i747.fsf@gnu.org> (raw)
In-Reply-To: <jefydtpp79.fsf@sykes.suse.de> (message from Andreas Schwab on Thu, 12 Oct 2006 16:46:02 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Cc: Joel Brobecker <brobecker@adacore.com>, drow@false.org,
> mark.kettenis@xs4all.nl, gdb-patches@sourceware.org
> Date: Thu, 12 Oct 2006 16:46:02 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > How about this, then:
> >
> > warning: .dynamic section for "/lib/libc.so.6" is not at the expected address
> > (wrong library or library version mismatch?)
>
> Isn't "wrong library" a superset of "library version mismatch"?
It is, but messages to users don't need such mathematical rigour. I
imagine some users won't immediately realize that ``wrong library''
might mean libc.so.6 instead of libc.so.7; ``version mismatch'' goes a
long way towards spelling out that possibility, IMO.
next prev parent reply other threads:[~2006-10-13 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 14:52 Daniel Jacobowitz
2006-10-10 21:28 ` Eli Zaretskii
2006-10-10 21:34 ` Joel Brobecker
2006-10-11 13:38 ` Daniel Jacobowitz
2006-10-11 16:09 ` Joel Brobecker
2006-10-11 20:32 ` Mark Kettenis
2006-10-11 20:39 ` Daniel Jacobowitz
2006-10-11 20:49 ` Mark Kettenis
2006-10-11 20:51 ` Daniel Jacobowitz
2006-10-12 4:29 ` Eli Zaretskii
2006-10-12 5:52 ` Joel Brobecker
2006-10-12 6:55 ` Eli Zaretskii
2006-10-12 14:39 ` Joel Brobecker
2006-10-12 14:46 ` Andreas Schwab
2006-10-13 15:10 ` Eli Zaretskii [this message]
2006-10-13 15:18 ` Daniel Jacobowitz
2006-10-17 20:53 ` Daniel Jacobowitz
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=uwt74i747.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=schwab@suse.de \
/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