Hi Fabian,
On Mon, Jan 07, 2019 at 02:27:58PM +0100, Fabian Klötzl wrote:
> mash internally uses MurmurHash 3 which is sensitive to the endianess. There
we have (at least):
med-team/centrifuge/third_party/MurmurHash3.cpp
med-team/centrifuge/third_party/MurmurHash3.h
med-team/diamond-aligner/src/util/algo/MurmurHash3.cpp
med-team/diamond-aligner/src/util/algo/MurmurHash3.h
med-team/khmer/third-party/smhasher/MurmurHash3.cc
med-team/khmer/third-party/smhasher/MurmurHash3.h
med-team/mash/src/mash/MurmurHash3.cpp
mash/src/mash/MurmurHash3.h
med-team/sga/src/Thirdparty/MurmurHash3.cpp
med-team/sga/src/Thirdparty/MurmurHash3.h
python-team/modules/python-murmurhash/murmurhash/MurmurHash3.cpp
python-team/modules/python-murmurhash/murmurhash/include/murmurhash/MurmurHash3.h
science-team/scikit-learn/sklearn/utils/src/MurmurHash3.cpp
science-team/scikit-learn/sklearn/utils/src/MurmurHash3.h
It seems to be time to package MurmurHash3 separately, isn't it?
Kind regards
Andreas.
--
http://fam-tille.de
