Bug #115364 for Coro: Build failure with perl 5.24

Thu Jun 16 07:02:39 2016 dimitri.pekarovsky [...] gmail.com - Ticket created

Subject:	Build failure with perl 5.24
Date:	Thu, 16 Jun 2016 13:01:59 +0200
To:	bug-Coro [...] rt.cpan.org
From:	ДП <dimitri.pekarovsky [...] gmail.com>

This is perl 5, version 24, subversion 0 (v5.24.0) built for x86_64-linux-thread-multi Running Mkbootstrap for Coro::State () chmod 644 "State.bs" "/usr/bin/perl" "/usr/share/perl5/core_perl/ExtUtils/xsubpp" -typemap "/usr/share/perl5/core_perl/ExtUtils/typemap" -typemap "typemap" State.xs > State.xsc && mv State.xsc State.c Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values in State.xs, line 3666 cc -c -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" -fPIC "-I/usr/lib/perl5/core_perl/CORE" -DCORO_ASM -DCORO_STACKSIZE=16384 -DCORO_GUARDPAGES=4 -DCORO_JIT=1 State.c In file included from /usr/lib/perl5/core_perl/CORE/perl.h:5554:0, from State.xs:12: State.xs: In function ‘runops_trace’: State.xs:1355:91: error: ‘struct block_sub’ has no member named ‘argarray’; did you mean ‘savearray’? PUSHs (CxHASARGS (cx) ? sv_2mortal (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); ^ /usr/lib/perl5/core_perl/CORE/pp.h:451:28: note: in definition of macro ‘PUSHs’ #define PUSHs(s) (*++sp = (s)) ^ State.xs:1355:51: note: in expansion of macro ‘sv_2mortal’ PUSHs (CxHASARGS (cx) ? sv_2mortal (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); ^~~~~~~~~~ /usr/lib/perl5/core_perl/CORE/sv.h:1970:23: note: in expansion of macro ‘newRV’ #define newRV_inc(sv) newRV(sv) ^~~~~ State.xs:1355:63: note: in expansion of macro ‘newRV_inc’ PUSHs (CxHASARGS (cx) ? sv_2mortal (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); ^~~~~~~~~ State.xs: In function ‘boot_Coro__State’: State.xs:3469:81: error: assignment of member ‘svt_get’ in read-only object orig_sigelem_get = PL_vtbl_sigelem.svt_get; PL_vtbl_sigelem.svt_get = coro_sigelem_get; ^ State.xs:3470:81: error: assignment of member ‘svt_set’ in read-only object orig_sigelem_set = PL_vtbl_sigelem.svt_set; PL_vtbl_sigelem.svt_set = coro_sigelem_set; ^ State.xs:3471:81: error: assignment of member ‘svt_clear’ in read-only object orig_sigelem_clr = PL_vtbl_sigelem.svt_clear; PL_vtbl_sigelem.svt_clear = coro_sigelem_clr; ^ make[1]: *** [Makefile:405: State.o] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-dimytch/aur-perl-coro/src/Coro-6.39/Coro' make: *** [Makefile:611: subdirs] Error 2

Thu Jun 16 08:05:00 2016 schmorp [...] schmorp.de - Correspondence added

Subject:	Re: [rt.cpan.org #115364] Build failure with perl 5.24
Date:	Thu, 16 Jun 2016 14:04:46 +0200
To:	ДП via RT <bug-Coro [...] rt.cpan.org>
From:	Marc Lehmann <schmorp [...] schmorp.de>

Hi! Please send your bug report to the official contact/author address for the module in question (or send it to rt.cpan.org@schmorp.de, that's fine as well). What follows is the rationale for this request, you don't have to read it if you don't care. 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 potentially vital bug reports such as yours (and of course it's a great impression if rt.cpan.org has lots of bug reports that are unanswered, making a module look unmaintained when in fact the opposite might be true). 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. One last issue: many people mail me that this can be "fixed" by including the bugtracker element in my module meta file. This is not true: 1. This field only affects search.cpan.org and maybe similar services. (Many people confuse rt.cpan.org with search.cpan.org for some reason). 2. It doesn't even work (there are still links to rt.cpan.org displayed). 3. Even if search.cpan.org does no longer display the link, it doesn't actually affect rt.cpan.org (and tests have shown that people go to rt.cpan.org regardless) Even *iff* rt.cpan.org would start listening on the bugtracker field, however, it's still wrong. I have a lot of modules, and each time a service like rt.cpan.org comes out, I would have to make dummy releases for all my modules. This not only creates a lot of extra work for me (I take releases very seriously) but also users, who would wonder why there is a new release. Thanks a lot, Marc Lehmann <rt.cpan.org@schmorp.de> Last updated: 2012-04-22

Thu Jun 16 08:05:01 2016 The RT System itself - Status changed from 'new' to 'open'

Wed Jun 22 16:17:11 2016 alexchandel [...] gmail.com - Correspondence added

From:

alexchandel [...] gmail.com

On Thu Jun 16 07:02:39 2016, dimitri.pekarovsky@gmail.com wrote: Show quoted text

> This is perl 5, version 24, subversion 0 (v5.24.0) built for > x86_64-linux-thread-multi > > Running Mkbootstrap for Coro::State () > chmod 644 "State.bs" > "/usr/bin/perl" "/usr/share/perl5/core_perl/ExtUtils/xsubpp" -typemap > "/usr/share/perl5/core_perl/ExtUtils/typemap" -typemap "typemap" > State.xs > State.xsc && mv State.xsc State.c > Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values in > State.xs, line 3666 > cc -c -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe > -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE > -D_FILE_OFFSET_BITS=64 -march=x86-64 -mtune=generic -O2 -pipe > -fstack-protector-strong -DVERSION=\"6.39\" -DXS_VERSION=\"6.39\" > -fPIC "-I/usr/lib/perl5/core_perl/CORE" -DCORO_ASM > -DCORO_STACKSIZE=16384 -DCORO_GUARDPAGES=4 -DCORO_JIT=1 State.c > In file included from /usr/lib/perl5/core_perl/CORE/perl.h:5554:0, > from State.xs:12: > State.xs: In function ‘runops_trace’: > State.xs:1355:91: error: ‘struct block_sub’ has no member named > ‘argarray’; did you mean ‘savearray’? > PUSHs (CxHASARGS (cx) ? sv_2mortal > (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); > > ^ > /usr/lib/perl5/core_perl/CORE/pp.h:451:28: note: in definition of macro > ‘PUSHs’ > #define PUSHs(s) (*++sp = (s)) > ^ > State.xs:1355:51: note: in expansion of macro ‘sv_2mortal’ > PUSHs (CxHASARGS (cx) ? sv_2mortal > (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); > ^~~~~~~~~~ > /usr/lib/perl5/core_perl/CORE/sv.h:1970:23: note: in expansion of macro > ‘newRV’ > #define newRV_inc(sv) newRV(sv) > ^~~~~ > State.xs:1355:63: note: in expansion of macro ‘newRV_inc’ > PUSHs (CxHASARGS (cx) ? sv_2mortal > (newRV_inc ((SV *)cx->blk_sub.argarray)) : &PL_sv_undef); > ^~~~~~~~~ > State.xs: In function ‘boot_Coro__State’: > State.xs:3469:81: error: assignment of member ‘svt_get’ in read-only object > orig_sigelem_get = PL_vtbl_sigelem.svt_get; > PL_vtbl_sigelem.svt_get = coro_sigelem_get; > > ^ > State.xs:3470:81: error: assignment of member ‘svt_set’ in read-only object > orig_sigelem_set = PL_vtbl_sigelem.svt_set; > PL_vtbl_sigelem.svt_set = coro_sigelem_set; > > ^ > State.xs:3471:81: error: assignment of member ‘svt_clear’ in read-only > object > orig_sigelem_clr = PL_vtbl_sigelem.svt_clear; > PL_vtbl_sigelem.svt_clear = coro_sigelem_clr; > > ^ > make[1]: *** [Makefile:405: State.o] Error 1 > make[1]: Leaving directory > '/tmp/yaourt-tmp-dimytch/aur-perl-coro/src/Coro-6.39/Coro' > make: *** [Makefile:611: subdirs] Error 2

This is a dupe of bug #114708, filed at https://rt.cpan.org/Public/Bug/Display.html?id=114708

Thu Sep 08 05:22:30 2016 gregoa [...] cpan.org - Cc GREGOA added