Red Hat Bugzilla – Bug 1478370
perl6 --profile-compile raises "No such file or directory" error
Last modified: 2017-09-09 19:49:41 EDT
Description of problem:
When running the Fedora-provided perl6 program on any perl 6 script with --profile-compile, it fails because it cannot find a certain template html file.
Example for hello world program (first line is of course simply program output):
$ perl6 --profile-compile test.pl6
Writing profiler output to profile-1501851048.16309.html
Failed to open file /usr/share/nqp/lib/profiler/template.html: No such file or directory
The profiler output html file is still created, but remains empty.
Version-Release number of selected component (if applicable): rakudo-0.2017.06-1.fc26
How reproducible: Always
Steps to Reproduce:
1. Run `perl6 --profile-compile scriptname' on any Perl 6 script
Actual results: Stated above.
Expected results: Profiler information written to html file.
The missing file is at an other place and belongs to the nqp package:
$ rpm -ql nqp | grep template
As work around you can create a symbolic link to it:
$ mkdir -p /usr/share/nqp/lib/profiler
$ ln -s /usr/lib64/nqp/profiler/template.html /usr/share/nqp/lib/profiler/template.html
$ perl6 --profile-compile -e "say 7"
Writing profiler output to profile-1501860118.87252.html
This bug will be fixed with the packages of the next release from rakudo.
New fedora packages will be build with the August release of rakudo (2017.08) and not available before the end of August.
moarvm-0.2017.08.1-1.fc26, nqp-0.0.2017.08-1.fc26, rakudo-0.2017.08-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7e04095858
moarvm-0.2017.08.1-1.fc26, nqp-0.0.2017.08-1.fc26, rakudo-0.2017.08-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.