GNOME Bugzilla – Bug 649844
./configure's --enable-tcl[=PATH] option ignores argument
Last modified: 2019-02-23 02:49:37 UTC
Created attachment 187540 [details] [review] xchat-gnome-enable-tcl-fix.patch checking whether TCL support is requested... yes checking for tclConfig.sh... not found configure: error: tclConfig.sh not found. Try --enable-tcl=/path/to/ So, I retry with ./configure --enable-tcl=/usr/lib64 (and I do have tclConfig.sh in /usr/lib64) and get checking whether TCL support is requested... /usr/lib64 checking for tclConfig.sh... not found configure: error: tclConfig.sh not found. Try --enable-tcl=/path/to/ I look at configure.ac and then see that the user's argument is completely ignored by ./configure, excepting to check --enable-tcl=no. Attached is the patch which allows xchat-gnome to find my TCL installation with the help of --enable-tcl, making --enable-tcl=<PATH> work as advertised.
xchat-gnome is not under active development anymore. Its codebase has been archived: https://gitlab.gnome.org/Archive/xchat-gnome/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather reactivate the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again. You may want to switch to Hexchat (or another IRC client that suits you).