-
Notifications
You must be signed in to change notification settings - Fork 287
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
Bedtools install on Mac #1077
Comments
Hi! first, make sure you are running conda on osx64 and not osx-arm64. Then, check your python version, I don't want to say any lies but I'm pretty sure that conda-forge / bioconda only works with Python 3.7 - 3.10 (you can always check it on their wiki). This is the most typical mistake when dealing with this type of message. Hope you solved it! |
Yes, I was trying to install it on arm processor. There is a way to install Bedtools with this difference? |
Uninstall everything and go to: Install directly the version x86_64 (You have to have downloaded before software meant for Intel proc and have Rosetta on your Mac) you can check on internet how to verify if you have it. Then, use bash to install the x86_64 version on the terminal. Reset the terminal and Then, create an env with a version of Python compatible with Bioconda (3.7 - 3.10) and you should be able to download everything! (While downloading Conda from Conda-Forge it will make these channels per default so no need to config them before install any package) This will also add per default mamba, which I strongly recommend to create env / download packs. (it has the same command structure than conda but way faster) Hope it works! |
Hi all,
I'm trying to install a package which has a dependencies based on bedtools, the hardware is a Macbook pro. I read about people that got the installation through Conda channels, but conda install or mamba install give me the following output:
bedtools does not exist (perhaps a typo or a missing channel).
Do you have some solutions or know where I can find a way to install it?
The text was updated successfully, but these errors were encountered: