Installing Trinity, Error with Samtools
1
0
Entering edit mode
8.4 years ago

Hello,

I am trying to install trinity on our schools server. I have installed it into my home directory since I do not have access to install it to the bin. I then ran the "make" command and "make plugins." Everything seemed to be running smoothly, however, when I went to run Trinitys sample code, I got this error:

which: no samtools in (/home/npetrill/trinityrnaseq-2.1.1/trinity-plugins/BIN:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/npetrill/bin:/usr/local/bin/trinityrnaseq-2.0.6:/usr/local/bin/bowtie-1.1.2:/home/npetrill/samtools-0.1.19:/home/npetrill/scripts) Error, cannot find samtools. Please be sure samtools is installed and included in your PATH setting.

I set my path so that it would search the directory in which samtools is in, however, I keep getting this error message. Does anyone know what I am doing wrong here?

Thank you for your help!

RNA-Seq samtools trinity • 5.5k views
ADD COMMENT
2
Entering edit mode
8.4 years ago
st.ph.n ★ 2.7k

When installing programs with make files, like samtools, one can specify the install path for the program. To do this when typing make simply enter: 'make prefix=/path/to/dir install' when running 'make install' This will install samtools in the directory that you wish. However, as indicated by Trinity, you need to set samtools in your path. I keep a directory in my home directory called 'bin', in which I install programs such as these. Then in .bashrc, enter a line to export the path to this directory: 'export PATH=$PATH:/home/your_home/bin'. Restart the terminal, and type 'echo $PATH'. Your home directory bin folder should now show up in your path as well as any others that are being exported, plus the typical /usr/local/bin/; /usr/bin; etc.

ADD COMMENT

Login before adding your answer.

Traffic: 2453 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6