This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
[Doc patch] Small changes to abi.html
- From: Paolo Carlini <pcarlini at suse dot de>
- To: libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Fri, 27 May 2005 20:06:29 +0200
- Subject: [Doc patch] Small changes to abi.html
Hi everyone,
a few days ago, while adding the baselines for powerpc64 I noticed that
check_abi may (spuriously) fail if special --with-cpu options are passed
at configure time, simply because the layout of directories is
completely different. Also, can - correctly - fail if the locale model
is different from the default. A notice seems in order (*): I don't
think we say explicitly the above anywhere. What do you think about the
below? In case, please feel free to suggest improvements to the english! ;)
Paolo.
(*) Maybe we can also substantively improve the multilib thing, but not
tomorrow ;)
/////////////
2005-05-27 Paolo Carlini <pcarlini@suse.de>
* docs/html/abi.html: Mention 3.4.0 as the current baseline; add
a notice about the configure options.
Index: abi.html
===================================================================
RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/abi.html,v
retrieving revision 1.6
diff -u -r1.6 abi.html
--- abi.html 12 Jul 2004 23:40:48 -0000 1.6
+++ abi.html 27 May 2005 17:56:14 -0000
@@ -734,11 +734,18 @@
<p>
This is a proactive check the library ABI. Currently, exported symbol
names that are either weak or defined are checked against a last known
-good baseline. Currently, this baseline is keyed off of 3.2.0
+good baseline. Currently, this baseline is keyed off of 3.4.0
binaries, as this was the last time the .so number was incremented. In
addition, all exported names are demangled, and the exported objects
are checked to make sure they are the same size as the same object in
the baseline.
+
+Notice that each baseline is relative to a <strong>default</strong>
+configured library and compiler: in particular, if options such as
+--enable-clocale, or --with-cpu, in case of multilibs, are used at
+configure time, the check may fail, either because of substantive
+differences or because of limitations of the current checking
+machinery.
</p>
<p>