Changing the Python release cadence

Posted Oct 24, 2019 21:46 UTC (Thu) by kjpye (subscriber, #81527)
In reply to: Changing the Python release cadence by flussence
Parent article: Changing the Python release cadence

Really? I compile Perl 6 (now Raku) from source daily -- indeed I just went and compiled it to make sure.

If you're using rakudobrew to build it, and you have a really old version, then you'll need to delete it and start again. The new version has many advantages, but they required a different disk layout which is incompatible with older versions.

The next rakudo release is imminent, and will probably be followed fairly quickly by a Rakudo Star release which is more end-user focussed.

Changing the Python release cadence

Posted Oct 25, 2019 0:45 UTC (Fri) by flussence (guest, #85566) [Link]

> If you're using rakudobrew to build it, and you have a really old version, then you'll need to delete it and start again.

I've built it straight from git since long before rakudobrew existed, and using a completely fresh checkout doesn't help.

The configure script dies with a missing function error:


HEAD is now at 93f8ff873 [MoarVM Bump] Brings 5 commits
Building NQP ...
/usr/bin/perl Configure.pl --prefix=/home/me/perl6/install --make-install --git-protocol=https \
        --no-relocatable --no-ignore-errors --silent-build --backends=moar --gen-moar
Undefined subroutine &main::slurp called at Configure.pl line 52.
 at /home/me/perl6/rakudo/nqp/3rdparty/nqp-configure/lib/NQP/Config.pm line 35.
        NQP::Config::__ANON__("Undefined subroutine &main::slurp called at Configure.pl line"...) called at Configure.pl line 51

That function *is* exported in the same Config.pm that stacktrace comes from though, so… what the hell?