[MacPorts] #42756: macports doesn't compile with bundled tcl

[MacPorts]

#42756: macports doesn't compile with bundled tcl
----------------------------+--------------------------------
  Reporter:  xeron.oskom@…  |      Owner:  macports-tickets@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  base           |    Version:  2.2.99
Resolution:                 |   Keywords:
      Port:                 |
----------------------------+--------------------------------

Comment (by cal@…):

 Replying to [comment:8 egall@…]:
 > If a user is building from source themselves, they should be aware of
 that. Also I fail to see why choosing Tcl 8.6 is considered a
 "mis"configuration.

 In that case you obviously haven't tried doing that. It currently breaks
 MacPorts (in a completely un-obvious way) because MacPorts declares `try`
 in a way incompatible with the command added natively to Tcl 8.6.

 > I just checked out trunk and the sqlite3 one still exists, too. Also
 while the "`--with-included-tclthread`" flag may be gone now, I would
 argue that should be brought back as well, as its presence has often made
 the difference between compilation success and failure for me...

 If that's the case then you should file a bug against the Tcl Thread
 package and ask them to fix the problem caused by the build. The problem
 might however be gone by now, because I also updated the included Tcl
 Thread package to 2.7.0. The `--with-included-tclthread` flag was actually
 never necessary IMO – base before the recent changes would automatically
 determine whether the host Tcl had the package and enable this option if
 it didn't. Without this option, trace mode doesn't work.

 Replying to [comment:11 xeron.oskom@…]:
 > Replying to [comment:7 cal@…]:
 > > That's certainly a good reason for having those variables set, but do
 you need them when compiling MacPorts?
 > No I don't. But also I don't want to cleanup them by hands before
 macports compilation.

 That's understandable. Let's wait what the discussion on -dev suggests,
 but at the moment I'm inclined to do the extra shell scripting/autoconf
 work to strip those paths automatically.

 > Compiling from source. Haven't tested with selfupdate (Is it possible to
 get SVN version of macports with selfupdate?).

 No.

-- 
Ticket URL: <https://trac.macports.org/ticket/42756#comment:13>
MacPorts <http://www.macports.org/>
Ports system for OS X