cannot configure
amerello opened this issue · comments
executing ./configure produces the following error:
config.status: error: cannot find input file: 'data/Makefile.in'
executing make afterwards fails.
Great. These kind of errors are the ones we want to solve. Note that for next week (Nov 5) is sufficient to move the repo to git with the history (what you already did) and list in the README.md some key points of the tool. See: Rostlab/PP2_CS_WS_2015-16#1
Specifically for this issue, it seems that no Makefile.in exists, but Makefile.am (https://github.com/Rostlab/LocTree/tree/master/data)
@gyachdav maybe you know ?
The repo indeed doesn't have the makefile.in. Note that this file should not be versioned in the repo as it is only relevant for build time and not part of the code base.
In order to generate this file and build the tar.gz archive for this package you should take a look at
https://rostlab.org/owiki/index.php/Packaging_howto#automake_and_autoconf
and esp follow the steps described at the end of the section. [Make sure you understand what each command does and don't just blindly run them sequentially. ]
@gyachdav but I think think the file is still relevant to have and be able to move around. I guess it can be separated from the actual source code, either in a separate folder or root folder.
That's the norm for say .pom or npm build files.
There's no reason to keep this file in the repo as it will get rebuilt every time you make a package. Since this is a target machine specific build file keeping it and trying to reuse it on a different system could result in a messed up build process.
On Nov 2, 2015, at 9:38 AM, Juan Miguel Cejuela notifications@github.com wrote:
@gyachdav but I think think the file is still relevant to have and be able to move around. I guess it can be separated from the actual source code, either in a separate folder or root folder.
That's the norm for say .pom or npm build files.
—
Reply to this email directly or view it on GitHub.
@gyachdav OK got it. Agree.
This problem is solved. Relevant information has been added to README.md