Craig,

> Congratulations, Martin.  That is really an achievement.

Thank you. It wasn't too hard; the C sources are quite portable.
The biggest part was a script (perl, of course) that transforms the Makefile
generated into an MMK description file (I think the Parrot build process
triggers an MMS bug that manifests in choosing the wrong source file for a
target, that's why I switched to MMK).

However, I'm not finished yet. There's more work in it...

Parrot wants dynamic PMCs as dynamically loadable files, i.e. shared images.
Building of these already works, but of course a lib$find_image_symbol won't
find any symbols (as I don't yet have a SYMBOL_VECTOR).

So I'm now diving into the process that converts a .PMC file into a .C file
to see where I can get a list of symbols from to create an options file to
link against. That seemed easier (and more portable) than pulling apart
object files.

>> And as VAXman is a big fan of VAXen, I will keep compatability towards
>> OpenVMS VAX 7.2 in mind
>> (as that's what his main machine FAFNER.dyndns.org is running under).
>
> Can Parrot really function without IEEE floating point and 64-bit integers?

I'll have a go at it over the weekend, and report back.

cu,
  Martin

Reply via email to