On Fri, 2004-12-17 at 21:44 +0000, Simon Windsor wrote: > Hi > > I have already the file, README.hpux, and it does not appear address this > problem.
Ah but it does. > > I have come to realise that the supplied Perl doesn't support threads and, as > you have suggested, needs rebuilding. Exactly, what the README says! > The annoying aspect this I have two > servers running Oracle 9.2.0.5, running latest versions of HP-UX 11i. The > Itanium one works fine, teh PA-RISC not. It seems that different configure > options are used to make Perl for the two releases. Its a totally different binary architecture, and a totally different OS! > Finally, I'll try an old release of gcc, the one used to make Perl (by HP) > and > see if that addresses issue, if not I'll have to make perl. Simon, I would never use a vendor supplied build of perl. It ties you to the vendor's compiler, the vendor's build options, the vendor's file system layout, it is often antique... at least 2 or more years out of date, and it makes it much more difficult to do OS upgrades, because things _will_ break... and you will wonder why... ESPECIALLY in HPUX-land! Why would you want to overlay site built software into the vendors delivered file system. Thats just asking for trouble. I've seen it over and over. I believe you will find that even when you use the old release of gcc, that the perl you are trying to use, is not linked with the right libraries to be able to dynamically load Oracle.sl, which is linked with Oracle shared libraries, which ARE linked with these libraries. I know you said you read the README, but I think you missed the point. Save your self the trouble: download perl, and build it. It really takes less time than it took to right this email. (You can even hack up for your environment the makefile I provided in the README). If you want it to work on HP, you are going to do this sooner or later. Oh, and FWIW (I might as well rant about this for a moment): HP's support for perl is really awful. I was able to get Openview::Message (http://search.cpan.org/~lbaxter/Openview-Message/) to build and link with the Openview API libraries on Sun, but _not_ on their own platform (HPUX). So on that platform it falls back to using the CLI command opcmsg. HP would not even provide support to my employer (a large US Bank) who had MANY licenses of Openview under support agreements. They just said "We don't support perl". The bank is now pretty committed to IBM's tools... (though not for this reason I am sure). Lincoln
