Figured this one out:

The Makefile.PL for DBD::Oracle looks for makefiles in your oracle
home directory.
If it finds one, it scans the makefile for compiler options used to
build Oracle applications.

In my case it found demo.mk which includes the option -locci.

What is interesting is that the makefiles are not present in the
instant client zip archives that Oracle makes available. So it appears
that libocci will get included or not depending on what kind of client
distribution you have.

Is anyone having problems using DBD::Oracle in a mod_perl environment
when libocci is _not_ linked in? I'm using perl 5.12.2 without
threading enabled.

On Tue, Nov 23, 2010 at 10:28 AM, John Scoles <sco...@pythian.com> wrote:
>  On 22/11/2010 2:58 PM, E R wrote:
>>
>> Hi,
>>
>> I have two DBD/Oracle/Oracle.so shared libraries. In one case ldd
>> reports that libocci is linked in, and in another case libocci doesn't
>> show up.
>>
>> I don't know how the first version was built, but the second one was
>> build using:
>>
>> export ORACLE_HOME=... # path the instantclient 10.2.0.4
>> export LB_LIBRARY_PATH="$ORACLE_HOME:"
>>
>> perl Makefile.PL
>> make
>> make install
>>
>> (I.e., a pretty generic build)
>>
>> Does anyone know how libocci gets picked up when building Oracle.so? I
>> am using instantclient version 10.2.0.4
>>
>> Thanks,
>> ER
>
> I know in the instant client the  so files are all squished together into a
>
> libclntsh.so.xx.x
>
> file where xx.x is the version number of the client.  ie libclntsh.so.10.1
> for ic 10.1
>
> What I have to do to get DBD::Oracle to compile is create a symbolic link to
> it like this
>
> ln -s libclntsh.so.10.1  libclntsh.so
>
> if you happen to already have a link like that in your path someplace it
> could be a problem.
>
> I have noticed on some other OS system that all the .so files are place in a
> common folder one I cannot find or do not have access to in the Makeifle.PL
>
> you might want to look into that.
>
> After the compile it no longer needs the link.
>
> Hope this helps
>
> Cheers
> John Scoles
>
>
>
>

Reply via email to