Hi Nick, Nick Glencross via RT wrote:
Yes, there's a problem building dynclasses on cygwin. [I think that there are a few related calls logged] One quick hack to complete the build is to type 'echo all: > src/dynclasses/Makefile' after running Configure.pl.
Many thanks. I shall do that in the meantime.
I've spent quite a bit of time researching the best solution to the cygwin build; whether it should be more UNIX or more Windows-like. All indicators have seemed to point to libparrot needing to be a DLL, which doesn't build too well at the moment. A fortnight ago or so I looked into the way that perl builds on cygwin. It's clear that it prefers to build a DLL, and uses the ld --out-implib flag to create a .dll.a file which the dynclasses link against to resolve the required symbols. Rerunning Configure by choosing to statically build libperl causes a build failure, so I'm still of the thinking that we need a shared libparrot.
A shared libparrot seems most desireable in any case. One can certainly imagine many instances running simultaneously.
Justin: This is certainly a problem that needs solving. We can join forces if you like...
I admit I'll need to do some work to get up to speed on the issues involved, but I will do what I can. Now that I have a partial build, I'll play around with Parrot in general so as to understand where dynclasses fits in the big picture. And after Christmas, I should have some time to devote.
Cheers, Justin
