> I've been using Tcl for the last decade or so with a simulator built as a static executable that can be sent to various remote linux clusters to run. As such I don't want to have to send libraries along with it. itcl and other packages have a configure file that doesn't conditionalize USE_TCL_STUBS on --enable-shared, and in fact, various files just set it. Every time I update to a new Tcl version, I have to edit these out. Is there some reason (1) USE_TCL_STUBS can't be controlled by configure, and (2) have it be dependent on whether or not you are building a static library?
I was under the impression that with careful choice of options, using Stubs is Mostly Harmless even when linking statically. Tcl_InitStubs will lay a stubs table into the interp, and indirecting through the stubs table will work. The strange bit in the cited bug is that the code in question is calling TclOO_InitStubs without calling Tcl_InitStubs first (and TclOO_InitStubs won't call Tcl_InitStubs for you). But I could be misremembering, because it's been a while since I built fully static extensions.
Donal?