jimmy@jimmy-virtual-machine ~/panda $ ../MoarVM/install/bin/perl6-m bootstrap.pl
==> Bootstrapping Panda
/bin/sh: 1: perl6-m: not found
Do we have a problem when we would hardcode the path of the binary? Are there possible cases where the binary would be installed to another location (in PATH), that should be picked up by scripts like these?
Using $*EXECUTABLE should be a fix for this issue.
Three things to mention about $EXECUTABLE
1) it is just a few commits old
2) it is an absolute IO::Path object
3) as of now it only does the right thing after rakudo was installed on moar/jvm, since it points to `.../install/bin/perl6-`. On parrot it always returns the currently running interpreter.
I hope to invalidate 3) soon, but I don't know how yet.
As a sidenote: doing s/$*EXECUTABLE_NAME/$*EXECUTABLE/ unbreaks panda on r-j star and r-m star.
s/EXECUTABLE_NAME/EXECUTABLE/ (for GH #73)
This lets us use panda with a perl6 that isn't in the current path.
Fixed now, retupmoca++