In other words, the "No Makefile" problem was a 'short between the ears'. Thanks for the explanation.

There's only one make on the system (GNU v.4.2.1). It's from an RPM built by Bull as part of their freeware offerings and was probably built using IBM's XLC. Could that matter? I know some perl modules must be built with gcc and require a perl and some dependencies also be built with gcc (IO::Socket::SSL), which is why I need to build perl myself. I didn't think it would matter with make, though.

make links to make_32. make_64 exists but won't load because libgmp and libgcc can't be loaded - I haven't explored why yet. Is it possible I need to be using a 64 bit version of make? Not necessarily as a solution to the bad "w" flag - that doesn't seem relevant - just as a rule when building 64 bit applications?


In reply to Re^4: perl-5.24.3 build woes by 2pipes
in thread perl-5.24.3 build woes by 2pipes

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.