On Tue 18 Mar 2003 12:00, Tim Bunce <[EMAIL PROTECTED]> wrote:
> Is that against DBD::Oracle 1.13? I got 5 out of 6 hunk failures from the patch.

Yes. I guess

l1:/pro/3gl/CPAN/DBD-Oracle-1.13 106 > ll README.hp*
   7744 -rw-rw-rw-    1 merijn   softwr      47207 Mar 18 13:02 README.hpux
  13006 -r--r--r--    1 merijn   softwr      45890 Aug  3  2002 README.hpux.org
l1:/pro/3gl/CPAN/DBD-Oracle-1.13 107 > diff -u README.hpux{.org,} > /tmp/xx.diff
Exit 1
l1:/pro/3gl/CPAN/DBD-Oracle-1.13 108 >

Now attached and inlined

> Tim.
> 
> p.s. Feel free to add the links to https://www.beepz.com/personal/merijn/
> and http://www.cmve.net/~merijn/ into the patch.

Good spot?

--- README.hpux.org     2002-08-03 22:03:47.000000000 +0200
+++ README.hpux 2003-03-18 13:02:35.000000000 +0100
@@ -1,10 +1,10 @@
 =head1 INTRODUCTION
 
 Building a working dynamically linked version of the Oracle DBD driver
-on HP-UX (11.00) has been a challenge for many.  For months after taking a
-new job, where HP-UX was the standard database server environment, I had only been
-able to build a statically linked version of perl and the DBD-Oracle 
-module on HP-UX 11.00.
+on HP-UX (11.00) has been a challenge for many.  For months after taking
+a new job, where HP-UX was the standard database server environment, I
+had only been able to build a statically linked version of perl and the
+DBD-Oracle module on HP-UX 11.00.
 
 Then Roger Foskett posted instructions for what turned out to be dynamic
 build.  Rogers's post got me farther than I had previously gotten.  In fact, 
@@ -39,17 +39,25 @@
  
 HP's default perl is no good (and antique).  
 
-By default, HP-UX 11.00 delivers perl 5.00503.  Others tell me that
-the default is a threaded GNUpro build of 5.6.1.  This is not what I
-found our systems, and it probably depends on which packages you
-install.  In any case, this version of perl delivered by HP will
-in all likelihood not work.
-
-If you are reading this, you 
-have probably discovered that something did not work.  To get good
-version of the DBD-Oracle driver, we have to start with a perl that as
-been built with the correct compiler flags and shared libraries.  This
-means that you must build your own version of perl from
+By default, HP-UX 11.00 delivers perl 5.00503 until September 2001.
+Others tell me that the default is a threaded GNUpro build of 5.6.1.
+This is not what I found our systems, and it probably depends on which
+packages you install.  In any case, this version of perl delivered by
+HP will in all likelihood not work. Before you check, be sure to prevent
+perl4 from /usr/contrib/bin to be the first perl version found in your $PATH.
+
+As of application release September 2001, HP-UX 11.00 is shipped with
+perl-5.6.1 in /opt/perl. The first occurrence is on CD 5012-7954. The
+build is a portable hppa-1.1 multithread build that supports large files
+compiled with gcc-2.9-hppa-991112. When you have a modern system with a
+hppa-2.0 architecture (PA8xxx processor) and/or the HP C-ANSI-C compiler
+consider building your own perl, which will for sure outperform this
+version.
+
+If you are reading this, you have probably discovered that something did
+not work.  To get good version of the DBD-Oracle driver, we have to start
+with a perl that as been built with the correct compiler flags and shared
+libraries.  This means that you must build your own version of perl from
 sources.
 
 See L<Appendix A> for a copy of a makefile used by me to biuld
@@ -94,6 +102,10 @@
 cleanly using the HP softbench compiler, and Oracle 8.0.5 (32bit), and
 Oracle 8.1.6, 8.1.7 (64 bit).  Oracle 8.1.5 will probably work as well.
 
+Oracle 8.1.7.4 (32bit) with DBI-1.35 and DBD-Oracle-1.13 has been proven
+to work on HP-UX 11.00 (64bit) with perl5.6.1, perl5.8.0, and perl5.9.0,
+using the guidelines in this document for both HP-C-ANSI-C and gcc-3.2.
+
 =head2 gcc Compiler
 
 For along time many folks have asked, how they could build a DBD-Oracle
@@ -156,8 +168,8 @@
     For example:
     What libraries to use? [-lnsl -lnm -lndbm -lmalloc -ldld -lm -lc -lndir -lcrypt 
-lsec] -lcl -lpthread -lnsl -lnm -lndbm -lmalloc -ldld -lm -lc -lndir -lcrypt -lsec
 
-H.Merijn Brand notes that the above can be accomplished by adding the following to 
-the ./Configure command line: 
+H.Merijn Brand notes that the above can be accomplished by adding the
+following to the ./Configure command line: 
 
    -A prepend:libswanted='cl pthread ' 
 
@@ -221,7 +233,7 @@
 =head1 Build and Install DBI
 
     
-    cd DBI-1.18/
+    cd DBI-1.35/
     perl Makefile.PL
     make
     make test
@@ -928,9 +940,19 @@
 
 =head1 Appendix D (Miscellaneous links which might be usefull)
 
+=head2 https://www.beepz.com/personal/merijn/ or http://www.cmve.net/~merijn/
+
+H.Merijn Brand has placed reasonable recent perl binary distributions
+here that already include the DBI that was current when the build was
+created. These builds are created using the most recent version of gcc
+available at that time. The gcc used to create the build, including the
+matching binutils and gdb are available from the same page. These perl
+binaries are I<Oracle prepared>, meaning that the libraries that Oracle
+requires are linked in.
+
 Thanks to Tony Foiani for these references:
 
-=head2  http://marc.theaimsgroup.com/?l=perl-dbi&m=96040350416305&w=2 
+=head2 http://marc.theaimsgroup.com/?l=perl-dbi&m=96040350416305&w=2 
 
 This link discusses older version of the DBI/DBD interface, so most of
 the code examples are probably no longer relevant.  This was written 
@@ -1088,7 +1110,7 @@
 
 
 Roger also provides a link to some threads containing some of his
-DBD-Oracle and HP-UX11 trials... 
+DBD-Oracle and HP-UX 11 trials... 
 L<http://www.geocrawler.com/search/?config=183&words=Roger+Foskett>
 
 

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.0 & 632 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
     WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.024 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/

Attachment: xx.diff
Description: Binary data

Reply via email to