"Alceu R. de Freitas Jr." via cpan-testers-discuss
<[email protected]> writes:
> Hello Slaven,
> It is a possibility that the default perl on OpenBSD is causing the issues.
> I won't say that is heavily patched, but there is obviously
> differences from standard interpreter.
The error message from the problematic reports ("data structure too deep
(hit recursion limit)") seems to originate in JSON::PP. Maybe some
debugging here can be done why it only fails here and not with any other
perl I've seen so far.
> In initial attempts with
> OpenBSD (5.8) I found that that I was unable to compile any perl with
> perlbrew since all of them failed the tests. In this thread here:
> installation of Perl on OpenBSD 5.8 with perlbrew fails due crypt.h
> there are more details about that.
> | |
> | | | | | | | |
> | installation of Perl on OpenBSD 5.8 with perlbrew fails ...Hi
> | there,My name is Alceu and I'm a newbie with OpenBSD. I hope I
> | reached the right mailing list to ask about compiling Perl with
> | perlbrew on OpenBSD. Advertisin... |
> | |
> | Visualizar em www.mail-archiv... | Visualizado por Yahoo |
> | |
> | |
>
Maybe perl5-porters may also say something about it --- at least this is
the original meaning of "porters", making sure that perl5 is running on
all platforms.
>
> Of course I can try to compile the interpreter without perlbrew, but that
> leads to the questions: are we looking for to validate CPAN modules against
> the interpreter shipped with OpenBSD or the standard perl?
>
There's no "or". Both types of reports are valuable.
Regards,
Slaven
>
> De: Slaven Rezic <[email protected]>
> Para: Alceu R. de Freitas Jr. via cpan-testers-discuss
> <[email protected]>
> Cc: Karen Etheridge <[email protected]>; Alceu R. de Freitas Jr.
> <[email protected]>
> Enviadas: Domingo, 4 de Setembro de 2016 12:11
> Assunto: Re: Your smoke testing reports
>
> Hi Alceu,
>
> it looks like you're using OpenBSD's system perl (PERL=/usr/bin/perl
> appears in the reports). A possibility is that this perl is heavily
> patched and now broken for even simple things like reading a META.yml
> file. If this is the case, then it would be good to find out, maybe with
> the help of the OpenBSD guys.
>
> Maybe the reports would be better if you would compile perl yourself?
>
> As for checking reports: I am doing this, at least the non-pass reports,
> and have some scripts to help in this workflow. One of the scripts is
> this one:
> https://github.com/eserte/srezic-misc/blob/master/scripts/ctr_good_or_invalid.pl
> I can give you assistance if you want to go this way (but it's still
> time-consuming!).
>
> Regards,
> Slaven
>
>
--
Slaven Rezic - slaven <at> rezic <dot> de
Berlin Perl Mongers - http://berlin.pm.org
