Skip Menu |

This queue is for tickets about the Coro CPAN distribution.

Report information
The Basics
Id: 57133
Status: resolved
Priority: 0/
Queue: Coro

People
Owner: Nobody in particular
Requestors: DOUGDUDE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 5.22
Fixed in: (no value)



Subject: Doesn't seem to work in Strawberry Perl 5.12 April 2010 release
So I just upgraded my Strawberry Perl not only to the new April 2010 release, but also to 5.12.0. Something seems to have changed in the gcc toolchain, as Coro will no longer compile with the <w>indows option, nor the <a>sm option (I also tried all other for some reason and none worked). 1) For the <w>indows option (which is the default), here is what I get: gcc -c -s -O2 -DWIN32 -DHAVE_DES_FCRYPT -DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -fno-strict-aliasing -mms-bitfields -DPERL_MSVCRT_READFIX -s -O2 -DVERSION=\"5.22\" -DXS_VERSION=\"5.22\" "-IC:\strawberry\perl\lib\CORE" -DCORO_LOSER -DCORO_STACKSIZE=16384 -DCORO_STACKGUARD=4 State.c State.xs: In function 'free_coro_mortal': State.xs:1149: warning: initialization discards qualifiers from pointer target type State.xs: In function 'transfer': State.xs:1603: error: too few arguments to function '_setjmp' dmake: Error code 129, while making 'State.o' dmake: Error code 255, while making 'subdirs' 2) For the <a>sm option, here is what I get: C:\strawberry\perl\bin\perl.exe C:\strawberry\perl\lib\ExtUtils\xsubpp -typemap C:\strawberry\perl\lib\ExtUtils\typemap -typemap typemap State.xs > State.xsc && C:\strawberry\perl\bin\perl.exe -MExtUtils::Command -e "mv" -- State.xsc State.c gcc -c -s -O2 -DWIN32 -DHAVE_DES_FCRYPT -DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -fno-strict-aliasing -mms-bitfields -DPERL_MSVCRT_READFIX -s -O2 -DVERSION=\"5.22\" -DXS_VERSION=\"5.22\" "-IC:\strawberry\perl\lib\CORE" -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_STACKGUARD=4 State.c State.xs: In function 'free_coro_mortal': State.xs:1149: warning: initialization discards qualifiers from pointer target type C:\Users\Douglas\AppData\Local\Temp\cc21RloD.s: Assembler messages: C:\Users\Douglas\AppData\Local\Temp\cc21RloD.s:5: Warning: .type pseudo-op used outside of .def/.endef ignored. C:\Users\Douglas\AppData\Local\Temp\cc21RloD.s:5: Error: junk at end of line, first unrecognized character is `c' dmake: Error code 129, while making 'State.o' dmake: Error code 255, while making 'subdirs' Now, the deep magic in the setjmp issue I can't figure out, but I did get the <a>sm option to work by modifying the top of the assemble code in coro.c: .globl coro_transfer .type coro_transfer, @function coro_transfer: to .globl _coro_transfer .def _coro_transfer; .scl 2; .type 32; .endef _coro_transfer: which seems to be the syntax for my platform. Not sure what you want to do here, but I wanted to inform you. I love your module!
Subject: Re: [rt.cpan.org #57133] Doesn't seem to work in Strawberry Perl 5.12 April 2010 release
Date: Sun, 2 May 2010 11:38:49 +0200
To: Douglas Christopher Wilson via RT <bug-Coro [...] rt.cpan.org>
From: Marc Lehmann <schmorp [...] schmorp.de>
Hi! You sent a possible bug report on or via rt.cpan.org. Please read this mail carefully if you want to be heard. Most likely, your report will be ignored. Please close the ticket again and sent it to the official contact address for the module in question (or send it to rt.cpan.org@schmorp.de). Why is this necessary? rt.cpan.org has many deficiencies which makes it tedious and hard to use, increasing the workload on the people who provide all the perl modules you probably appreciate (and that is really to be avoided - module authors should be able to invest all their time into improving their modules and not fighting with rt.cpan.org's bugs). Still, for some people, rt.cpan.org is useful to have, and some people even like it and really want to use it. That is fine, too. Unfortunately, the designers of rt.cpan.org didn't make their "service" optional - you can neither opt-in nor opt-out of rt.cpan.org as a module author. Just like a spammer, rt.cpan.org forces its "service" (whether wanted or unwanted) on everybody. Just like a spammer, they don't care for the people they actively hurt. Just like a spammer, they don't don't care to fix these issues and make their "service" ethically acceptable. You cannot even configure it to redirect tickets to somewhere else. Unfortunately, ignoring rt.cpan.org is not an option either: for people reporting possible bugs there is no indication that their report will be ignored, and for module authors it means they miss possibly vital bug reports (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module unmaintained when in fact the opposite might be true). This is why it is important that you delete/resolve your ticket. I am sorry that this wasted a bit of your time, but please understand that I am just as much a victim as you are - the problem is the unethical stance of the rt.cpan.org providers who force their "service" on everybody. Please redirect your bug report as stated in the beginning of this mail, and please consider petitioning the rt.cpan.org providers to stop their unethical behaviour and allow opt-in, opt-out, or some redirect option. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de>
I discussed this on IRC and am closing this ticket.