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

./updateTaxonomy.sh: line 287: make: command not found #168

Open
transyhieu opened this issue Jan 6, 2022 · 3 comments
Open

./updateTaxonomy.sh: line 287: make: command not found #168

transyhieu opened this issue Jan 6, 2022 · 3 comments

Comments

@transyhieu
Copy link

I was trying to use both 2.8 and 2.8.1, but both of them showed the error. I run the command on a conda environment, I was also asked to install curl, but nothing works after installing curl.
Thank you and have a nice day
Hieu

@clementmlay
Copy link

I have the same problem

@danchurch
Copy link

Is make available to you in the environment you are using (i.e. are you on some sort of cluster or cloud virtual machine where make isn't installed or within your user-privileges?)

For me, I am able to install make (as in, with an ubuntu environment: sudo apt install make), and CCMetagen can then use it, getting rid of the error.

@FranciscoAscue
Copy link

If you're using Anaconda, you'll need to run ktUpdateTaxonomy.sh in your environment. The same goes for Miniconda you may need to create two folders, taxonomy and scripts, in the '~/miniconda3/envs/krona_env/bin' directory. This is what I did, and then I linked the scripts and content from the ~/miniconda3/envs/krona_env/opt/krona/scripts folder ln -s ~/miniconda3/envs/krona_env/opt/krona/scripts/taxonomy.make . ln -s ~/miniconda3/envs/krona_env/opt/krona/scripts/extractTaxonomy.pl .. Finally, run ktUpdateTaxonomy to complete the process.
– if you encounter an error.
navigate to cd ~/miniconda3/envs/krona_env/opt/krona/taxonomy/ and run ./updateTaxonomy.sh. This will update the taxonomy and resolve the issues.

It's possible that linking the content of the scripts and taxonomy folders may not be necessary, but I haven't been able to verify this. If anyone has tested this and found success without linking the folders, that would be great to know.

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

4 participants