2008/7/16 Will Coleda <[EMAIL PROTECTED]>: > On Wed, Jul 16, 2008 at 2:31 AM, Reini Urban via RT > <[EMAIL PROTECTED]> wrote: >> 2008/7/15 Reini Urban <[EMAIL PROTECTED]>: >>> Will Coleda via RT schrieb: >>>> On Tue May 13 05:21:32 2008, rurban wrote: >>>>> 2008/5/13 Andrew Whitworth via RT <bugs-parrot- >>>>> [EMAIL PROTECTED]>: >>>>>> >>>>>> is this ticket (#51944) resolved? I don't see any outstanding todo >>>>> >>>>> items >>>>>> >>>>>> here that need to be considered further, and the submitted patch >>>>> >>>>> has >>>>>> >>>>>> already been applied. Can we close this, or is this a placeholder >>>>> >>>>> for us >>>>>> >>>>>> to further improve cygwin documentation? >>>>> >>>>> The list os build preq's is required. >>>>> >>>>> Well, the tip for smoke to do cpan Test::TAP::HTMLMatrix >>>>> could be added. But this should be added in the general README for all >>>>> platforms. >>>>> >>>>> Then platform specific is only that pg.t fails due to missing loadlib >>>>> exceptions >>>>> and that cygwin perl-5.10.0 fails to send the smoke report. perl-5.8.8 >>>>> works ok. >>>>> >>>>> I'll send that as extra README_cygwin.pod patch. >>>> >>>> ENOPATCH. =-) >>>> >>>> Can someone with cygwin access go through the README once more so we can >>>> get this ticket closed? Thanks. >>> >>> Ok, since there's now almost an official parrot package, the updates are >>> easy. >>> Patch attached. >>> >>> The parrot-0.6.4-1 packages are in the works. >> >> I found a better link for the SDL link. >> Yesterday the http://cygwinports.dotsrc.org/ site was down, but now it >> is up again. >> >> Please use the attached revised patch instead. > > This looks good; I'd ask you double check which deps are required vs. > optional: I'm pretty sure we don't -require- any of those packages. > Ditto for their correspond build deps. (e.g. libgdbm-devel)
Note, there are more cygwin-side updates to come to this README, which I will commit after my parrot-0.6.4 release (in 1-2 days). In which pod should we document the non-windows package requirements? Most of those packages have similar names anyway for every unix/posix platform. > parrot is recursively listed as a build requirement oops. > For the optional items, perl's Moose should be on the list (for > smartlink), and Test::Perl::Critic/Perl::Critic for the critic tests. > (Honestly we should have this documented somewhere else and just refer > to it from here.) Good. Where? > Here are some notes about the build/tests.. > > ** I get this warning on configure: > > Determining CPU architecture and OS...................................done. > Determining JIT capability... 10 [main] test 1944 > _cygtls::handle_exceptions > : Error while dumping state (probably corrupted stack) > 10 [main] test 4596 _cygtls::handle_exceptions: Error while dumping state > ( > probably corrupted stack) > ..........................................yes. There's a cygwin jit patch outstanding. [perl #56824] [PATCH] Configure - fix SEGV in JIT has_exec_protect test on Cygwin > Generating CPU specific stuff.........................................done. > Verifying that the compiler supports function pointer casts............yes. > > ** Get a similar error running t/src/extend.t > > ** Bug in t/doc/pod.t - few warnings of the type: > > Error: /cygdrive/d/sandbox/parrot/pbc_to_exe is unreadable: No such file or > dire > ctory Yes, this needs to be fixed, but it's not so urgent. Just the test is wrong. > ... But all tests pass. More urgent for me is fixing the .include search path. [perl #56996] [TODO] remove non FHS-compliant searchpaths -- Reini Urban http://phpwiki.org/ http://murbreak.at/
