/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4/configure complains about a C compiler flag

[ballapete (Peter "Pete" Dyballa)]

checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for tclsh... /opt/local/var/macports/sources/selfupdate/base/vendor/tcl8.6.14/unix/tclsh
/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4/configure: line 9259: -I/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4: No such file or directory
configure: creating ./config.status
config.status: creating Makefile

Performing the selfupdate in GNU Emacs it shows that the string after "-I" is exactly the pathname to the directly in which configure is running…

[ballapete (Peter "Pete" Dyballa)]

And I think I saw it before with 2.10.2…

[jmroot (Joshua Root)]

Is this causing the build to fail?

[ballapete (Peter "Pete" Dyballa)]

No.

[jmroot (Joshua Root)]

Then AFAICT there is no problem. If the message bothers you cosmetically, you can report it to Tcl upstream if it's not already fixed.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ballapete:

/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4/configure: line 9259: -I/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4: No such file or directory

This message is what you would get if the configure script tried to execute the command -I/opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4. Looking at ​that line the command being run is:

eval itcl_INCLUDE_SPEC="-I${itcl_SRC_DIR}/generic -I${itcl_SRC_DIR}"

Reducing this to a smaller test case:

% eval a="b c"
zsh: command not found: c

This does indeed seem like a bug in itcl. Perhaps it shouldn't be using eval. Two bug reports were already filed about it last year, with no response so far:

​https://core.tcl-lang.org/itcl/tktview/7248d8e9ac7c63a5a414

​https://core.tcl-lang.org/itcl/tktview/97c5842cd64dbff310c0