Le mar. 9 juin 2020 à 16:47, Aaron M. Ucko <u...@debian.org> a écrit :
> Andreas Tille <ti...@debian.org> writes: > > > On Tue, Jun 09, 2020 at 02:25:58PM +0200, Étienne Mollier wrote: > >> My current impression is that makeblastdb is unable to work > >> properly on most 32 bits machines, because the amount of memory > >> needing to be addressed by the process looks like it might > >> exceed too easily 32 bits architectural limits. > > That's entirely plausible; upstream tends to assume 64-bit systems > nowadays. Explicitly supplying -blastdb_version 4 (the default prior to > BLAST+ 2.10.x) may help. > options: * simply remove 32bit package from Debian.... (though should work on *small* datasets). more and more systems are going to 64bit only, and we don't have the task force to fix 32bits issues on such software (too much effort) OR * ignore issue as it is related to memory management but will work on relatively *small* jobs, so software is ~OK 'till a certain point. Olivier > > Thanks for calling this report to my attention! > > -- > Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) > http://www.mit.edu/~amu/ | > http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu > -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
