Segfaults building Rakudo

[Gerd Pokorra]

When making Parrot releases I execute a simple script from time to time
that download a complete new Parrot and Rakudo repository and build
both. I do not know if there is a more efficient way. I heard from
plumage but never tried it for this. Are where any other languages a
Parrot release manager should look for or will the maintainer of the
language look that it work on the current Parrot repository?

Gerd


Am Donnerstag, den 14.04.2011, 20:20 +0200 schrieb Patrick R. Michaud: 
> On Thu, Apr 14, 2011 at 10:32:38AM -0700, Jonathan Duke Leto wrote:
> > Could you give us the exact incantation for how to compile Rakudo and run the
> > test suite with the correct paramters, such that the data will be 
> > useful to you and others debugging this?
> 
>     $ git clone https://github.com/rakudo/rakudo.git
>     ...
>     $ cd rakudo
>     $ perl ./Configure.pl --parrot-config=path/to/install/bin/parrot_config
>     ...
>     $ make spectest
> 
> Pm
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev


-------------- next part --------------
A non-text attachment was scrubbed...
Name: rakudo-check.sh
Type: application/x-shellscript
Size: 670 bytes
Desc: not available
URL: <http://lists.parrot.org/pipermail/parrot-dev/attachments/20110414/7b58c217/attachment.bin>