Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

rurban (7989)

  reversethis-{ta.yar-x} {ta} {nabrur}

cygwin maintainer for perl, parrot, clisp, postgresql, ... and some perl modules (perl-libwin32, perl-Win32-GUI). Has also some hairy CPAN packages: B::C, B::Generate, C::DynaLib, B::Debugger ...

Journal of rurban (7989)

Saturday August 23, 2008
11:56 AM

cygwin parrot-0.7.0-1 released

[ #37260 ]

After several days of hacking and testing I could release the cygwin package for parrot-0.7.0 with a lot of patches:

The new exception code only affected dotnet, which I fixed with #58176-dotnet-exceptions.patch

Most problems came from languages which were not included in my huge #56554-make-install-lang.patch yet. make languages installable and add the actions to their makefiles.
I finished this treatment now for all langs, just a few are still misbehaving and I gave up on m4, pipp, tcl, pheme and forth.

I described it at

Interesting is

$ parrot-forth
Could not find non-existent sub _config
current instr.: ' init' pc 944 (forth.pir:11)
called from Sub 'main' pc 1033 (forth.pir:55)

which looks like that pbc_to_exe already solved the _config bootstrap problem, but fails.

$ parrot-pipp.exe
Parrot VM: Can't stat /usr/src/perl/parrot/parrot-0.7.0-1/build/languages/pipp/s
rc/common/pipplib.pbc, code 2.
Unable to append PBC to the current directory
current instr.: 'parrot;Pipp;__onload' pc 55 (src/common/pipp.pir:95)
called from Sub 'parrot;Pipp;pipp' pc -1 ((unknown file):-1)

$ parrot-pheme.exe
"load_bytecode" couldn't find file 'compilers/tge/TGE/Rule.pbc'
current instr.: 'parrot;TGE;__onload' pc 19 (TGE.pir:94) called from Sub 'parrot;Pheme::AST::Grammar;__onload' pc 6901 (languages/pheme/lib/ASTGrammar.pir:5)
called from Sub 'parrot;Pheme::Compiler;main' pc -1 ((unknown file):-1)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.