On Mon, Dec 13, 2010 at 8:05 AM, Dichi <[email protected]> wrote: > Thanks kid51++ for that report. > > Looking at it briefly it looks like the failures are related either to the > *wording* of some error messages or the exe's ( parrot, ... ) exiting > without an error exit code. I'll try to fix them in the course of this week. > > Said that, I'm more concerned of Parrot not building in OSX. Will, since I > don't have access to any OSX HW can you send me the full output of "make" so > I can see what's going on? > > Thanks. > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > >
Full output of build script at: http://nopaste.snit.ch/27037 The segfault is in: ./pbc_merge -o runtime/parrot/library/PCT/PAST.pbc \ compilers/pct/src/PCT/Node.pbc \ compilers/pct/src/PAST/Node.pbc \ compilers/pct/src/PAST/Compiler.pbc \ compilers/pct/src/POST/Node.pbc \ compilers/pct/src/POST/Compiler.pbc Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x00000000015090d0 0x00000001000468f4 in Parrot_block_GC_mark () (gdb) bt #0 0x00000001000468f4 in Parrot_block_GC_mark () #1 0x0000000100000b19 in main () -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
