Updated ebuild, some deps got tracked correctly, the language support is still missing and the install phase is still hackish.
Created attachment 172032 [details] parrot 0.8.0 initial ebuild First try
Created attachment 172070 [details, diff] Fix parallel make issues
Created attachment 179314 [details] New ebuild This one get you a possibly working parrot and perl6 BUT: - faulty build if you are using distcc - pollutes /usr with bogus directories. - no cardinal there yet (I'll add it later)
After adding ~x86 to the keywords, the 0.9.0 ebuild fully compiles without errors, however, perl6 won't run. I get... "load_bytecode" couldn't find file 'PCT.pbc' current instr.: '' pc 148 (src/classes/Object.pir:20) called from Sub 'parrot;Perl6;Compiler;main' pc -1 ((unknown file):-1) Any ideas? Thanks
On further investigation PCB.pct in installed in /usr/runtime/parrot/library/PCT.pbc and if I change directory to /usr/runtime/parrot/library and run perl6 I get a different error... "load_bytecode" couldn't find file 'PGE/Dumper.pir' current instr.: 'parrot;PGE;Match;' pc 2 (compilers/pge/PGE/Match.pir:15) called from Sub 'parrot;PCT;Grammar;onload' pc 0 (src/PCT/Grammar.pir:41) called from Sub 'parrot;PCT;__onload' pc 0 (PCT.pir:15) called from Sub '' pc 148 (src/classes/Object.pir:20) called from Sub 'parrot;Perl6;Compiler;main' pc -1 ((unknown file):-1) Am I looking for an @INC equivalent in perl6? :-)
Ok, http://svn.perl.org/parrot/trunk/languages/perl6/README suggests that the executable needs a copy of the source tree in order to work: > This binary executable feature is still somewhat experimental, > and may not work on all platforms. Also, the binary has hardcoded > paths to the Parrot build tree (especially the dynamic libraries > and modules), so removing the build tree will cause the binary > to stop working. However, invoking parrot directly works fine: parrot /usr/languages/perl6/perl6.pbc test.pl Cheers
0.9.1 is out and 1.0 is slated for the next week, hopefully I'll update the ebuild soon, most of the languages are now in separated repos.
*** Bug 234007 has been marked as a duplicate of this bug. ***
Created attachment 185615 [details] parrot 1.0.0 ebuild parrot-1.0.0 now has the following issues: - miscompile with distcc for yet to be discovered reasons - doesn't install with make -jN
hmm, I'm interested in the python interpreter version 1.0 brings :)
Test Summary Report ------------------- t/library/pcre.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=398, Tests=11703, 1425 wallclock secs ( 3.24 usr 0.40 sys + 99.00 cusr 31.70 csys = 134.34 CPU) Result: FAIL make: *** [test] Error 1 * * ERROR: dev-lang/parrot-1.0.0 failed.
meanwhile, parrot 1.1.0 was released. it builds and installs fine, but to also install some essential development files, the install target needs to be modified to install-dev
Created attachment 192372 [details] parrot 1.2.0 ebuild Updated ebuild, it won't let you build rakudo out of box and leaks the build dir in parrot_config --dump and other places, I'll have a look on it later. where is the python parrot today btw?
There are some changes that could be useful in https://trac.parrot.org/parrot/ticket/712, right now they do not solve parrot_config having portage build dir paths inside itself.
Looks like http://code.google.com/p/pynie/ is the most up-to-date Python-on-Parrot.
Test Summary Report ------------------- t/steps/auto_icu-01.t (Wstat: 256 Tests: 136 Failed: 1) Failed test: 132 Non-zero exit status: 1 t/library/pcre.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=395, Tests=11710, 427 wallclock secs ( 5.19 usr 1.06 sys + 108.28 cusr 49.23 csys = 163.76 CPU) Result: FAIL make: *** [test] Error 1 * * ERROR: dev-lang/parrot-1.2.0 failed. Still testfailures, but it's looking much better already.
+*parrot-1.3.0 (27 Jun 2009) + + 27 Jun 2009; Patrick Lauer <patrick@gentoo.org> +parrot-1.3.0.ebuild: + Bump to 1.3.0. Closes #247125 Still test failures, but that's a lot better than 0.6.stoneage :)