Re: Likely Tcl.pm issue on PerlMonks

Hi Vadim,

Note that I=E2=80=99m 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 =E2=80=A6 so it=E2=80=99s =
nice there is a 32-bit option.

Regards,
Jeff

> On May 13, 2019, at 12:35 AM, Konovalov, Vadim =
<[email protected]> wrote:
>=20
> Thanks for pointing this out.
>=20
> 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.
>=20
> Should we recommend to BAWT to Tck::pTk users?
>=20
>=20
>=20
> -----Original Message-----
> From: Christopher Chavez <[email protected]>=20
> Sent: Monday, May 13, 2019 2:23 AM
> To: [email protected]
> Subject: Likely Tcl.pm issue on PerlMonks
>=20
>=20
> [EXTERNAL EMAIL]=20
>=20
> 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=3D1233609
>=20
> 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 =E2=80=94=
 =E2=80=9Cfailed dlopen(=E2=80=A6)=E2=80=9D.