From 35e453d9e17c299d58d5d2c9f44b4b4eec9867b6 Mon Sep 17 00:00:00 2001 From: Gerald Pfeifer Date: Wed, 5 Jun 2024 07:59:47 +0200 Subject: [PATCH] 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. --- 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 e84e455c4e96..dcb94ba67dc7 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 - testing + testing documentation for GCC and Testing in the libstdc++ manual for more details. @@ -458,14 +458,14 @@ g++ -E -dM -x c++ /dev/null to display a list of predefined macros for any particular installation.

This has been discussed on the mailing lists - quite a bit. + quite a bit.

This method is something of a wart. We'd like to find a cleaner solution, but nobody yet has contributed the time.

4.4.

Mac OS X ctype.h is broken! How can I fix it?

Note

This answer is old and probably no longer be relevant.

This was a long-standing bug in the OS X support. Fortunately, the - patch + patch was quite simple, and well-known.

4.5.

Threading is broken on i386? @@ -636,7 +636,7 @@ <iterator> header), then you will suddenly be faced with huge numbers of ambiguity errors. This was discussed on the mailing list; Nathan Myers - sums + sums things up here. The collisions with vector/string iterator types have been fixed for 3.1.

6.4.

@@ -729,7 +729,7 @@

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 submitting + on submitting patches 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 79edb02bec4f..4888fa93ae92 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 - testing + testing documentation for GCC and Testing in the libstdc++ manual for more details. @@ -583,7 +583,7 @@ a list of predefined macros for any particular installation. This has been discussed on the mailing lists - quite a bit. + quite a bit. 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 @@ This was a long-standing bug in the OS X support. Fortunately, the - patch + patch was quite simple, and well-known. @@ -885,7 +885,7 @@ <iterator> header), then you will suddenly be faced with huge numbers of ambiguity errors. This was discussed on the mailing list; Nathan Myers - sums + sums things up here. The collisions with vector/string iterator types have been fixed for 3.1. @@ -1041,7 +1041,7 @@ 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 submitting + on submitting patches 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++ -- 2.47.2