Replace the use of <a name=...> by ids. Remove the id of "bugreport" which was only used by GCC < 2.95.3.
A number of cases here required special attention such as the very first one which originally read <a name="general"></a> <h1>General information</h1> Committed. Gerald Index: faq.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v retrieving revision 1.227 diff -u -r1.227 faq.html --- faq.html 2 Jun 2018 21:16:10 -0000 1.227 +++ faq.html 26 Aug 2018 16:40:56 -0000 @@ -57,12 +57,9 @@ <hr /> -<a name="general"></a> -<h1>General information</h1> +<h1 id="general">General information</h1> -<!-- The "bugreport" anchor was used in ICE messages of GCC < 2.95.3. --> -<h2 id="bugreport"><a name="support">How do I get a bug fixed or - a feature added?</a></h2> +<h2 id="support">How do I get a bug fixed or a feature added?</h2> <p>There are lots of ways to get something fixed. The list below may be incomplete, but it covers many of the common cases. These are listed @@ -94,7 +91,7 @@ </ul> <hr /> -<h2><a name="platforms">Does GCC work on my platform?</a></h2> +<h2 id="platforms">Does GCC work on my platform?</h2> <p>The host/target specific installation notes for GCC include information about known problems with installing or using GCC on particular platforms. @@ -105,10 +102,9 @@ for several versions of GCC are also available at the web site.</p> <hr /> -<a name="installation"></a> -<h1>Installation</h1> +<h1 id="installation">Installation</h1> -<h2><a name="multiple">How to install multiple versions of GCC</a></h2> +<h2 id="multiple">How to install multiple versions of GCC</h2> <p>It may be desirable to install multiple versions of the compiler on the same system. This can be done by using different prefix paths at @@ -168,7 +164,7 @@ <code>/usr/local/bin/gcc</code>.</p> <hr /> -<h2><a name="rpath">Dynamic linker is unable to find GCC libraries</a></h2> +<h2 id="rpath">Dynamic linker is unable to find GCC libraries</h2> <p>This problem manifests itself by programs not finding shared libraries they depend on when the programs are started. (This @@ -204,7 +200,7 @@ <hr /> -<h2><a name="gas">GCC can not find GNU as/GNU ld</a></h2> +<h2 id="gas">GCC can not find GNU as/GNU ld</h2> <p>GCC searches the PATH for an assembler and a linker, but it only does so after searching a directory list hard-coded in the GCC executables. Since, on most platforms, the hard-coded list includes @@ -240,7 +236,7 @@ specified filenames exist.</p> <hr /> -<h2><a name="environ">cpp: Usage:... Error</a></h2> +<h2 id="environ">cpp: Usage:... Error</h2> <p>If you get an error like this when building GCC (particularly when building __mulsi3), then you likely have a problem with your environment variables.</p> @@ -257,11 +253,10 @@ <hr /> -<a name="testsuite"></a> -<h1>Testsuite problems</h1> +<h1 id="testsuite">Testsuite problems</h1> -<h2><a name="testoptions">How do I pass flags like - <code>-fnew-abi</code> to the testsuite?</a></h2> +<h2 id="testoptions">How do I pass flags like <code>-fnew-abi</code> to +the testsuite?</h2> <p>If you invoke <code>runtest</code> directly, you can use the <code>--tool_opts</code> option, e.g:</p> @@ -275,7 +270,7 @@ </pre> <hr /> -<h2><a name="multipletests"> How can I run the testsuite with multiple options? </a></h2> +<h2 id="multipletests"> How can I run the testsuite with multiple options? </h2> <p>If you invoke <code>runtest</code> directly, you can use the <code>--target_board</code> option, e.g:</p> @@ -295,11 +290,10 @@ <hr /> -<a name="misc"></a> -<h1>Miscellaneous</h1> +<h1 id="misc">Miscellaneous</h1> -<h2><a name="friend">Friend Templates</a></h2> +<h2 id="friend">Friend Templates</h2> <p>In order to make a specialization of a template function a friend of a (possibly template) class, you must explicitly state that the @@ -354,7 +348,7 @@ <hr /> -<h2><a name="dso"><code>dynamic_cast</code>, <code>throw</code>, <code>typeid</code> don't work with shared libraries</a></h2> +<h2 id="dso"><code>dynamic_cast</code>, <code>throw</code>, <code>typeid</code> don't work with shared libraries</h2> <p>The new C++ ABI in the GCC 3.0 series uses address comparisons, rather than string compares, to determine type equality. This leads @@ -413,7 +407,7 @@ "<code>-Bsymbolic</code>" flags.</p> <hr /> -<h2><a name="generated_files">Why do I need autoconf, bison, xgettext, automake, etc?</a></h2> +<h2 id="generated_files">Why do I need autoconf, bison, xgettext, automake, etc?</h2> <p>If you're using diffs up dated from one snapshot to the next, or if you're using the SVN repository, you may need several additional programs @@ -436,7 +430,7 @@ <hr /> -<h2><a name="picflag-needed">Why can't I build a shared library?</a></h2> +<h2 id="picflag-needed">Why can't I build a shared library?</h2> <p>When building a shared library you may get an error message from the linker like `assert pure-text failed:' or `DP relative code in file'.</p> @@ -459,7 +453,7 @@ <hr /> -<h2><a name="vtables">When building C++, the linker says my constructors, destructors or virtual tables are undefined, but I defined them</a></h2> +<h2 id="vtables">When building C++, the linker says my constructors, destructors or virtual tables are undefined, but I defined them</h2> <p>The ISO C++ Standard specifies that all virtual methods of a class that are not pure-virtual must be defined, but does not require any
