On Sun, Sep 20, 2009 at 05:38:22PM -0700, m...@purdue.edu (via RT) wrote: > # New Ticket Created by m...@purdue.edu > # Please include the string: [perl #69252] > # in the subject line of all future correspondence about this issue. > # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=69252 > > > > SUMMARY > > On Fedora 11 I get > > ../../parrot ../../runtime/parrot/library/PGE/Perl6Grammar.pir > --output=PGE/builtins_gen.pir PGE/builtins.pg > gmake[1]: *** [PGE.pbc] Segmentation fault > > Am I doing something wrong?
Two possibilities: Possibility 1: Any chance that you have a previous version of Parrot installed on your system? I'm guessing that Parrot's build process is finding the wrong version of libparrot and using that, resulting in the segfault. The problem is very unlikely to be in PGE itself; PGE is often just the first significant component to be built using the newly created Parrot executable and so lots of build errors tend to show themselves there. I suggest looking for a previous install or build of Parrot on the system (including one possibly from an rpm install), and if found, remove it. Possibility 2: Is your installation of Fedora running with SELinux enabled? If yes, Parrot's JIT implementation has difficulty dealing with SELinux and often simply results in a segfault, and that may be what is happening here. Your Configure.pl output coming from Parrot says: > ... > auto::isreg - Does your C library have a working S_ISREG..........yes. > auto::arch - Determine CPU architecture and OS..................done. > auto::jit - Determine JIT capability...p = 0x810a000 PAGE_SIZE = > 4096 (0x1000) > failure: Permission denied > .........................yes. Perhaps try building Rakudo using the following command instead: $ perl Configure.pl --gen-parrot --gen-parrot-option=--jitcapable=0 Shortly after the 1.6.0 release of Parrot this last week we've completely disabled the jit features of Parrot, so future versions of Parrot shouldn't have this problem. Hope one of these two help resolve the problem. If not, then let me know and I'll install Fedora 11 on one of my boxes and see if I can track it down a bit further. Thank you for the very helpful bug report! Pm
