From: Gavin Smith <gavinsmith0123@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Richard Stallman <rms@gnu.org>, bug-texinfo@gnu.org, gcc@gcc.gnu.org
Subject: Re: Makeinfo generates wrong link
Date: Mon, 3 Oct 2022 15:56:34 +0100 [thread overview]
Message-ID: <Yzr4Igz76hPvB+lh@starmint> (raw)
In-Reply-To: <CAH6eHdTX38zVrXvZ3yYV7iU+4hDGB7btuzqCXgf3TUJR+tYXdw@mail.gmail.com>
On Mon, Oct 03, 2022 at 08:31:06AM +0100, Jonathan Wakely wrote:
> On Mon, 3 Oct 2022 at 07:01, Gavin Smith via Gcc <gcc@gcc.gnu.org> wrote:
> >
> > On Sun, Oct 02, 2022 at 09:06:06PM -0400, Richard Stallman wrote:
> > > generates the following output:
> > >
> > > <li> Some macros are predefined on each kind of machine
> > > (see <a href="https://gcc.gnu.org/onlinedocs/gcc/System_002dspecific-Predefined-Macros.html#System_002dspecific-Predefined-Macros">System-specific Predefined Macros</a> in <cite>Using the GNU Compiler
> > > Collection</cite>). This allows you to provide code specially tuned for a
> > > particular machine.
> > >
> > > but that link is broken. The OP suggests this link
> > >
> > > https://gcc.gnu.org/onlinedocs/gcc-4.8.5/cpp/System-specific-Predefined-Macros.html
> > >
> > > may be correct.
> > >
> > > Where do those directory names come from? Is there a table in makeinfo
> > > that needs to be updated?
> > The gcc developers need to provide a stable, version-independent link
> > for the manual. This link would have worked in the past, but I don't
> > know how recently it broke.
>
> The URL https://gcc.gnu.org/onlinedocs/cpp/System-specific-Predefined-Macros.html
> has been stable for many years.
In that case it is the input that is wrong:
Some macros are predefined on each kind of machine
(@pxref{System-specific Predefined Macros, System-specific Predefined
Macros, System-specific Predefined Macros, gcc, Using the GNU Compiler
Collection}). This allows you to provide code specially tuned for a
particular machine.
It should be
Some macros are predefined on each kind of machine
(@pxref{System specific Predefined Macros, System specific Predefined
Macros, System-specific Predefined Macros, gcc, Using the GNU Compiler
Collection}). This allows you to provide code specially tuned for a
particular machine.
changing the hyphen to a space in "System specific".
next prev parent reply other threads:[~2022-10-03 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1of9uI-0004mn-Ep@fencepost.gnu.org>
2022-10-03 6:00 ` Gavin Smith
2022-10-03 7:31 ` Jonathan Wakely
2022-10-03 8:23 ` Jonathan Wakely
2022-10-03 14:56 ` Gavin Smith [this message]
2022-10-04 1:02 ` Richard Stallman
2022-10-04 4:45 ` Jacob Bachmeyer
2022-10-04 17:39 ` Richard Stallman
2022-10-04 19:41 ` Gavin Smith
2022-10-04 20:28 ` Jonathan Wakely
2022-10-10 22:03 ` Richard Stallman
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=Yzr4Igz76hPvB+lh@starmint \
--to=gavinsmith0123@gmail.com \
--cc=bug-texinfo@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=rms@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).