I've been trying to chase down a minimal patch to autosetup to make our configure work again. This was reported on fossil-users early this morning, and I can confirm that my build and test automation here is affected.

The issue seems to be that autosetup 0.6.6 includes a new and "improved" option parser with changed support for boolean options. The most visible new feature is that --with-x is now a synonym for --enable-x and --x=1, and correspondingly --without-x, and --disable-x both mean --x=0.

We have a bunch of options named --with-somthing. Some default to 0 and are used like booleans. Others take strings.

Attempting a configuration with most features turned on, I see:

$ ../fossil/configure --with-zlib=tree --with-openssl=/local/ssl --json --with-tcl --with-tcl-stubs --with-tcl-private-stubs --with-th1-docs --with-th1-hooks
Host System...i686-pc-mingw32
Build System...i686-pc-mingw32
C compiler... cc -g -O2
C++ compiler... c++ -g -O2
Build C compiler...cc
Checking for stdlib.h...ok
Error: Unknown option --tcl
Try: 'configure --help' for options
$

I then edited autosetup/autosetup to remove the --with prefix from the getopt function. That changed the error, bud did not cure the problem. Now I see:

....
Error: Option --with-tcl requires a value

I assume there were good reasons to update autosetup from upstream. But this change broke our builds.

--
Ross Berteig                               r...@cheshireeng.com
Cheshire Engineering Corp.           http://www.CheshireEng.com/
+1 626 303 1602

_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to