Front page | perl.perl5.porters |
Postings from May 2021
From: H.Merijn Brand
May 19, 2021 10:40
Message ID: 20210519124008.3580fb8f@pc09
On Wed, 19 May 2021 10:15:50 +0000, Nicholas Clark <email@example.com>
> On Tue, May 18, 2021 at 03:58:14PM +0100, David Cantrell wrote:
> > On Tue, May 18, 2021 at 02:23:31PM +0100, Paul LeoNerd Evans wrote:
> > > Nicholas Clark <firstname.lastname@example.org> wrote:
> > > In case it is of interest, I've been using all three of these in
> > > XS modules on CPAN for a while now, and haven't yet encountered
> > > any platforms which complain. No doubt there are some around, but
> > > those don't seem to be ones that report smoketest results.
> > If you're relying on CPAN testers for that you mostly won't get
> > reports when your code fails to build. Most testers only report
> > when the tests fail, and if your code won't even build the tests
> > won't get run. The reason for that is that we can't really tell
> > automatically if the build failure is because of your broken code
> > or our missing libraries that it tried to link against.
> Also, I think that *most* CPAN testers are using gcc or clang, few are
> on (old) MSVC, and approximately zero are on AIX, HP-UX or VMS, whose
> vendor compilers are the most likely candidates for "being exacting".
I have an HP-UX *and* an AIX machine available for anyone willing to
work on CPAN testing on those.
Note that the resources are very limited, and that running it in cron
is not really an option, unless we stop smoking core.
Both have GNU gcc as well as the OS native compiler.
> So it's not a wonderful sample for compiler portability testing.
> Nicholas Clark
H.Merijn Brand https://tux.nl Perl Monger http://amsterdam.pm.org/
using perl5.00307 .. 5.33 porting perl5 on HP-UX, AIX, and Linux
https://tux.nl/email.html http://qa.perl.org https://www.test-smoke.org