I'm trying to figure this whole bowtie2 thing out, so I tried running through the tutorials, but I can't seem to get the bowtie2-build command to work.
I make a temp directory in /gwork/cmoore/ and then tried to run the following command:
bowtie2-build /gwork/cmoore/installers/bowtie2-2.2.6/example/reference/lambda_virus.fa lambda_virus
Every time, I get the following error:
Traceback (most recent call last):
File "/gwork/cmoore/installers/bowtie2-2.2.6/bowtie2-build", line 95, in <module>
main()
File "/gwork/cmoore/installers/bowtie2-2.2.6/bowtie2-build", line 92, in main
os.execv(build_bin_spec, argv)
OSError: [Errno 8] Exec format error
Any ideas?
I will take a quick shot out in the dark. If you downloaded the source code try to build bowtie2 again on your local machine.
cd /gwork/cmoore/installers/bowtie2-2.2.6/
make clean
make -j
Then try to run your build command again using the local binaries.
./bowtie2-build example/reference/lambda_virus.fa lambda_virus
Let me know how it goes.
Val
Still getting an error:
[cmoore@saw-login1 ~]$ cd /work/cmoore/installers/
[cmoore@saw-login1 installers]$ ls
bowtie2-2.2.6/ cutadapt-1.8.3/ FastQC-0.10.1/ samtools-1.2/
tophat-2.0.13/
[cmoore@saw-login1 installers]$ cd bowtie2-2.2.6/
[cmoore@saw-login1 bowtie2-2.2.6]$ make clean
make: *** No rule to make target `clean'. Stop.
[cmoore@saw-login1 bowtie2-2.2.6]$ make -j
make: *** No targets specified and no makefile found. Stop.
[cmoore@saw-login1 bowtie2-2.2.6]$
On Wed, Nov 4, 2015 at 12:56 PM, Val valduboisvert@users.sf.net wrote:
--
Regards,
Clayton Moore
BSc. Molecular Biology and Genetics (Honours)
University of Guelph
Related
Bugs:
#342Still getting an error:
[cmoore@saw-login1 ~]$ cd /work/cmoore/installers/
[cmoore@saw-login1 installers]$ ls
bowtie2-2.2.6/ cutadapt-1.8.3/ FastQC-0.10.1/ samtools-1.2/ tophat-2.0.13/
[cmoore@saw-login1 installers]$ cd bowtie2-2.2.6/
[cmoore@saw-login1 bowtie2-2.2.6]$ make clean
make: *** No rule to make target `clean'. Stop.
[cmoore@saw-login1 bowtie2-2.2.6]$ make -j
make: *** No targets specified and no makefile found. Stop.
[cmoore@saw-login1 bowtie2-2.2.6]$
Ok, you do not have the source code. Could you please let me know the output of the command uname -a please?
[cmoore@saw-login1 bowtie2-2.2.6]$ uname -a
Linux saw-login1 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Last edit: Clayton Moore 2015-11-04
Not sure if you got my message. I sent you a few commands to run. Do not forget the dot in front of ./bowtie-build command.
thanks,
Val
I believe you're talking about these commands:
Still not having any luck... sorry if I've missed any commands you sent.
Sorry, it was a typo in my original message. Here is the command again:
./bowtie2-build-s example/reference/lambda_virus.fa lambda_virus
That double ./ should not be there.
Even with the single ./ I'm having no luck. Still getting the binary error.
Do you have the proper right to execute from that directory? Did you install bowtie2 into that location? A quick way to check if this is related with the system is to download bowtie into your home dir and try it from there. Something like this:
cd
wget http://sourceforge.net/projects/bowtie-bio/files/bowtie2/2.2.6/bowtie2-2.2.6-linux-x86_64.zip/download
unzip bowtie2-2.2.6-linux-x86_64.zip
cd bowtie2-2.2.6
./bowtie2-build-s example/reference/lambda_virus.fa lambda_virus
I have a similar system and I just retested the bowtie2 build we have on sourceforge over there. It works fine on my end. We need to figure out what is happening on your system now.
I've never had any problems running any other programs from that directory. I just uninstalled the bowtie2 I had, and reinstalled it and it seems to have worked... Still no clue what the problem was... but I it seems to work now.
As another quick question, what's the difference between bowtie2-build and bowtie2-build-s?
Glad that worked. bowtie2-build is just a wrapper that calls the proper binaries. In the case of bowtie2 the wrapper is taking care of much more. In the case of bowtie2-build it is just calling the "large" or "small" binaries. That is the binaries that can build a very large index or those that can build a small one.
Val
Awesome. Thanks so much for your help!!!
I will close this for now.