The combination of gcc option -m32 is likely to conflict with -Duse64bitall or its implications

Yeah - I wasn't sure if -Duse64bitall would inevitably fail to provide the 64bit pointers on an -m32 build, and I also wondered whether Osprey actually wanted the -m32 arg.
In the end, rather than providing any detailed explanation, I just left it as a suggestion that might be tried - something that can be discussed further if Osprey is so inclined.

IIRC, if -Duse64bitint delivers 64bit integers then -Duse64bitall will do the same, even if it fails to deliver 64bit pointers.

Cheers,
Rob

In reply to Re^3: Building perl from source by syphilis
in thread Building perl from source by Osprey

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.