NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
toolchain/54027: enabling real libstdc++ gnu.ver config.h processing has duplicate symbols
>Number: 54027
>Category: toolchain
>Synopsis: enabling real libstdc++ gnu.ver config.h processing has duplicate symbols
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: toolchain-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 01 05:50:00 +0000 2019
>Originator: matthew green
>Release: NetBSD 8.99.34
>Organization:
people's front against (bozotic) www (softwar foundation)
>Environment:
All
>Description:
the current libstdc++.so linking attempts to use the c++config.h
but it uses the wrong one, and ends up not having right checks
applied. i've fixed mknative-gcc to copy the un-processed
config.h as symver-config.h, but i need this patch to enable the
use of it as well:
Index: external/gpl3/gcc/dist/libstdc++-v3/config/abi/pre/gnu.ver
===================================================================
RCS file: /cvsroot/src/external/gpl3/gcc/dist/libstdc++-v3/config/abi/pre/gnu.ver,v
retrieving revision 1.1.1.6
diff -p -u -u -r1.1.1.6 gnu.ver
-
+++ external/gpl3/gcc/dist/libstdc++-v3/config/abi/pre/gnu.ver 1 Mar 2019 05:25:06 -0000
@@ -1007,7 +1007,10 @@ GLIBCXX_3.4 {
#ifdef HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT
# GLIBCXX_ABI compatibility only.
# std::string
+ # XXXMRG this causes dupe symbols on netbsd
+#if 0
_ZNKSs11_M_disjunctEPKc;
+#endif
_ZNKSs15_M_check_lengthE[jmy][jmy]PKc;
_ZNSs4_Rep26_M_set_length_and_sharableE*;
_ZNSs7_M_copyEPcPKc[jmy];
@@ -1015,7 +1018,10 @@ GLIBCXX_3.4 {
_ZNSs9_M_assignEPc[jmy]c;
# std::wstring
+ # XXXMRG this causes dupe symbols on netbsd
+#if 0
_ZNKSbIwSt11char_traitsIwESaIwEE11_M_disjunctEPKw;
+#endif
_ZNKSbIwSt11char_traitsIwESaIwEE15_M_check_lengthE[jmy][jmy]PKc;
_ZNSbIwSt11char_traitsIwESaIwEE4_Rep26_M_set_length_and_sharableE*;
_ZNSbIwSt11char_traitsIwESaIwEE7_M_copyEPwPKw[jmy];
>How-To-Repeat:
i plan to commit the above change and the processing, but we
should figure out why this is happening.
>Fix:
Home |
Main Index |
Thread Index |
Old Index