[gcc r15-1023] libstdc++: Update gcc.gnu.org links in FAQ to https
Gerald Pfeifer
gerald@gcc.gnu.org
Wed Jun 5 06:02:06 GMT 2024
https://gcc.gnu.org/g:35e453d9e17c299d58d5d2c9f44b4b4eec9867b6
commit r15-1023-g35e453d9e17c299d58d5d2c9f44b4b4eec9867b6
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Wed Jun 5 07:59:47 2024 +0200
libstdc++: Update gcc.gnu.org links in FAQ to https
libstdc++-v3:
* doc/xml/faq.xml: Move gcc.gnu.org to https.
* doc/html/faq.html: Regenerate.
Diff:
---
libstdc++-v3/doc/html/faq.html | 10 +++++-----
libstdc++-v3/doc/xml/faq.xml | 10 +++++-----
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index e84e455c4e9..dcb94ba67dc 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -268,7 +268,7 @@
Libstdc++ comes with its own validation testsuite, which includes
conformance testing, regression testing, ABI testing, and
performance testing. Please consult the
- <a class="link" href="http://gcc.gnu.org/install/test.html" target="_top">testing
+ <a class="link" href="https://gcc.gnu.org/install/test.html" target="_top">testing
documentation</a> for GCC and
<a class="link" href="manual/test.html" title="Testing">Testing</a> in the libstdc++
manual for more details.
@@ -458,14 +458,14 @@
<span class="command"><strong>g++ -E -dM -x c++ /dev/null</strong></span> to display
a list of predefined macros for any particular installation.
</p><p>This has been discussed on the mailing lists
- <a class="link" href="http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris" target="_top">quite a bit</a>.
+ <a class="link" href="https://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris" target="_top">quite a bit</a>.
</p><p>This method is something of a wart. We'd like to find a cleaner
solution, but nobody yet has contributed the time.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.darwin_ctype"></a><a id="q-darwin_ctype"></a><p><strong>4.4.</strong></p></td><td align="left" valign="top"><p>
Mac OS X <code class="filename">ctype.h</code> is broken! How can I fix it?
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-darwin_ctype"></a></td><td align="left" valign="top"><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>This answer is old and probably no longer be relevant.</p></div><p>
This was a long-standing bug in the OS X support. Fortunately, the
- <a class="link" href="http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html" target="_top">patch</a>
+ <a class="link" href="https://gcc.gnu.org/ml/gcc/2002-03/msg00817.html" target="_top">patch</a>
was quite simple, and well-known.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.threads_i386"></a><a id="q-threads_i386"></a><p><strong>4.5.</strong></p></td><td align="left" valign="top"><p>
Threading is broken on i386?
@@ -636,7 +636,7 @@
<code class="filename"><iterator></code> header),
then you will suddenly be faced with huge numbers of ambiguity
errors. This was discussed on the mailing list; Nathan Myers
- <a class="link" href="http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html" target="_top">sums
+ <a class="link" href="https://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html" target="_top">sums
things up here</a>. The collisions with vector/string iterator
types have been fixed for 3.1.
</p></td></tr><tr class="question"><td align="left" valign="top"><a id="faq.v2_headers"></a><a id="q-v2_headers"></a><p><strong>6.4.</strong></p></td><td align="left" valign="top"><p>
@@ -729,7 +729,7 @@
</p></td></tr><tr class="answer"><td align="left" valign="top"><a id="a-easy_to_fix"></a></td><td align="left" valign="top"><p>
If you have found a bug in the library and you think you have
a working fix, then send it in! The main GCC site has a page
- on <a class="link" href="http://gcc.gnu.org/contribute.html" target="_top">submitting
+ on <a class="link" href="https://gcc.gnu.org/contribute.html" target="_top">submitting
patches</a> that covers the procedure, but for libstdc++ you
should also send the patch to our mailing list in addition to
the GCC patches mailing list. The libstdc++
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 79edb02bec4..4888fa93ae9 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -313,7 +313,7 @@
Libstdc++ comes with its own validation testsuite, which includes
conformance testing, regression testing, ABI testing, and
performance testing. Please consult the
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/install/test.html">testing
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/install/test.html">testing
documentation</link> for GCC and
<link linkend="manual.intro.setup.test">Testing</link> in the libstdc++
manual for more details.
@@ -583,7 +583,7 @@
a list of predefined macros for any particular installation.
</para>
<para>This has been discussed on the mailing lists
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris">quite a bit</link>.
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris">quite a bit</link>.
</para>
<para>This method is something of a wart. We'd like to find a cleaner
solution, but nobody yet has contributed the time.
@@ -604,7 +604,7 @@
</note>
<para>
This was a long-standing bug in the OS X support. Fortunately, the
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html">patch</link>
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/ml/gcc/2002-03/msg00817.html">patch</link>
was quite simple, and well-known.
</para>
@@ -885,7 +885,7 @@
<filename class="headerfile"><iterator></filename> header),
then you will suddenly be faced with huge numbers of ambiguity
errors. This was discussed on the mailing list; Nathan Myers
- <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html">sums
+ <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/ml/libstdc++/2001-01/msg00247.html">sums
things up here</link>. The collisions with vector/string iterator
types have been fixed for 3.1.
</para>
@@ -1041,7 +1041,7 @@
<para>
If you have found a bug in the library and you think you have
a working fix, then send it in! The main GCC site has a page
- on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://gcc.gnu.org/contribute.html">submitting
+ on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://gcc.gnu.org/contribute.html">submitting
patches</link> that covers the procedure, but for libstdc++ you
should also send the patch to our mailing list in addition to
the GCC patches mailing list. The libstdc++
More information about the Gcc-cvs
mailing list