Package Details: rakudo-star 2017.07-2

Git Clone URL: (read-only)
Package Base: rakudo-star
Description: Rakudo Perl6 on MoarVM with additional modules
Upstream URL:
Licenses: PerlArtistic
Conflicts: rakudo-moarvm, rakudo-star
Provides: rakudo-moarvm, rakudo-star
Submitter: maleadt
Maintainer: savagezen
Last Packager: savagezen
Votes: 15
Popularity: 0.248757
First Submitted: 2010-08-06 13:18
Last Updated: 2017-11-15 03:18

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

savagezen commented on 2017-11-05 18:53

As discussed below, I have created a metapackage to install the Rakudo Star modules if Zef has already been installed. Zef is the Perl6 module manager and requires Rakudo (Perl6) to have already been installed.

savagezen commented on 2017-10-29 20:21


Thanks for the feedback. The short answer is "no" I haven't got this to build / work properly. You're correct about a meta-package being the way to go. I've been holding out hope that each new release would fix DESTDIR support, but it hasn't.

I can set to work on the meta-package, but haven't had much time lately. If you (or anyone) are inclined to do so, you'll also need to make a 'zef' package to that will be used to install the Star modules on top of rakudo. That said, you'll also want to use the *-git versions of moarvm, nqp, and rakudo as another ongoing issue has been that the official releases of those packages are "not new enough" to support the Star modules.

piojo commented on 2017-10-29 04:26

This package isn't building, and the "star" modules aren't even designed to build unless rakudo is already installed. It fails as soon as zef starts to compile, because it looks for /usr/share/perl6/runtime/perl6.moarvm, but the file only exists as $pkgdir/usr/share/perl6/runtime/perl6.moarvm.

Since this isn't even supposed to work--upstream said it would make more sense for "star" or "star-packages" to be a meta package which ONLY includes modules, and will be built after rakudo is installed.

(stmuk is the rakudo-star maintainer, so that is as official as it gets.)

So it actually makes sense to remove this package and replace it with a "star-modules" package.

atweiden commented on 2017-08-07 02:18

Could you install tools/ to /usr/bin, e.g.

install -Dm 755 tools/ "$pkgdir/usr/bin/perl6-install-dist"

This makes it possible to install perl6 pkgbuilds system-wide without downloading the script per package.

savagezen commented on 2017-06-25 19:05


I'm not sure of the issue, however I'm looking into it. There is a forum thread created by someone else to discuss.

newnumbertwo commented on 2017-06-20 05:53

Does not build. Ends with:

== Installing modules for MoarVM
cd modules/zef && sh -c "PATH=/usr/bin:/home/USERNAME/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl /tmp/yaourt-tmp-USERNAME/aur-rakudo-star/pkg/rakudo-star/usr/bin/perl6-m -Ilib bin/zef install ."
Unhandled exception: While looking for '/usr/share/perl6/runtime/perl6.moarvm': no such file or directory
make: *** [Makefile:66: modules-install-m] Error 1
==> ERROR: A failure occurred in package().
==> ERROR: Makepkg was unable to build rakudo-star.
==> Restart building rakudo-star ? [y/N]
==> ------------------------------------

savagezen commented on 2017-01-20 00:03

Thanks @spider-mario. Update had been pushed.

spider-mario commented on 2017-01-18 09:06

The difference with the contents of the PKGBUILD is due to the fact that the .SRCINFO is out of date (and that’s where the AUR gets its version number from). You can regenerate it using mksrcinfo.

dietchrst commented on 2017-01-13 03:24

Yes that makes sense - that PKGBUILD will pull the current one. I was facing a proxy issue, which was avoided by just manually downloading the sources myself and then building from there. It isn't something I normally do, and that's what made me notice the difference in what is listed by the AUR as the source. I don't maintain packages, so I don't really know how it works, or how common it is that there is a difference between what's listed and what the PKGBUILD says. Thanks for responding so quick, and thanks for keeping this current!

savagezen commented on 2017-01-12 20:05

@dietchrst The PKGBUILD is correct. It will build the 2016.11 upstream release (which is the current one, not 2016.12).

The AUR is reporting the version (and corresponding "Sources") as 2015.06 and I'm not sure what is causing that. If you've got suggestions for that, you can make an issue or pull request on GitHub:

dietchrst commented on 2017-01-12 19:06

the source listed here is wrong for the current package. I have to manually download the sources, and the rakudo-star-2015.06.tar.gz is behind the current one (2016.12). It was easy to get the correct one, but might be confusing.

savagezen commented on 2016-12-13 16:30

Thanks @blippy. You're correct. Update has been pushed.

blippy commented on 2016-12-13 12:51

I think your checksum is wrong:
sha512sum rakudo-star-2016.11.tar.gz
77803d3e5e81c89d7a9ebbd6405c4675e58560a8feff555b3dd8a142d4460ad0f18c005e385788344f75efe79be4368a75d81f6aa346bd53792513c7775c99bd rakudo-star-2016.11.tar.gz

savagezen commented on 2016-10-30 20:17

Thanks @moyamo, I forgot to update the checksum when changing the source version. PKGBUILD has been updated.

moyamo commented on 2016-10-30 11:17

I think the sha512 sum is wrong. It should be

savagezen commented on 2016-04-28 02:52

@alx741 As of the 2016.01 version I've had an issue open on GitHub which I've yet to resolve

alx741 commented on 2016-04-27 03:53

Currently got:

from gen/moar/m-main.nqp:37 (perl6.moarvm:MAIN)
from gen/moar/m-main.nqp:33 (perl6.moarvm:<mainline>)
from <unknown>:1 (perl6.moarvm:<main>)
from <unknown>:1 (perl6.moarvm:<entry>)
Makefile:437: recipe for target 'CORE.setting.moarvm' failed
make[1]: *** [CORE.setting.moarvm] Error 1
make[1]: Leaving directory '/tmp/packerbuild-1000/rakudo-star/rakudo-star/src/rakudo-star-2016.01/rakudo'
Makefile:43: recipe for target 'rakudo/perl6-m' failed
make: *** [rakudo/perl6-m] Error 2
==> ERROR: A failure occurred in build().
The build failed.

rafalp commented on 2015-12-07 11:36

This package is broken. perl6 yields errors on my machine:

$ perl6
/usr/bin/perl6: line 2: /tmp/yaourt-tmp-tester/aur-rakudo-star/src/rakudo-star-2015.11/install/bin/moar: No such file or directory

It looks like it searches for moar in the temporary build directory instead of /usr/bin. Perhaps because the whole packaging process is merely a

cp "$srcdir"/"$pkgname-$pkgver"/install/bin/* /usr/bin/


dWolf commented on 2014-06-26 16:29

When I have remove parrot dependances (I need only moar) panda doesn't work at all :(

smls commented on 2013-12-21 19:10

The "rakudo-star" AUR package seems to be a very outdated duplicate of the "rakudo" package. They should probably be merged.

smls commented on 2013-12-21 19:09

The "rakudo-star" AUR package seems to be a very outdated duplicate of the "raduko" package. They Should probably be merged.

Anonymous comment on 2012-10-30 08:23


Would the maintainer of this package be interested in an updated PKGBUILD for Rakudo * 2012.10? I have one laying around...

Anonymous comment on 2011-09-27 11:31

There's a 2011.07 release available now at It requires Parrot 3.6.0 to build, though, and the latest version of Parrot in [community] is 3.3.0.

konstantin commented on 2011-02-12 04:06

Rakudo still needs parrot to run.
I've added it to runtime depencies.

konstantin commented on 2011-02-12 02:43

As far as I know rakudo needs parrot to run.
I've added it to runtime depencies.

konstantin commented on 2011-02-12 02:36

As far as I know rakudo needs parrot to run.
I've added it to runtime depencies.

spider-mario commented on 2011-02-11 22:54

The runtime parrot dependency shouldn’t have been removed, should it? After running “yaourt -Qdt” and removing unneeded dependencies, running “perl6” prints:

perl6: error while loading shared libraries: cannot open shared object file: No such file or directory

Anonymous comment on 2011-01-21 15:59

Please don't flag this package out-of-date when it's actually not. This one packages the rakudo-star tarball as published on and . I know that the current *rakudo* release seems to be 2011.01, but rakudo-star is still at 2010.12. I'll update this package when there's an update on the front page.