Hi Vadim, Note that I’m no longer with ActiveState myself, so my opinions are very independent. ;)
As this is just about a 32 v 64 bit load issue, I would recommend that people be aware of that in some level of documentation, with pointers to whatever the appropriate matching combo for their install would be. I think ActiveTcl will remain to be 64-bit only … so it’s nice there is a 32-bit option. Regards, Jeff > On May 13, 2019, at 12:35 AM, Konovalov, Vadim <vadim.konova...@dell.com> > wrote: > > Thanks for pointing this out. > > Hi Jeff, > What would be your best recommendation on the matter? > IMO there are plenty of alternatives to ActiveTCL only because ActiveTCL > (together with its teacup) became harder to use, therefore lot of binary > builds have appeared: IronTCL, BAWT, etc. > > Should we recommend to BAWT to Tck::pTk users? > > > > -----Original Message----- > From: Christopher Chavez <chrischa...@gmx.us> > Sent: Monday, May 13, 2019 2:23 AM > To: tcltk@perl.org > Subject: Likely Tcl.pm issue on PerlMonks > > > [EXTERNAL EMAIL] > > Just want to share a recent question I found on PerlMonks, in case anyone > else wants to take a look or can help: > https://www.perlmonks.org/?node_id=1233609 > > The user was initially trying to get Tkx working with DWIM Perl + ActiveTcl > but the error looks like it might be coming from Tcl.pm — “failed dlopen(…)”.
