splintchecker/splint

No ability to configure or make / make errors

zeshinsei opened this issue · 6 comments

The documentation indicates to:

  1. configure
  2. make

Attempting these both and neither work.

$ ./configure
-bash: ./configure: No such file or directory

Looking in the Github package, there is no configure script anywhere with that specific name.

How is this meant to be installed?

Or if I use bootstrap, the make results in:

make  all-recursive
make[1]: Entering directory `/home/user/splint/'
Making all in src
make[2]: Entering directory `/home/user/splint/src'
no -v -t -d --debug --no-lines -p lsl signature.y
make[2]: no: Command not found
make[2]: *** [signature.tab.c] Error 127
make[2]: Leaving directory `/home/user/splint/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/splint/'
make: *** [all] Error 2

The repository does not contain the configure script because it's generated by autoconf.
You have to run ./bootstrap first if you check out the source code from the repository.

The documentation is meant for the users compiling splint from the source tarballs created by make dist.

The repository does not contain the configure script because it's generated by autoconf.
You have to run ./bootstrap first if you check out the source code from the repository.

The documentation is meant for the users compiling splint from the source tarballs created by make dist.

Tried that too, no luck as it results in make errors. Updated my Issue with the details.

same issue here.

no -v -t -d --debug --no-lines -p lsl signature.y
make[2]: no: Command not found

The repository does not contain the configure script because it's generated by autoconf.
You have to run ./bootstrap first if you check out the source code from the repository.
The documentation is meant for the users compiling splint from the source tarballs created by make dist.

Tried that too, no luck as it results in make errors. Updated my Issue with the details.

Could you try autoreconf instead of the bootstrap script? Also, can you give some more details of the systems you are using. Example, uname -a and autoreconf -V. Or with the bootstrap, autoconf --version and automake --version.

According to Makefile, it results from variable BISON is set as no. Try making sure that /usr/bin/bison is exists on your machine then build again.

Setting BISON=no is a bug. Instead of this wrong definition, ./configure should rather produce an error message "Bison/yacc is required".