public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-10003] libstdc++: Fix hyperlink in docs
Date: Mon, 16 May 2022 14:10:21 +0000 (GMT)	[thread overview]
Message-ID: <20220516141021.63C20383D821@sourceware.org> (raw)

https://gcc.gnu.org/g:ae564e7003dea013a53fe47f702974d89d1d2065

commit r11-10003-gae564e7003dea013a53fe47f702974d89d1d2065
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon May 16 14:54:07 2022 +0100

    libstdc++: Fix hyperlink in docs
    
    libstdc++-v3/ChangeLog:
    
            * doc/xml/manual/prerequisites.xml: Fix attributes for external
            hyperlink.
            * doc/html/manual/setup.html: Regenerate.
    
    (cherry picked from commit 682e587f1021241758f7dfe0b22651008622a312)

Diff:
---
 libstdc++-v3/doc/html/manual/setup.html       | 2 +-
 libstdc++-v3/doc/xml/manual/prerequisites.xml | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/setup.html b/libstdc++-v3/doc/html/manual/setup.html
index 069354b8ce0..f27b8d806df 100644
--- a/libstdc++-v3/doc/html/manual/setup.html
+++ b/libstdc++-v3/doc/html/manual/setup.html
@@ -57,7 +57,7 @@
 	      Glibc already provides <code class="function">iconv</code> so you should
 	      not need libiconv anyway.
 	    </p></li><li class="listitem"><p>
-	    <a class="link" href="../">
+	    <a class="link" href="https://www.gnu.org/software/libiconv/#downloading" target="_top">
 	    Download</a> the libiconv sources and extract them into the
 	    top level of the GCC source tree, e.g.,
 	    </p><pre class="programlisting">
diff --git a/libstdc++-v3/doc/xml/manual/prerequisites.xml b/libstdc++-v3/doc/xml/manual/prerequisites.xml
index 8799487c821..f00979a1afa 100644
--- a/libstdc++-v3/doc/xml/manual/prerequisites.xml
+++ b/libstdc++-v3/doc/xml/manual/prerequisites.xml
@@ -71,7 +71,8 @@
 	  </listitem>
 	  <listitem>
 	    <para>
-	    <link linkend="https://www.gnu.org/software/libiconv/#downloading">
+	    <link xmlns:xlink="http://www.w3.org/1999/xlink"
+	      xlink:href="https://www.gnu.org/software/libiconv/#downloading">
 	    Download</link> the libiconv sources and extract them into the
 	    top level of the GCC source tree, e.g.,
 	    </para>


                 reply	other threads:[~2022-05-16 14:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220516141021.63C20383D821@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).