I got a step further than Richard.... It seems to need a config dir...
mkdir ./config Run the bootstrap script ./bootstrap Configure it... ./configure Make make Alas, still dies... Making all in imports make[2]: Entering directory '/home/johnc/build/splint-patched/imports' GEN assert.lcs mv: './assert.lcs' and './assert.lcs' are the same file Makefile:488: recipe for target 'assert.lcs' failed make[2]: *** [assert.lcs] Error 1 make[2]: Leaving directory '/home/johnc/build/splint-patched/imports' Makefile:364: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/johnc/build/splint-patched' Makefile:305: recipe for target 'all' failed make: *** [all] Error 2 On Tue, Mar 21, 2017 at 1:31 PM, Richard A. O'Keefe <o...@cs.otago.ac.nz> wrote: > > > > Your are correct, those bits should be changed, but I'd like to point > > out that my main goal was code, not documentation (if I'd have to also > > update documentation, there are places that are in need since earlier > > then the last official version, not to mention the changes that I've > > described). > > Installation instructions basically *are* code, > that just happens to be executed by a human being. > Code I cannot install is code I cannot use. > > > > > As I've mentioned in the description, my approach to code repository > > is that all generated files (including configure, generated from > > configure.ac) don't belong in the repository (changing the [external] > > generation tool without any changes to the template files causes > > changes in repository -- not my idea of good practice). But, as I've > > also mentioned in the announcement, now 'make dist' works correctly, > > producing valid archives (*.tar.gz) to distribute. > > There are many respected software engineers who say that > EVERYTHING belongs in the repository. But it's your > repository, so your rules. > > If I could use 'make dist' I wouldn't need to. > >> > > > > automake provides some standard macros that are not installed by > > default (that should be done only once, and its assumed the developer > > runs that). If I remember correctly, in order to force autotools > > (autoconf/automake/libtool) to install/generate what is standard but > > missing, one should use 'autoconf -i' in the directory containing > > configure.ac. [Keep in mind this is just a temporary solution until > > I find a way to distribute proper source archives, not repositories]. > > Sadly, this is not a solution. > > % autoconf -i > configure.ac:16: error: possibly undefined macro: AM_INIT_AUTOMAKE > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:17: error: possibly undefined macro: AM_SILENT_RULES > configure.ac:31: error: possibly undefined macro: AM_PROG_LEX > > It turns out that the latest version of autoconf available > from the GNU site is 2.69, which is the one already installed > on the system. > > Just to make sure, I downloaded autoconf-latest and built a > local installation of it, and > > m% autoconf > configure.ac:16: error: possibly undefined macro: AM_INIT_AUTOMAKE > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:17: error: possibly undefined macro: AM_SILENT_RULES > configure.ac:31: error: possibly undefined macro: AM_PROG_LEX > > m% autoconf --version > autoconf (GNU Autoconf) 2.69 > ... > > so it is not a problem with the system's autoconf. > > So I flicked over to a Linux box and found that autoconf > wasn't installed there. So I installed a local copy of > autoconf 2.69, and no difference. Still doesn't work. > It's not a Linux -vs- MacOSX difference. > > Your repository, your rules, my two days of frustration. > > > _______________________________________________ > splint-discuss mailing list > splint-discuss@mail.cs.virginia.edu > http://www.cs.virginia.edu/mailman/listinfo/splint-discuss > -- John Carter Phone : (64)(3) 358 6639 Tait Electronics PO Box 1645 Christchurch New Zealand -- ------------------------------ This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.taitradio.com/email_disclaimer ------------------------------
_______________________________________________ splint-discuss mailing list splint-discuss@mail.cs.virginia.edu http://www.cs.virginia.edu/mailman/listinfo/splint-discuss
