shawnlaffan

Same issue when running a full build.

I should have looked at the logs earlier. It looks like the argument parsing is awry. ``` >> started 'E:\shawn\sp_repos\Perl-Dist-Strawberry\blib\lib\auto\share\dist\Perl-Dist-Strawberry\utils\CPAN_get_upgrade_list.pl' Unknown option: u Unknown option: r Unknown option: l Unknown...

Looks like we need to also revert the most recent change to this line: https://github.com/StrawberryPerl/Perl-Dist-Strawberry/blob/2ba78fc83d0cc29d039b4987f85a92ff7febf376/share/utils/CPANPLUS_get_upgrade_list.pl#L7 Edit: Or update the passed arguments accordingly. Edit 2: There are more such changes that...

See also https://github.com/StrawberryPerl/Perl-Dist-Strawberry/discussions/157

> An alternative to removing them from the distro is to relocate them to a separate folder that is not in the path. Users can then still conveniently access those...

It was with the utility renamed to ```make``` that the issue first manifested (#148). I should hopefully have some time next week to look at this.

What happens if you use ```mingw32-make```? The ```make``` and ```gmake``` are just copies of ```mingw32-make``` and that appears to have caused the issues under #148. If ```mingw32-make``` does not work...

These links seem to be relevant: https://unix.stackexchange.com/questions/517190/what-causes-make-to-delete-intermediate-files https://stackoverflow.com/questions/47447369/gnu-make-removing-intermediate-files Given their contents, maybe something is messing with ```perly.c``` and changing its timestamp. The ```make``` process then assumes it is an intermediate...

Thanks @sisyphus If I get a chance I'll have a go as well.

The fourth digit in the version number is used for Strawberry Perl versioning, i.e. where changes are made to the SP build options, packaged modules and similar. The changes for...