in reply to Re^5: Strawberry CPAN: error code 130, while making 'pm_to_blib'
in thread Strawberry CPAN: error code 130, while making 'pm_to_blib'

I've been using nmake though

Nmake and dmake have slightly different syntax rules - and, with Strawberry perl, MakeMaker writes a Makefile that conforms to *dmake* syntax, not nmake syntax. It does this because $Config{make} is set to dmake. (You're expected to use the make that $Config{make} specifies.)

If you want to use nmake with Strawberry Perl, you need to set $Config{make} to nmake. This could be done by by replacing the one occurrence of 'dmake' in lib/Config_heavy.pl with 'nmake'. So long as you have a recent version of nmake (not that crappy old 1.50), that should work ok - but I don't see that it achieves anything useful.

There's nothing wrong with your ExtUtils::MakeMaker or ExtUtils::Install. They're doing precisely what they're supposed to do :-)

Cheers,
Rob
  • Comment on Re^6: Strawberry CPAN: error code 130, while making 'pm_to_blib'

Replies are listed 'Best First'.
Re^7: Strawberry CPAN: error code 130, while making 'pm_to_blib'
by frankcox (Acolyte) on Mar 14, 2009 at 23:59 UTC
    Thanks again Rob, I appreciate all the useful information.

    This is a great outcome because it means I can put Strawberry Perl back in my path and get on with my work. That's good because I feel more at home with the way cpan works there.

    --Frank Lyon Cox