Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Explained "Why can't we use Jim Tcl for the test suite?" in the auto.def comment above the check for a suitable tclsh version. Basically, I tried it and then documented a few of the resulting failures.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | tclsh-macos|
|Files:||files | file ages | folders|
|User & Date:||wyoung 2018-09-02 21:00:05|
|21:46||Fixed an incorrect Tcl string comparison checked in with [e449cb09]. (Closed-Leaf check-in: c94617b5 user: wyoung tags: tclsh-macos)|
|21:00||Explained "Why can't we use Jim Tcl for the test suite?" in the auto.def comment above the check for a suitable tclsh version. Basically, I tried it and then documented a few of the resulting failures. (check-in: 91eaef61 user: wyoung tags: tclsh-macos)|
After autosetup checks for the existence of tclsh in the PATH, it now
checks whether it's at least version 8.6, because macOS is still
shipping 8.5, despite it being nearly 6 years old. If we find an old
tclsh, try to find the Homebrew tcl-tk package, and use that version
instead. This is not a macOS or Homebrew specific change in principle:
we can extend this logic for other systems to find their best Tcl/Tk
version, as needed.
On systems where autosetup is used, this only affects "make test". There are other uses of tclsh in this tree which may also benefit from our PATH discoveries, but this checkin doesn't update those.
This checkin also doesn't try to address similar problems on other platforms, such as the "TCLSH = tclsh" line in Makefile.mingw.(check-in: e449cb09 user: wyoung tags: tclsh-macos)
Changes to auto.def.