Thanks for the info. I found that I can do this in a Tkx script to work around the problem:

BEGIN {
    $ENV{PERL_DL_NONLAZY} = 1;
}

This enables one to just run the script as normal without setting the variable manually first. Is this variable okay to use in production code? It sounds to me like it would be analogous to "use strict", as in, it might mean a slight performance hit when starting Perl but it catches potential errors at compile time.