That's why I indicated that using a directory
relative would make it easier to diagnose/implement.
If both of your custom JSON modules declare
package JSON;
You
should, as
toolic initially asserted, be able to use
use lib '/abc/xyz';
or
use lib ('/abc/xyz');
then
use JSON;
use Test::JSON
because as I noted earlier; the double-colon is a path/directory separator. Meaning;
Test::JSON ==
Test/JSON.
You might also try
use lib '/abc/xyz/';
as that negates the need to preface a slash before your custom modules.
In any case; you must ensure that the path to your custom JSON modules preceeds (is before) your system Perl module path.
That's why you see reference to conflicts within the system's perl, in the latest error you quoted.
--Chris
¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH
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.