Correction, aside from the case where Fossil doesn’t build at all because I’m trying to link it against a from source statically built copy of libtcl, all other scenarios I’ve outlined use Tcl obtained from running:
sudo apt-get install libtcl8.6 > On Mar 16, 2017, at 7:55 PM, Ryan Dingman <[email protected]> wrote: > > >> On Mar 16, 2017, at 7:03 PM, Joe Mistachkin <[email protected]> wrote: >> >> >> How was the Tcl library built? > > In the case where Fossil builds successfully as a statically linked binary > and then crashes, the Tcl library used is one that gets installed via: > > sudo apt-get install libtcl8.6 > > So, I don’t know precisely how it gets built (other than that it is a dynamic > library). > >> Are you able to step through Fossil in gdb to see why tclInvoke is not >> getting added to the TH1 interpreter? > > I haven’t gone this far in my debugging yet. I’ll try to step through Fossil > later this evening and I’ll report my findings. > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
