Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error compiling metacache #4

Closed
ghost opened this issue Nov 27, 2017 · 5 comments
Closed

error compiling metacache #4

ghost opened this issue Nov 27, 2017 · 5 comments

Comments

@ghost
Copy link

ghost commented Nov 27, 2017

Hi

I ran into this error trying to compile metacache:

mkdir build_release
g++ -std=c++11 -O3 -Wall -Wextra -Wpedantic -c src/args_handling.cpp -o build_release/args_handling.o
g++ -std=c++11 -O3 -Wall -Wextra -Wpedantic -c src/cmdline_utility.cpp -o build_release/cmdline_utility.o
g++ -std=c++11 -O3 -Wall -Wextra -Wpedantic -c src/filesys_utility.cpp -o build_release/filesys_utility.o
g++ -std=c++11 -O3 -Wall -Wextra -Wpedantic -c src/main.cpp -o build_release/main.o
src/main.cpp: In function ‘int main(int, char**)’:
src/main.cpp:72:16: error: ‘runtime_error’ in namespace ‘std’ does not name a type
catch(std::runtime_error& e) {
^
src/main.cpp:73:37: error: ‘e’ was not declared in this scope
std::cerr << "\nABORT: " << e.what() << "!" << std::endl;
^
src/main.cpp:75:16: error: ‘invalid_argument’ in namespace ‘std’ does not name a type
catch(std::invalid_argument& e) {
^
src/main.cpp:76:37: error: ‘e’ was not declared in this scope
std::cerr << "\nABORT: " << e.what() << "!" << std::endl;
^
make: *** [build_release/main.o] Error 1

Any advice on how to resolve it would be great! Thank you.

@muellan
Copy link
Owner

muellan commented Nov 28, 2017

Hi,
looks like the <stdexcept> header is not included in main.cpp.
Which compiler do you use? Clang?
The problem should go away if you #include <stdexcept> in main.cpp.
I should probably fix that, too. GCC doesn't complain, probably because it is included transitively through <vector> or some other header there.

@ghost
Copy link
Author

ghost commented Nov 28, 2017 via email

@muellan
Copy link
Owner

muellan commented Nov 29, 2017

The genomes itself and the taxonomy are no longer needed after the database has been built. The database consists of one large binary file that contains all relevant information for classification.
(But you might want to keep the genomes and taxonomy if you want to build another database with different settings.)

@ghost
Copy link
Author

ghost commented Nov 30, 2017

Hi Andre

is there a way to generate a taxonomic/abundance table from the results file?

Thank you

@muellan
Copy link
Owner

muellan commented Dec 1, 2017

Hi.
Yes, that's one of the things a colleague of mine is currently working on :-)
He does it in a post processing step. But I'm sorry we can't share the code yet, because it is part of an upcoming publication.

@muellan muellan closed this as completed Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant