[MacPorts] #71220: /opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4/configure complains about a C compiler flag

[MacPorts]

#71220: /opt/local/var/macports/sources/selfupdate/base/vendor/tcl/pkgs/itcl4.2.4/configure
complains about a C compiler flag
------------------------+--------------------------
  Reporter:  ballapete  |      Owner:  (none)
      Type:  defect     |     Status:  closed
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.10.4
Resolution:  wontfix    |   Keywords:  sonoma intel
      Port:             |
------------------------+--------------------------

Comment (by ryandesign):

 Replying to [ticket:71220 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 [https://github.com/macports/macports-
 base/blob/release-2.10/vendor/tcl8.6.14/pkgs/itcl4.2.4/configure#L9259
 that line] the command being run is:

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

 Reducing this to a smaller test case:

 {{{#!sh
 % 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

-- 
Ticket URL: <https://trac.macports.org/ticket/71220#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS