I am attempting to install vcftools on my macOS Sierra (version 10.12.3). I am using the installation instructions from github as follows (from https://github.com/vcftools/vcftools):
git clone https://github.com/vcftools/vcftools.git
cd vcftools
./autogen.sh
./configure
make
sudo make install (I added sudo because otherwise I got permission denied).
Before beginning vcftools installation, I used homebrew to install the following packages: autoconf, pkg-config, automake, libtool, and zlib. zlib is keg-only so I also used homebrew to link it ('brew link --force zlib'). That way, I would not get errors when running ./autogen.sh.
Now, no errors are listed when I run every line. However, a bin folder containing the vcftools executable is never created in my vcftools folder after finishing the installation instructions. What am I doing wrong?
After running 'sudo make install' the following lines are the last ones printed. Does this have anything to do with the fact that a bin folder is not created?
make[3]: Nothing to be done for install-exec-am'.
make[3]: Nothing to be done forinstall-data-am'.
make[2]: Nothing to be done for install-exec-am'.
make[2]: Nothing to be done forinstall-data-am'.
I would appreciate any feedback. Thank you!
•
written
by
spider_monkey •
However, a bin folder containing the vcftools executable is never created
sudo make install would install it in /usr/local/bin or /usr/bin
try
which vcftools
if you want to install it in a specific directory, you would use
./configure --prefix /path/to/your/dir
Thank you, I understand now! I chose to install it in my vcftools directory and I also entered 'make install' instead of 'sudo make install' like I originally did. Now there is a bin folder containing executables within my vcftools directory. Thanks again!
if it answers , mark my answer as answered (green tick on the left)
Log in to answer this question.
If you already have Homebrew, it might be easier to just use Homebrew Science.
See: https://github.com/Homebrew/homebrew-science