From 52f0be3a933225429b9b59b58de4fe54c2b20a02 Mon Sep 17 00:00:00 2001 From: fanquake Date: Wed, 10 Mar 2021 14:31:10 +0800 Subject: compat: remove memcpy -> memmove backwards compatibility alias In glib 2.13 memcpy was changed such that the way it copied bytes was reversed. This caused all sorts of issues for existing software, which depended on the existing behavior (when they should have been using memmove). See: https://sourceware.org/bugzilla/show_bug.cgi?id=12518 https://bugzilla.redhat.com/show_bug.cgi?id=638477 Now that we require glibc 2.17+ (#17538), we should be well clear of having to maintain our memcpy -> memmove aliasing, which was introduced in #4339. --- src/Makefile.am | 1 - 1 file changed, 1 deletion(-) (limited to 'src/Makefile.am') diff --git a/src/Makefile.am b/src/Makefile.am index 56f561a172..583779e865 100644 --- a/src/Makefile.am +++ b/src/Makefile.am @@ -553,7 +553,6 @@ libbitcoin_util_a_SOURCES = \ support/lockedpool.cpp \ chainparamsbase.cpp \ clientversion.cpp \ - compat/glibc_sanity.cpp \ compat/glibcxx_sanity.cpp \ compat/strnlen.cpp \ fs.cpp \ -- cgit v1.2.3