Commit 0fdebf99 by Phil Edwards

index.html (#3.6): Rewrap and close <a href> tags.

2002-03-19  Phil Edwards  <pme@gcc.gnu.org>

	* docs/html/faq/index.html (#3.6):  Rewrap and close <a href> tags.
	* docs/html/faq/index.txt:  Regenerate.

From-SVN: r51038
parent 85763cee
2002-03-19 Phil Edwards <pme@gcc.gnu.org>
* docs/html/faq/index.html (#3.6): Rewrap and close <a href> tags.
* docs/html/faq/index.txt: Regenerate.
2002-03-19 Steve Ellcey <sje@cup.hp.com> 2002-03-19 Steve Ellcey <sje@cup.hp.com>
* acinclude.m4 (GLIBCPP_ENABLE_LIBUNWIND_EXCEPTIONS): Define * acinclude.m4 (GLIBCPP_ENABLE_LIBUNWIND_EXCEPTIONS): Define
......
...@@ -61,7 +61,7 @@ ...@@ -61,7 +61,7 @@
<li><a href="#3_4">I can't use 'long long' on Solaris</a> <li><a href="#3_4">I can't use 'long long' on Solaris</a>
<li><a href="#3_5"><code>_XOPEN_SOURCE</code> / <li><a href="#3_5"><code>_XOPEN_SOURCE</code> /
<code>_GNU_SOURCE</code> / etc is always defined</a> <code>_GNU_SOURCE</code> / etc is always defined</a>
<li><a href="#3_6">OS X ctype.h is broken! How can I hack around it? <li><a href="#3_6">OS X ctype.h is broken! How can I hack it?</a>
</ol> </ol>
<li><a href="#4_0">Known Bugs and Non-Bugs</a> <li><a href="#4_0">Known Bugs and Non-Bugs</a>
...@@ -470,11 +470,11 @@ which is no longer available, thanks deja...--> ...@@ -470,11 +470,11 @@ which is no longer available, thanks deja...-->
</p> </p>
<hr> <hr>
<h2><a name="3_6">3.6 OS X ctype.h is broken! How can I hack around it?</h2> <h2><a name="3_6">3.6 OS X ctype.h is broken! How can I hack it?</a></h2>
<p>This is a long-standing bug in the OS X support. Fortunately, <p>This is a long-standing bug in the OS X support. Fortunately,
the patch is quite simple, and well-known. Here's a link to the the patch is quite simple, and well-known.
solution: <a href="http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html"> Here's a
<a href="http://gcc.gnu.org/ml/gcc/2002-03/msg00817.html">yay!</a> link to the solution.</a>
</p> </p>
<hr> <hr>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment