>>> Compiling source in /var/tmp/portage/dev-lang/nqp-2013.03/work/nqp-2013.03 ... make -j5 -j1 perl tools/build/generate-constants.pl > nqp_const.pir /usr/bin/perl5.16.2 /usr/lib64/parrot/5.1.0/tools/build/pmc2c.pl --no-lines --dump --include src/pmc --include /usr/src/parrot/5.1.0 --include /usr/src/parrot/5.1.0/pmc src/pmc/stable.pmc src/pmc/sixmodelobject.pmc src/pmc/nqplexinfo.pmc src/pmc/nqplexpad.pmc src/pmc/serializationcontext.pmc src/pmc/ownedhash.pmc src/pmc/ownedresizablepmcarray.pmc src/pmc/qrpa.pmc make: /usr/bin/perl5.16.2: Command not found make: *** [src/pmc/nqp_group.so] Error 127 emake failed * ERROR: dev-lang/nqp-2013.03 failed (compile phase): * (no error message) # ls /usr/bin/perl5* /usr/bin/perl5.16.3 It took some strace-ing to figure out that the name of the perl 5 binary apparently is stored somewhere in parrot. perl6-nqp-f6738e7/tools/lib/NQP/Configure.pm contains source code for a file parrot-config.pir which is written, executed using parrot and then unlinked again. That execution does, among others, echo the following setting: parrot::perl=/usr/bin/perl5.16.2 So it seems that after every upgrade of perl 5, the whole perl 6 toolchain consisting of parrot, nqp and rakudo have to be re-merged. The perl-cleaner --all invocation which I performed did not catch this fact. It would be nice if it were able to do so.
We will need more information to resolve this. Please attach the complete build log, that way we can see why it picks the wrong version; also reply with the output of `emerge --info =dev-lang/nqp-2013.03`. Thank you in advance.
Created attachment 344152 [details] build log
Created attachment 344154 [details] emerge --info
> Please attach the complete build log, that way we can see why it > picks the wrong version I doubt that the build log will tell you more than my strace investigations. After remerging parrot, I'm back to bug #459840.(In reply to comment #1)
(In reply to comment #4) > I doubt that the build log will tell you more than my strace investigations. Heh, indeed a short build log; thank you for the information output.
This should be fixed starting with perl-5.20.1-r4 (now perl${PV} is a symlink to perl, not the other way around). (Patrick please reopen if you think otherwise.)
