Hi Alexander,
That may be true if I was running an Itanium 11.23 system with "so" 
instead of normal "sl" files.     Yes HP furnishes files compilied with 
the gcc and the other binaries also done that way.   Their was an issue 
some time ago with people using an aCC (c++) perl but that is not true in 
my case.
You can check your perl with the perl -V option to see which compilier was 
used. Mine is (without giving you the whole output).

This source file for DBD::Oracle came straight from cpan and once we 
correct the typo in the makefile.pl,  it ran all the way to this point 
with the "make test". And yes there are binaries for HP-UX but they are 
old and not at this version with 10g. 

   use64bitint=define use64bitall=define uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='gcc', ccflags =' -D_POSIX_C_SOURCE=199506L -D_REENTRANT 
-D_HPUX_SOURCE -
fPIC -DUSE_SITECUSTOMIZE -DNO_HASH_SEED -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=
64  -fno-strict-aliasing -pipe',
    optimize='',
    cppflags='-Aa -D__STDC_EXT__ -D_HPUX_SOURCE -D_POSIX_C_SOURCE=199506L 
-D_REE
NTRANT -D_HPUX_SOURCE

Also, that item on google was solve sometime ago.   Note it was back in 
2002.   It's a shame most people ask for help and then they don't provide 
feedback to the person whether it worked or not.   Usually if the answer 
works you never hear back from them.

Thank You for taking the time to answer
Rich



--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




Alexander V Alekseev <[EMAIL PROTECTED]> 
09/07/2007 09:29 AM

To

cc
[email protected]
Subject
Re: DBD need to finish..






                                 Hello!

On Fri, 7 Sep 2007, Richard T Malafa wrote:

> As I understand it you are the head person for this area of DBI and
> DBD::Oracle.   We had a lot of help from both Merijn and Handly in 
finding
> typo  error in the original perl Makefile.pl  and that works great now.
>
> We desperately need to get by the "make test" part and any suggestion 
from
> you or the other experts is most welcome.   Is the following error due 
to
> the Oracle Installation or the test.pl script would be a good suggestion
> part if you could.  This is used on a N4000  with HP UX 11i Version 1 
with
> 1.  Oracle 10g
> 2.  Perl 5.8.8 with DBI 1.50 from HP (64 bit)
> 3.  gcc 4.2 from HP.
> 4.  DBD::Oracle 1.19 from cspan
>
> If you need the total output with environment  from the start using 
"perl
> makefile.PL -l" , just ask.   Hopefully you have a moment to glance at
> this and give me an "Aha. it's"
>
> Thank You
> Rich

                 Google says, this may be bad-built gcc effect. See:

http://gcc.gnu.org/ml/gcc/2002-06/msg00112.html

                 I never worked with HPUX, but for Sun Solaris there are
Sun-built GNU binaries, and www.sunfreeware.org - built. So one has
a choice, and Sunfreeware binaries are usually built in other way.

                 May be, there is such a resource for HPUX? Or you may
try to compile perl yourself.

                 But it seems to me, that there is some bug between
compiler-linker. May be the linker, used by HT doesn't understand weak
symbols. With Sun-built binaries I see such incompatibilities sometimes.

                                 Bye. Alex.

>
>
> Current error is:
> Script started on Thu Sep  6 07:51:50 2007
> [EMAIL PROTECTED]> make test
>        PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> /usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_Jv_RegisterClasses' 
in
> load module
> '/opt/perl_64/lib/5.8.8/PA-RISC2.0-thread-multi-LP64/auto/Cwd/Cwd.sl'.
> t/01base................/usr/lib/pa20_64/dld.sl: Unsatisfied code symbol
> '_Jv_RegisterClasses' in load module
> '/opt/perl_64/lib/5.8.8/PA-RISC2.0-thread-multi-LP64/auto/
> Cwd/Cwd.sl'.
> /usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_Jv_RegisterClasses' 
in
> load module
> 
'/opt/perl_64/lib/5.8.8/PA-RISC2.0-thread-multi-LP64/auto/List/Util/Util.sl'.
>
> /usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_Jv_RegisterClasses' 
in
> load module
> 
'/opt/perl_64/lib/5.8.8/PA-RISC2.0-thread-multi-LP64/auto/List/Util/Util.sl'.
>
> /usr/lib/pa20_64/dld.sl: Unsatisfied code symbol '_Jv_RegisterClasses' 
in
> load module
> '/tmp/work/DBD-Oracle-1.19/blib/arch/auto/DBD/Oracle/Oracle.sl'.
> Failed to load Oracle extension and/or shared libraries:
> install_driver(Oracle) failed: Can't load
> '/tmp/work/DBD-Oracle-1.19/blib/arch/auto/DBD/Oracle/Oracle.sl' for 
module
> DBD::Oracle: Unresolved external at /opt/perl_64/li
> b/5.8.8/PA-RISC2.0-thread-multi-LP64/DynaLoader.pm line 230.
> at (eval 7) line 3
> Compilation failed in require at (eval 7) line 3.
> Perhaps a required shared library or dll isn't installed where expected
> at t/01base.t line 19
> The remaining tests will probably also fail with the same error
>
>
> 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written agreement or government initiative expressly permitting the use 
of
> e-mail for such purpose.
> 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>

Reply via email to