On 5/13/2017 10:50 AM, Joe Mistachkin wrote:
....
It appears that --with-tcl is unique in that it actually requires a value
in order to proceed. The value can be a path or the string literal "1".
It's not clear to me that it would have worked properly before the --with
changes without a value (i.e. because "opt-val" would have returned an
empty string, thus skipping the whole block that handles it in auto.def).
Maybe I'm wrong?
Perhaps there was a latent bug in the autosetup's handling of option values?
I didn't edit my shell script until poking at this on Friday, and it had
been happily building freshly configured fossils using just plain
--with-tcl with no arguments until then. I was always confused from the
description whether --with-tcl was needed if --with-tcl-stubs and/or
--with-tcl-private-stubs were used, or for that matter if the latter two
weren't conflicting in some way. But it had built and passed all tests
with this configure line:
../../fossil/configure --with-zlib=tree
--with-openssl=C:/Programs/MinGW/msys/1.0/local/ssl --json --with-tcl
--with-tcl-stubs --with-tcl-private-stubs --with-th1-docs --with-th1-hooks
That stopped working, so I liberally salted it with =1 and configure
started working again.
--
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
