Front page | perl.perl5.porters |
Postings from May 2008
Re: 5.8.9-to-be on Irix
From: Sébastien Aperghis-Tramoni
May 14, 2008 17:09
Re: 5.8.9-to-be on Irix
Message ID: 05803593-A1BA-4BEE-9B1C-1F3694681DAF@free.fr
David Cantrell wrote:
> On Fri, May 09, 2008 at 02:26:44PM +0200, Sébastien Aperghis-
> Tramoni wrote:
>> Given 5.8.8 has Sys::Syslog 0.13, and 5.8.9-tobe and blead both have
>> 0.24, could you try the following combinations:
> OK, in both cases I built a fresh perl (5.8.9-to-be is Nicholas's
> 33536), ignored the test failures in 5.8.9-to-be, and intalled to
> ~/perl-5.8.[whatever]. Then I did the untarred Sys-Syslog 0.13 and
> and for each perl and each dist of the module did:
> [path]/perl Makefile.PL
> make test
> 0.24 came from the CPAN, 0.13 from the backpan.
Yes, sorry, I'm used to delete old versions in order to improve the
>> - 5.8.8 with 0.24 (will show if the regression was introduced by
> That fails, but passes with 0.13. But according to CPAN-testers, 0.24
> *passes* with 5.8.8 on some other platforms, so this is Irix-specific.
>> - 5.8.9-tobe with 0.13 (will show if the regression was introduced
>> by something else in Perl)
> That passes.
> With 0.24 I noticed this:
> cc-1174 cc: WARNING File = Syslog.c, Line = 367
> The variable "RETVAL" was declared but never referenced.
> which might explain the failures.
Strange, this file hasn't changed much between 0.18 and 0.19, mostly
by a couple of #ifdef
Does this warning appears in XS_Sys__Syslog_setlogmask_xs()? If not,
could you paste me the part of the C file where it occurs?
> So given that 0.24 fails with 5.8.8 it looks like the problem is in
> Sys::Syslog, and not with perl itself. Tomorrow I'll grovel over the
> backpan and see exactly when the bug was introduced.
> 0.13 through to 0.18 pass all their tests with 5.8.8 and with
> 5.8.9-to-be on Irix. 0.19 onwards all fail on both versions.
Ok, so this means the problem has appeared between 0.18 and 0.19.
Unfortunately, 0.19 was a quite big release because it added Win32
support and numerous bugfixes. Also, this was the time I begun using
a SVN for Sys::Syslog and I made the mistake of importing a WIP
version instead of starting with a clean 0.18 release.
[ two hours of diff'ing and getting lost/distracted by googling later ]
Holy cow. I bet it's related to this change:
which I just realised was fixed very recently:
So, could you try the version from the SVN and check whether this
fixes the problem?
$ svn co svn://svn.mongueurs.net/Sys-Syslog
Thanks for your hard work. I owe you your favourite drinking for the
next Perl conference :-)
Close the world, txEn eht nepO.