Merry happy, all -

Lately I've been trying to get better at Perl debugging, since Perl is the language I use most these days. I've discovered that there are some options I can't explore unless the Perl I'm using was compiled with the DEBUGGING flag ... and this seems not to be the case with Slackware's Perl.

So I'm not sure whether the best thing to do would be roll my own "alternate" Perl with DEBUGGING, or ... something else.

It's a naive question, but I guess that the Perl in the Slackware package is already compiled, right? I mean it wouldn't do me any good to try to reinstall Slackware's Perl with a modified install script ...?

Thanks for any pointers,

Glenn

Just modify the SlackBuild and add the configure options you want, bump the BUILD number and re-compile and package it.

This would be a good place to start: http://slackware.osuosl.org/slackwar...source/d/perl/

Use the build script as suggested, but Slackware and everything else in a Slackware using Perl doesn't break if you compile a new Perl by hand with your favorite options.

Two Perls also work fine as long as you remember your paths and don't overwrite the executables by accident.

I've got the Slack orginal Perl (still on 12.0...), a recent 5.10, a pugs and rakudo and everything works fine.