Ok, so where is that, or where should that be applied? I'm not understanding... are you saying that in one of the two test runs that API.so is being read out of blib and the other isn't?

There's no API.so or API.pm in the blib dir I'm building:

spek@sequoia ~/repos/rpi-dac-mcp4922 $ find . -name API.so spek@sequoia ~/repos/rpi-dac-mcp4922 $ spek@sequoia ~/repos/rpi-dac-mcp4922 $ find . -name API.pm spek@sequoia ~/repos/rpi-dac-mcp4922 $

...and:

spek@sequoia ~/repos/rpi-dac-mcp4922 $ ll | grep blib drwxr-xr-x 8 spek spek 4096 Feb 21 18:11 blib/ -rw-r--r-- 1 spek spek 0 Feb 21 18:44 pm_to_blib

So can you please elaborate?

Thanks,

-stevieb


In reply to Re^2: "make test" catches a C undefined symbol, but "prove" doesn't by stevieb
in thread "make test" catches a C undefined symbol, but "prove" doesn't by stevieb

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.