I have done this install on quite a few machines. Honestly, i have never had a machine pass all of the tests, and often have it fail all tests and still work correctly once installed. I would
make install the code into a private dir, and whip up a quick login/select script to test it. My most common cause for errors in tests is something in the
%ENV, usually LD_LIBRARY_PATH (Solaris) or SYBASE. Incase you run into DBD::Sybase scripts which will not run from cron, or appear to die at the connect call, i usually end up adding something like the following (on Solaris) :
BEGIN {
$ENV{LD_LIBRARY_PATH} = "$ENV{SYBASE}/lib:$ENV{LD_LIBRARY_PATH}";
}
which is also a fix for the test fails i believe.
OH, a sarcasm detector, that’s
really useful
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.