From: Eli Zaretskii <eliz@gnu.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org,
monaka@monami-software.com
Subject: Re: [doc] Avoid conflicts between gdb and cross-gdb.
Date: Thu, 07 Aug 2014 15:50:00 -0000 [thread overview]
Message-ID: <8338d8nvsc.fsf@gnu.org> (raw)
In-Reply-To: <5772813.BLhj1dYueK@vapier>
> From: Mike Frysinger <vapier@gentoo.org>
> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org, monaka@monami-software.com
> Date: Wed, 06 Aug 2014 20:21:13 -0400
>
> > Besides, why do that? The Info manual does not include any
> > system-specific information, it is valid for all supported systems.
> > So I see no reason to put it into a system-dependent place or call it
> > by system-dependent name.
>
> it's not system-dependent, but it is version dependent. reading the
> documentation for the native version can be wildly inaccurate than the
> documentation for the cross version. it's probably less of an issue for gdb
> as features/flags don't change wildly quickly, but it makes a huge difference
> for gcc (e.g. 4.7 to 4.8 to 4.9).
As I wrote elsewhere, Info doesn't support different versions of the
same manual installed on the same system, without some non-trivial
tinkering.
next prev parent reply other threads:[~2014-08-07 15:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 8:18 Masaki Muranaka
2014-08-01 15:07 ` Joel Brobecker
2014-08-02 12:58 ` Mike Frysinger
2014-08-06 13:24 ` Joel Brobecker
2014-08-06 17:05 ` Eli Zaretskii
2014-08-06 17:37 ` Joel Brobecker
2014-08-06 17:40 ` Eli Zaretskii
2014-08-06 19:53 ` Joel Brobecker
2014-08-06 20:05 ` Doug Evans
2014-08-06 21:34 ` Joel Brobecker
2014-08-07 15:43 ` Eli Zaretskii
2014-08-07 15:53 ` Joel Brobecker
2014-08-08 6:19 ` Mike Frysinger
2014-08-21 14:26 ` Pedro Alves
2014-08-21 15:00 ` Eli Zaretskii
2014-08-07 0:21 ` Mike Frysinger
2014-08-07 15:50 ` Eli Zaretskii [this message]
2014-08-08 2:53 ` Mike Frysinger
2014-08-08 6:05 ` Eli Zaretskii
2014-08-08 7:17 ` Mike Frysinger
2014-08-21 14:30 ` Pedro Alves
2014-08-06 22:55 ` Mike Frysinger
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=8338d8nvsc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.com \
--cc=vapier@gentoo.org \
/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