Building Mothur 1.19.0

mothur bugs
1

Mothur 1.19.0 does not appear to build correctly in an environment in which 1.18.1 builds just fine. The error message produced:

mpic++ -O3 -m64 -march=native -DBIT_VERSION -DRELEASE_DATE="“5/9/2011"” -DVERSION="“1.19.0"” -DUSE_READLINE -DUSE_MPI -I. -c -o classify.o classify.cpp
classify.cpp: In member function ‘virtual void Classify::generateDatabaseAndNames(std::string, std::string, std::string, int, float, float, float, float)’:
classify.cpp:65: error: no matching function for call to ‘BlastDB::BlastDB(float&, float&, float&, float&)’
blastdb.hpp:20: note: candidates are: BlastDB::BlastDB()
blastdb.hpp:19: note: BlastDB::BlastDB(std::string, float, float, float, float)
blastdb.hpp:16: note: BlastDB::BlastDB(const BlastDB&)
make: *** [classify.o] Error 1

suggests that the problem is that on line 65 of classify.cpp BlastDB() still has only four parameters, where it’s been changed elsewhere in the code to have five.

This is seen on Debian Linux v6.0.1 using openmpi 1.4.2 and gcc 4.4.5 as supplied with the operating system, though that may not be relevant.

2

Thanks for bringing this issue to our attention. I have fixed the problem and uploaded the new source code to the wiki.

3

Yes, thanks, that seems to be working fine.

You may want to make a practise of changing RELEASE_DATE when making code changes. It would make it easier to track which set of code anyone’s looking at.