That said, I get the same error you do with that patch. 

cd /tmp
curl -sSL 'http://search.cpan.org/CPAN/authors/id/M/ML/MLEHMANN/Coro-6
+.49.tar.gz' | tar xz
cd Coro-6.49
curl -sSL 'http://markmail.org/download.xqy?id=a5n4rqivzbn5zsqp&number
+=1' | patch -p1
perl Makefile.PL
make test

[download]
...
State.xs: In function 'coro_sig_copy':
State.xs:1144:3: warning: return makes integer from pointer without a 
+cast [enabled by default]
State.xs: In function 'runops_trace':
State.xs:1430:27: error: 'struct block_sub' has no member named 'argar
+ray'
make[1]: *** [State.o] Error 1
make[1]: Leaving directory `/home/ikegami/tmp2/Coro-6.49/Coro'
make: *** [subdirs] Error 2

[download]

Coro's author doesn't use a public RT, so I can't tell if anyone's addressed this already.

In reply to Re^2: Coro woes by ikegami
in thread Coro woes by runrig

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.