I should say, that I am running oracle under linux emulation on FreeBSD. I have 5.6.1 Linux Perl running. Like I said before the DBD::Oracle 1.12 compiles fine.
Here are where the header files are, /usr/compat/linux/usr/include/bits/posix1_lim.h /usr/compat/linux/usr/include/bits/posix2_lim.h I am going to upgrade the DBI, currently running 1.38. What would have changed from 1.12 => 1.15 that would cause this? I am diffing the header files and Makefile.PL ....oh wait I found it, 567,568c423 < $OCIINCLUDE .= " -I$OH/rdbms/demo -I$OH/precomp/public"; < my @h_dirs = find_headers(); --- > $OCIINCLUDE .= " -I$OH/rdbms/demo"; Those headers are included by > > /usr/oracle/precomp/public/limits.h:27: posix1_lim.h: No such file or > > directory > > /usr/oracle/precomp/public/limits.h:31: posix2_lim.h: No such file or > > directory > > /usr/oracle/precomp/public/limits.h:35: xopen_lim.h: No such file or > > directory I am going to upgrade the DBI(not this is affecting this) and see if I am missing a compatibility patch, the old RH5 libraries. I will report back, I should just upgrade the Oracle, but that will take longer.. :-) > > I am using old linux libraries, 6.1, but DBD::Oracle 1.12 compiles fine. > > The missing header files are in /usr/include/bits. Any Ideas?? > > DBIXS.h is including CORE/perl.h which then includes /usr/include/sys/param.h > which then fails to find some system header files. > > Can you trace through the lines perl.h:488 param.h:23 to see what's > influencing the inclusion of posix1_lim.h (for example). And then > check if posix1_lim.h exists _anywhere_ on your system. > > Either a #define is wrong or a -Idirectory is missing, for some reason. > > Tim. > > > On Thu, 2004-07-08 at 12:54, Tim Bunce wrote: > > > On Thu, Jul 08, 2004 at 04:31:43PM +0200, Gert-Jan Paulissen wrote: > > > > Hi all, > > > > > > > > I installed DBD::Oracle 1.15 from CPAN using Cygwin perl v5.8.2 and I got > > > > a link error. > > > > > > > > After some investigation it appeared the symbol OCILobWriteAppend was > > > > missing from oci.def and therefore > > > > the command > > > > > > > > $ dlltool --input-def oci.def --output-lib liboci.a > > > > > > > > did not include it, hence the link error. > > > > > > > > I added the symbol after OCILobWrite and everything worked fine. > > > > I am using Oracle 9.2. > > > > > > Thanks. > > > > > > Can anyone confirm that adding OCILobWriteAppend to oci.def does not cause > > > problems with Oracle < 8.1.7? (which don't have OCILobWriteAppend). > > > > > > Tim.
