#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 egall@…): Replying to [comment:6 cal@…]:
Replying to [comment:4 egall@…]:
Perhaps there could be a "`--with-bundled-tcl`" flag for the configure script to control whether the bundled tcl gets built or not? Or a "`--with-tcl-prefix=`" flag to control which already-installed copy of Tcl gets used, if any?
That increases the possibility for misconfigurations (such as choosing Tcl 8.6), 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. and is generally even more autoconf work to do, which I'd like to avoid. I like doing autoconf work, you could always let me do that for you. Heck, I may even already have such flags in my own fork of MacPorts, let me check...
There are already precedents for both in MacPorts, as I remember there
being a "`--with-included-tclthread`" flag previously, and there are also "`--with-curlprefix`" and "`--with-sqlite3prefix`" flags for choosing the prefix of curl and sqlite3 respectively...
Check again, those no longer exist (actually the curl one does, but the
others are gone). 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... -- Ticket URL: <https://trac.macports.org/ticket/42756#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X