On Tuesday, July 27, 2004, at 01:20AM, <[EMAIL PROTECTED]> wrote:


>I ran 'perl -d makemaker.pl' and stepped through until I found the code where
>it went awry, in DBD.PM, and edited shamelessly until it succeded...
>Maybe not the best way of doing things, but at least I got wiser ...

Sounds like that's what needed to be done. Ideally the necessary changes would be sent 
to the author and rolled into the next version.

>Then I tried to compile, and found out - at least, it looks so to me - that
>DBD-ORACLE not yet is oracle 9.2 compliant ...

I don't know details about the Oracle interface libraries, but it seems odd to me they 
would break compatibility.

>PERL_ROOT:[LIB.DBD-ORACLE-1_15] mms
>
>CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/NOANSI_ALIA
>S/Define=(UTF8_SUPPORT,"VERSION=""1.15""","XS_VERSION=""1.15""")/Include=(perl_r
>oot:[lib.VMS_AXP.5_6_1.CORE],SAM103:[ORACLE92.rdbms],SAM103:[ORACLE92.rdbms.demo
>],PERL_ROOT:-
>[LIB.SITE_PERL.VMS_AXP.auto.DBI],ora_progint_incl)/Optimize  DBDIMP.c
>
>#include <ociextp.h>
>.^
>%CC-F-NOINCLFILEF, Cannot find file <ociextp.h> specified in #include directive.
>at line number 2159 in file SAM103:[oracle92.rdbms.demo]oci.h;3
>%MMS-F-ABORT, For target DBDIMP.OBJ, CLI returned abort status: %X10B91264.
>
>It is possible for me to compile against a oracle 8.1.7 tree, but the database 
>is 9ir2, and it is a pain to have to switch between oracle homes, to have perl 
>accessing oracle. 

What is "ora_progint_incl"?  If that's expected to be a logical name pointing to a 
directory containing Oracle include files, make sure it's defined.  Other than that, 
you'ld need to track down where exactly ociextp.h lives and take steps to make sure 
that location gets listed in the list passed to the compiler with /INCLUDE=(...).  

Reply via email to