On 12/21/05, via RT Justin Koser <[EMAIL PROTECTED]> wrote: > # New Ticket Created by Justin Koser > # Please include the string: [perl #37997] > # in the subject line of all future correspondence about this issue. > # <URL: https://rt.perl.org/rt3/Ticket/Display.html?id=37997 > > > > Hello Parrot hackers, > > I'm trying to build Subversion revision 10604 of Parrot on Cygwin, and > everything seems fine until I end up with a bunch of linker errors. > Below, please find the contents of `myconfig' and some of the build > output. Naturally, I'm willing to help solve this in any way that I can. > > Thanks, > Justin
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. 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. Justin: This is certainly a problem that needs solving. We can join forces if you like... Nick
