I have recently installed parrot from svn, but get errors during
make. I see the same errors on a x86 running unstable Debian, and
a sparc running Gentoo.
typing perl Configure.pl && make ends with:
gmake -C compilers/past-pm
gmake[1]: Entering directory
`/home/bob/src/parrot/compilers/past-pm'
/usr/bin/perl5.8.8 -MExtUtils::Command -e rm_rf PAST-pm.pbc
../../runtime/parrot/library/PAST-pm.pbc
No root path(s) specified at
/usr/lib/perl5/5.8.8/ExtUtils/Command.pm line 105
../../parrot ../../compilers/tge/tgc.pir
--output=POST/Grammar_gen.pir POST/Grammar.tg
PackFile_unpack: Bytecode not valid for this interpreter:
fingerprint mismatch
Parrot VM: Can't unpack packfile
/home/bob/src/parrot/./compilers/tge/TGE/Rule.pbc.
PackFile_unpack: Bytecode not valid for this interpreter:
fingerprint mismatch
Parrot VM: Can't unpack packfile
/home/bob/src/parrot/./compilers/tge/TGE/Tree.pbc.
PackFile_unpack: Bytecode not valid for this interpreter:
fingerprint mismatch
Parrot VM: Can't unpack packfile
/home/bob/src/parrot/./compilers/tge/TGE/Parser.pbc.
PackFile_unpack: Bytecode not valid for this interpreter:
fingerprint mismatch
Parrot VM: Can't unpack packfile
/home/bob/src/parrot/./compilers/tge/TGE/Grammar.pbc.
Class 'TGE::Grammar' doesn't exist
current instr.: 'parrot;TGE::Compiler;__onload' pc 2
(TGE/Compiler.pir:16)
called from Sub 'parrot;TGE;__onload' pc 12 (TGE.pir:91)
called from Sub 'main' pc 3 (../../compilers/tge/tgc.pir:30)
gmake[1]: *** [PAST-pm.pbc] Error 1
gmake[1]: Leaving directory `/home/bob/src/parrot/compilers/past-pm'
make: *** [compilers.dummy] Error 2
bob@spain:~/src/parrot$ svn update
At revision 15883.
I'm unsure how to proceed.
Bob
--
Paranoia is simply an optimistic outlook on life.
The "Bytecode not valid for this interpreter" means that parrot
is finding a .pbc file somewhere that is from an older
(and incompatible) version of Parrot. So, I'd say that either:
1. you need to run "make realclean" before running Configure.pl
and starting the build, to get rid of any old .pbc files, or
2. there's an earlier version of Parrot installed somewhere
(e.g., from a previous "make install"), and the build process
is inadvertently picking up the files from that previous
installation.
FWIW, most of us who are working with svn head recommend against
ever performing a 'make install', just to avoid Parrot getting
confused by multiple incompatible versions.
Pm
Hi Jonathan
Yes it built fine once I'd done tha
Bob
--
Q: How many lawyers does it take to change a light bulb?
A: One. Only it's his light bulb when he's done.