G'day docdurdee,

The "DYLD_LIBRARY_PATH" (from $ENV{DYLD_LIBRARY_PATH}) looks wrong. Should that be "LD_LIBRARY_PATH" (i.e. no leading "DY")?

See also: "DBD::Oracle - Oracle Environment Variables".

The DYLD_LIBRARY_PATH is OS X related. I tried setting LD_LIBRARY_PATH, but that doesn't work.

Fair enough. I'm also using Mac OS X (10.10.3) but, as I don't have local access to Oracle, I'm unable to run any tests for you. Here's a few more thoughts and suggestions.

Using backticks (as shown in your update) will not be helpful. The command within the backticks will be executed in a new process environment which will be discarded (and the old process environment restored) when completed. E.g.

$ XXX=unset perl -E 'say "$$: XXX=$ENV{XXX}"; print `export XXX=xxx; e
+cho \$\$: XXX=\$XXX`; say "$$: XXX=$ENV{XXX}"'
3494: XXX=unset
3495: XXX=xxx
3494: XXX=unset
[download]

Also from your update, if setting $ENV{whatever} in a BEGIN block has no apparent effect, then that BEGIN block is possibly being reached too late. Try putting that BEGIN block earlier in the code. Remember, BEGIN blocks are executed in FIFO order, and use statements are

... exactly equivalent to

BEGIN { require Module; Module->import( LIST ); }
[download]

Consider writing env.t (or similar) with lines like:

ok $ENV{whatever} eq $whatever_expected_value, ...
[download]

Try setting environment values on the command line (like I did with XXX=unset above) prior to running your tests. I'm not suggesting this as a solution, but it may provide some useful feedback. You can set multiple values, e.g.

DYLD_LIBRARY_PATH=... ORACLE_HOME=... make test
[download]

Check if Dist::Zilla is performing actions based on what it considers to be tainted data (see perlsec). This could affect your environment.

I'll also front-page this thread to try to get you a bit more coverage.

— Ken

Actually, either the LD_LIBRARY_PATH or DYLD_LIBRARY_PATH will work as long as they are actually set in the environment. Thanks! Following Corion's suggestion, I was able to get it to work with the restart parameter. See my response to Corion's comment for details.

Do you have the tnsname.ora file from the working systems replicated to the test systems or at least the section that enables Oracle to resolve the DB to which you connect? It should normally be in $ORACLE_HOME/network/admin/tnsnames.ora

Cheers,
R.

At least with some environment variables and some operating systems, the variables are only used by the OS at process start time. This means that setting the environment variables after the start of your process does not help the current instance of your process. One approach to circumvent is to set up the environment within the first instance of your process and then to relaunch the process via exec. See for some examples:

• LD_LIBRARY_PATH setting
• Perl and paths...again :-(

Thanks Corion!! I was able to get it to work following your previous posts on the topic. Adding this to head of the test:

BEGIN {
    if( ! $ENV{PDUPRE_RESTART}) {
      $ENV{LD_LIBRARY_PATH} = '...some Oracle path../lib';
      #$ENV{DYLD_LIBRARY_PATH} = '...some Oracle path../lib';  #Either
+ LD OR DYLD works
      $ENV{PDUPRE_RESTART} = 1;
      exec $0, '--restarted', @ARGV
    };
};
[download]

worked after I made the test an executable and set the shebang line to point to my local install of perl:

!#/Users/.ME./perl
[download]

I had it set to:

!#/usr/bin/env perl
[download]

but it didn't show up because I am in the habit of running my perl scripts/tests using `perl t/some.t`; if I run using `/usr/bin/env perl t/some.t` than I again get the error from the OP.