From: Andrew Roberts <andrewm.roberts@sky.com>
To: gcc@gcc.gnu.org
Subject: Re: Broken links in INSTALL/specific.html
Date: Tue, 01 May 2018 09:43:00 -0000 [thread overview]
Message-ID: <2d2fc215-d59e-77a5-9b3e-793c0a23678d@sky.com> (raw)
In-Reply-To: <20180501072701.GJ8577@tucnak>
The reason I was looking at the versions in the RC tarball was that I
have never been clear as to what release the website
install/prerequisite/target info actually applies to.
It would be much better if this info was on a per release basis on the
web site, like the changelog and manuals. Thus any target
specific stuff which was removed wouldn't affect older releases
documentation.
Speaking of manuals, it might be worth documenting the make commands for
the documentation (make html, install-html and pdf, install-pdf) on the
build.html page.
The documentation can only get checked before the release if people are
aware how to build it.
Andrew
On 01/05/18 08:27, Jakub Jelinek wrote:
> Hi!
>
> PR web/85578 complains about broken links in INSTALL/specific.html inside of
> the rc tarballs, I've looked at past releases and at least the releases I've
> checked (4.7.0, 6.1, 7.1, 7.3, 8.1rc2) all have the broken links,
> e.g.
> <a href="#aarch64-x-x">aarch64*-*-*</a>
> and
> <a name="aarch64_002dx_002dx"></a><a name="aarch64_002a_002d_002a_002d_002a"></a>
> <h3 class="heading">aarch64*-*-*</h3>
> Looking at online docs, they are ok.
>
> I think this has been fixed for the online docs with:
> Index: preprocess
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/bin/preprocess,v
> retrieving revision 1.38
> retrieving revision 1.39
> diff -u -p -r1.38 -r1.39
> --- preprocess 28 Aug 2003 13:05:38 -0000 1.38
> +++ preprocess 5 Sep 2004 21:50:02 -0000 1.39
> @@ -144,7 +144,10 @@ process_file()
> cat $STYLE > $TMPDIR/input
> printf '<set-var MHTML::INCLUDE-PREFIX="%s">\n' `pwd` >> $TMPDIR/input
> cat $f >> $TMPDIR/input
> - ${MHC} $TMPDIR/input > $TMPDIR/output
> + # Use sed to work around makeinfo 4.7 brokenness.
> + ${MHC} $TMPDIR/input \
> + | sed -e 's/_002d/-/g' -e 's/_002a/*/g' \
> + > $TMPDIR/output
>
> # Copy the page only if it's new or there has been a change, and,
> # first of all, if there was no problem when running MetaHTML.
>
> revision 1.39
> date: 2004/09/05 21:50:02; author: gerald; state: Exp; lines: +4 -1
> Use sed to work around makeinfo 4.7 brokenness.
>
> Isn't this something we should be doing in gcc/doc/install.texi2html
> too (or somewhere else)?
>
> Bugzilla is down, so can't discuss it there...
>
> Jakub
>
prev parent reply other threads:[~2018-05-01 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 7:27 Jakub Jelinek
2018-05-01 9:43 ` Andrew Roberts [this message]
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=2d2fc215-d59e-77a5-9b3e-793c0a23678d@sky.com \
--to=andrewm.roberts@sky.com \
--cc=gcc@gcc.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).