Focusing on this aspect of your question:
... bail out if there is not support for 64 bit but then I'll get spammed by CPAN testers running tests on 32-bit Perls. Is there any way to avoid this?

cpantesters will treat a report that dies/exits with "OS unsupported" in the message as an NA result (which will not show up as a FAIL, and I don't think gets spammed to you; I've never gotten a mail for NA, that I remember, anyway). More about NA can be found in the CPAN Tester Wiki "Reports" section; it doesn't specifically mention the required die-message, but my tests show that any message starting with "OS unsupported" -- and it might be "containing" rather than "starting with" -- will trigger the NA.

With ExtUtils::MakeMaker, running os_unsupported() from the Makefile.PL will cause the process to die with the message "OS unsupported". So if you check bitness in Makefile.PL, then run os_unsupported() if not $bit64; or similar message, it will return a cpantesters status of NA. Other build environments may have a similarly-encapsulated function, or you can just die "OS unsupported because of 32bit integers";

Instead of exiting Makefile.PL prematurely, you could replicate what I use in Win32::Mechanize::NotepadPlusPlus 00-load.t, where in the test file, I BAIL_OUT with a $reason message that contains "OS unsupported" (like BAIL_OUT('OS unsupported because of 32bit integers'); for your case). I successfully use that mechanism, as seen in reports like this one to get a result of NA in the matrix. So you could test your bitness in the first .t file run, and BAIL_OUT with an appropriate message if it's not 64bit.

In reply to Re: Best way to check for 64-bit support by pryrt
in thread Best way to check for 64-bit support by gflohr

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.