Bug#667979: TokyoCabinet got endianness in DB wrong on both big- and little-endian architectures

2017-04-20 Thread Josh Littlefield
Just ran into this myself when I found TC DB files are not portable from CentOS. Really unsure why this change was added in the first place, since configure script has always auto-detected endianness and added swapping compile flags (-D_MYBIGEND) when needed. The TC file format specification is

Bug#667979: TokyoCabinet got endianness in DB wrong on both big- and little-endian architectures

2015-03-12 Thread Tobias Frost
Control: tags -1 -patch On Fri, 4 Oct 2013 15:13:04 +0200 Mathieu Malaterre ma...@debian.org wrote: tags 667979 patch thanks Moreless we would need an migration path, like patching tokyocabinet to automatically detect endianess and act accordingly (whatever this is; for sure this is not

Bug#667979: TokyoCabinet got endianness in DB wrong on both big- and little-endian architectures

2013-10-04 Thread Mathieu Malaterre
tags 667979 patch thanks Moreless we would need an migration path, like patching tokyocabinet to automatically detect endianess and act accordingly (whatever this is; for sure this is not a trivial thing ) Here is what I do in tifffile: DEB_HOST_ARCH_ENDIAN:=$(shell dpkg-architecture