What I get is this error:$dbh = DBI->connect( "dbi:Proxy:hostname=$host;port=$port;dsn=dbi:Oracle:$oradb", $user, $pass);
The installation of RPC::PlClient fails during the "make test" for Net::Daemon. Here is the output:install_driver(Proxy) failed: Can't locate RPC/PlClient.pm in @INC
Checking if your kit is complete... Looks good Writing Makefile for Net::Daemon cp lib/Net/Daemon/Test.pm blib/lib/Net/Daemon/Test.pm cp lib/Net/Daemon/Log.pm blib/lib/Net/Daemon/Log.pm cp lib/Net/Daemon.pm blib/lib/Net/Daemon.pm Manifying blib/man3/Net::Daemon::Test.3pm Manifying blib/man3/Net::Daemon.3pm Manifying blib/man3/Net::Daemon::Log.3pm /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_h +arness(0, 'blib/lib', 'blib/arch')" t/*.t t/base..........ok + t/config........ok + t/fork..........ok + t/forkm.........dubious + Test returned status 15 (wstat 3840, 0xf00) DIED. FAILED tests 1-10 Failed 10/10 tests, 0.00% okay t/ithread.......ok + t/ithreadm......ok + t/loop-child....ok + t/loop..........ok + t/single........ok + t/thread........ok + t/threadm.......ok + t/unix..........ok + Failed Test Stat Wstat Total Fail Failed List of Failed ---------------------------------------------------------------------- +--------- t/forkm.t 15 3840 10 10 100.00% 1-10 Failed 1/12 test scripts, 91.67% okay. 10/73 subtests failed, 86.30% o +kay. make: *** [test_dynamic] Error 29 /usr/bin/make test -- NOT OK Running make install make test had returned bad status, won't install without force
Apparently my problem is that all the forkm tests fail. Ultimately I just need to access the Oracle server. Is there a completely different solution that I haven't thought of? Is there a workaround to make forkm work for the Net::Daemon installation, or to install DBD::Proxy without Net::Daemon? Should I force install either of these?
Or am I doomed to always create data dumps from Oracle, FTP them across, and parse them on the other side?
The only plausible theory that I have heard yet is that the failure of forkm has something to do with the fact that the machine has a dual processor. That didn't really help me, but perhaps it will help you. If you have the solution to my dilemma.
In reply to problem installing DBD::Proxy by guido1977ahs
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |