Re^2: How and where to pass PERL_USE_UNSAFE_INC=1; to Perl while compilation.

Thank you for the reply.

That is how it was working in the application since years with perl version 5.24.

I understand using FindBin is definitely better option than having current directory (.) but it seems to work for us.

also finding all these files and updating is quite a task for us.

Regards

Comment on Re^2: How and where to pass PERL_USE_UNSAFE_INC=1; to Perl while compilation.

Replies are listed 'Best First'.
Re^3: How and where to pass PERL_USE_UNSAFE_INC=1; to Perl while compilation. by ikegami (Patriarch) on Sep 28, 2021 at 17:38 UTC
That is how it was working in the application since years with perl version 5.24. Doesn't mean it wasn't buggy; it just means you always set the CWD to be the script's directory before starting it up. You literally had to take an extra step to work around the bug. also finding all these files and updating is quite a task for us. `find -name '*.pl' -exec perl -i~ -pe'$_ = "use FindBin qw( \$RealBin ) +; use lib \$RealBin;\n$_" if $. ==2' {} \;` [download]	[reply] [d/l]
Re^4: How and where to pass PERL_USE_UNSAFE_INC=1; to Perl while compilation. by Anonymous Monk on Sep 28, 2021 at 18:13 UTC
Thank you for the reply and the command, yes I agree with you about adding the current directory in the scripts. setting PERL_USE_UNSAFE_INC=1; seems to work, let me still think about the command you have provided. Regards.	[reply]