Dear all,
I am re-building bioinformatics software in a newly acquired machine; I am using tools that I have compiled on Ubuntu 14 and 16, but the new machine has Ubuntu 17 and I am getting strange warnings and poor failure in compilation, For instance I have been using Bowtie2 in the old machine; in the new I have installed tbb with sudo apt-get install libtbb-dev then downloaded the latest Bowtie2 source and built it with make as suggested in the manual. I got, just for an example, the following errors:
diff_sample.h:180:6: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
if(!diffs[d1]) diffCnt++; diffs[d1] = true;
^~
diff_sample.h:180:32: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
if(!diffs[d1]) diffCnt++; diffs[d1] = true;
^~~~~
diff_sample.h:181:6: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
if(!diffs[d2]) diffCnt++; diffs[d2] = true;
^~
diff_sample.h:181:32: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
if(!diffs[d2]) diffCnt++; diffs[d2] = true;
^~~~~
that I did not obtain previously. In the old computer, for instance, bowtie2-align-l is given as 'executable shared library (application/x-executable)' with the classic purple icon; in the new computer the file compiled is listed as 'shared library (application/x-sharedlib)'. Similarly with other tools such as blast. I installed 'make' with sudo apt-get install make.
The tools are contained in the directory ~/src and then their location is exported to PATH.
Is there something funny with Ubuntu 17 or I forgot to install in the new machine some fundamental library required for the compilation?
Why are you building things from source? Ubuntu comes with plenty of tools available via
apt, including blast and bowtie.Compiling from source is often the only way to get the latest version, which is desirable especially if it has bug fixes and/or new features.
in the case of bowtie itself, i had a previous error with
apt-get bowtie2, compiling from source was the solution.This should be
apt install bowtie2. Packages normally install without problem with apt so I wonder what kind of error you got.probably it was
apt install bowtie2but I forgot the issue...This is probably due to using a newer compiler. Newer versions of GCC tend to produce errors where previous versions only issued warnings. It also depends on which compiler options are used. These warnings are an indication that not all is well with the code and I would report them to the developers so that the issues could be fixed before the software becomes impossible to compile with new compilers.
if u17 comes with a newer compiler than u16, would be possible to downgrade the compiler? i had not these issues with u16.
I got gcc 7.2.0 pm both machines. The difference is that I installed with success Bowtie2 on ubuntu16 and I am now getting errors while compiling on ubuntu17.
Same kind of error with BWA, the file produced by the compilation is a shared library rather than an executable. It is not just an issue of Bowtie.
What exactly the compilation produced? Did you try:
actually now it works like an executable...
HISAT2 is also built as shared library instead of executable, even if in this case I could not locate the libraries MSYS and zlib, also the pre-compiled binaries for linux are not available.
What do you mean by "is built as a shared library". Did you try:
since I am getting the issue that -- even if the compilation succeed -- the executables are listed as shared libraries, can I compile the tools on the old Ubuntu 16 machine and the copy them in the new Ubuntu 17 machine?
Did you try to run these "shared objects"? See this:
Executables vs Shared objects