backward/hash_set (g++ 4.3.0)
I'm testing Boost.Python compilation with the latest g++ 4.3.0 (svn rev 129691). It fails because ext/hash_set is not available. On 2007-10-18 it was moved to backward/hash_set (gcc svn rev 129442). The patch below restores the Boost.Python compilation. Is this an OK adjustment? Ralf Index: boost/config/stdlib/libstdcpp3.hpp =================================================================== --- boost/config/stdlib/libstdcpp3.hpp (revision 40556) +++ boost/config/stdlib/libstdcpp3.hpp (working copy) @@ -68,6 +68,11 @@ # define BOOST_HAS_SLIST # define BOOST_HAS_HASH # define BOOST_SLIST_HEADER <ext/slist> +# if defined(__GLIBCXX__) && __GLIBCXX__ < 20071018 // GCC >= 4.3.0 # define BOOST_HASH_SET_HEADER <ext/hash_set> # define BOOST_HASH_MAP_HEADER <ext/hash_map> +# else +# define BOOST_HASH_SET_HEADER <backward/hash_set> +# define BOOST_HASH_MAP_HEADER <backward/hash_map> +# endif #endif
On Oct 29, 2007, at 2:12 PM, Ralf W. Grosse-Kunstleve wrote:
I'm testing Boost.Python compilation with the latest g++ 4.3.0 (svn rev 129691). It fails because ext/hash_set is not available. On 2007-10-18 it was moved to backward/hash_set (gcc svn rev 129442). The patch below restores the Boost.Python compilation. Is this an OK adjustment?
You might want to hold off on this change... the GCC folks are reconsidering whether ext/hash_set will exist in 4.3.0 or not. - Doug
On Mon, Oct 29, 2007 at 11:12:57AM -0700, Ralf W. Grosse-Kunstleve wrote:
I'm testing Boost.Python compilation with the latest g++ 4.3.0
Index: boost/config/stdlib/libstdcpp3.hpp =================================================================== --- boost/config/stdlib/libstdcpp3.hpp (revision 40556) +++ boost/config/stdlib/libstdcpp3.hpp (working copy) @@ -68,6 +68,11 @@ # define BOOST_HAS_SLIST # define BOOST_HAS_HASH # define BOOST_SLIST_HEADER <ext/slist> +# if defined(__GLIBCXX__) && __GLIBCXX__ < 20071018 // GCC >= 4.3.0
A stupid question: Why do you use __GLIBCXX__ instead of __GNUC__ and __GNUC_MINOR__ as described on http://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html?
# define BOOST_HASH_SET_HEADER <ext/hash_set> # define BOOST_HASH_MAP_HEADER <ext/hash_map>
Is the location of hash_set a property of the glibc and not of the compiler or belong both together? I do not see how changing the path of a header file could cause a ABI bump of glibc ... Jens
participants (3)
-
Doug Gregor -
Jens Seidel -
Ralf W. Grosse-Kunstleve