I couldn't get Net::SMTP::SSL to install with OS X 10.4 default perl build. I decided to install a new perl from source (using /usr/local/bin to avoid messing up the default version). I followed the REAME.macosx install instructions and the build seems fine until I start trying to install certain modules, e.g. DBD::mysql, Mac::Carbon, etc...

In each make or make test failure I get the following error: lipo: can't open input file: ...

I'm not sure if this is a library conflict, or because of the universal binary build, or something completely different.

I need to either be able to build Net::SMTP::SSL (errors saying it needs perl 5.8.8 to run) with the original perl build, or build a new version that doesn't keep giving me the "lipo" error. The lipo error always points to a file in /var/tmp// if that helps...

In reply to getting the error lipo: can't open input file: while compiling modules by boysie

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.