Hi Aaron, Aaron M. Ucko, on 2021-09-19: > As of BLAST+ 2.10.0, makeblastdb defaults to making version 5 databases, > via the third-party LMDB library that uses an architecture-dependent > on-disk layout (differing between little-endian and big-endian systems; > I'm not sure offhand about 32-bit vs. 64-bit systems). TTBOMK, BLAST+ > is fine on either type of system as long as you don't try to mix and > match, so the bug is most likely in kleborate; please try directing > makeblastdb to produce traditional version 4 databases by invoking it > with the "-blastdb_version 4" flag. > > See also > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959587 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960756 > > and especially > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981293
This is amazing! I more or less followed these threads, and even actively participated to one, but only now I am putting all the pieces of the puzzle together. Thanks for your explanation, notably by insisting on lmdb outputing architecture dependent data, bit which really cleared things up to me! I see how to address the situation on kleborate side. > Thanks for checking! You're welcome! Thank you so much for your help on that issue! Have a nice day, :) -- Étienne Mollier <emoll...@emlwks999.eu> Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity.
signature.asc
Description: PGP signature
