Viewing of perl -V

[schniela]

Good afternoon,
I am a novice with Perl, and have been asked to assist in loading some OpenLink software. The system is an Itanium w/11.23. We started with Perl 5.8.8.A, DBI-1.57 and DBD-ODBC-1.14. The Perl install and modules "test & make" worked fine. (after a few links & permission changes) and the DBA's are able to make a connection (sql on Windows).

We were able to run simple perl commands but specific function calls within their script are core dumping.

OpenLinks is suggesting we try a different versions of Perl,DBI and DBD-ODBC. Which brings us to my question of where does the initial response of >perl -V come from? We are seeing the following, listing the OSVERS=11.22, which is why OpenLink is asking for a new Perl install?
Any help is greatly appreciated, any addtl info will be provided. Thx

[root@stldb33d]:/SD_CDROM # perl -V
Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
Platform:
osname=hpux, osvers=11.22, archname=IA64.ARCHREV_0-thread-multi-LP64
uname='hp-ux bigsur03 b.11.22 u ia64 1800516905 unlimited-user license '
config_args='-ders -Dcc=cc -Dusethreads -Duseithreads -Ud_sigsetjmp -Uinstallusrbinperl -Ulocincpth= -Uloclibpth= -Duse64bitall -Dd_attribut=undef -Dd_attribute_warn_unused_result=undef -Dd_u32align=define -Aprepend:libswanted=cl -Dvendorprefix=/opt/perl_64 -Doptimize=-fast +DSitanium2 +Ofltacc=strict -Accflags=+Z -Accflags=-DUSE_SITECUSTOMIZE -Duselargefiles -Accflags=-DNO_HASH_SEED -Dinc_version_list=5.8.7/$archname 5.8.7 5.8.6/$archname 5.8.6 5.8.4/$archname 5.8.4 5.8.3/$archname 5.8.3 5.8.2/$archname 5.8.2 5.8.1/$archname 5.8.1 5.8.0/$archname 5.8.0 -Duseshrplib -Dconfig_heavy=Config_dynamic.pl -Dprefix=/opt/perl_64 -Dcf_by=ActiveState -Dcf_email=support@ActiveState.com'
hint=recommended, useposix=true, d_sigaction=define
usethreads=define use5005threads=undef useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=define use64bitall=define uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler:
cc='cc', ccflags =' -D_POSIX_C_SOURCE=199506L -D_REENTRANT -Ae -D_HPUX_SOURCE -Wl,+vnocompatwarnings +DD64 +Z -DUSE_SITECUSTOMIZE -DNO_HASH_SEED -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 ',
optimize='-fast +DSitanium2 +Ofltacc=strict',
cppflags='-D__STDC_EXT__ -D_HPUX_SOURCE -D_POSIX_C_SOURCE=199506L -D_REENTRANT -D_HPUX_SOURCE -Wl,+vnocompatwarnings -DUSE_SITECUSTOMIZE -DNO_HASH_SEED'
ccversion='B3910B A.05.55', gccversion='', gccosandvers=''
intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=87654321
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries:
ld='/usr/bin/ld', ldflags =' -L/usr/lib/hpux64'
libpth=/usr/lib/hpux64 /lib /usr/lib /usr/ccs/lib /usr/local/lib
libs=-lcl -lnsl -lnm -ldl -ldld -lm -lsec -lpthread -lc
perllibs=-lcl -lnsl -lnm -ldl -ldld -lm -lsec -lpthread -lc
libc=/usr/lib/hpux64/libc.so, so=so, useshrplib=true, libperl=libperl.so
gnulibc_version=''
Dynamic Linking:
dlsrc=dl_hpux.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-B,deferred '
cccdlflags='+Z', lddlflags='-b +vnocompatwarnings -L/usr/lib/hpux64'


Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY PERL_IMPLICIT_CONTEXT
PERL_MALLOC_WRAP USE_64_BIT_ALL USE_64_BIT_INT
USE_ITHREADS USE_LARGE_FILES USE_PERLIO
USE_REENTRANT_API USE_SITECUSTOMIZE
Locally applied patches:
ActivePerl Build 817 [257965]
Iin_load_module moved for compatibility with build 806
Avoid signal flag SA_RESTART for older versions of HP-UX
PerlEx support in CGI::Carp
Less verbose ExtUtils::Install and Pod::Find
Patch for CAN-2005-0448 from Debian with modifications
Partly reverted 24733 to preserve binary compatibilty
27528 win32_pclose() error exit doesn't unlock mutex
27527 win32_async_check() can loop indefinitely
27515 ignore directories when searching @INC
27359 Fix -d:Foo=bar syntax
27210 Fix quote typo in c2ph
27203 Allow compiling swigged C++ code
27200 Make stat() on Windows handle trailing slashes correctly
27194 Get perl_fini() running on HP-UX again
27133 Initialise lastparen in the regexp structure
27034 Avoid "Prototype mismatch" warnings with autouse
26970 Make Passive mode the default for Net::FTP
26921 Avoid getprotobyname/number calls in IO::Socket::INET
26897,26903 Make common IPPROTO_* constants always available
26670 Make '-s' on the shebang line parse -foo=bar switches
26379 Fix alarm() for Windows 2003
26087 Storable 0.1 compatibility
25861 IO::File performace issue
25084 long groups entry could cause memory exhaustion
24699 ICMP_UNREACHABLE handling in Net::Ping
Built under hpux
Compiled at Mar 20 2006 20:52:50
@INC:
/opt/perl_64/lib/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
/opt/perl_64/lib/5.8.8
/opt/perl_64/lib/site_perl/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
/opt/perl_64/lib/site_perl/5.8.8
/opt/perl_64/lib/site_perl
/opt/perl_64/lib/vendor_perl/5.8.8/IA64.ARCHREV_0-thread-multi-LP64
/opt/perl_64/lib/vendor_perl/5.8.8
/opt/perl_64/lib/vendor_perl

[James R. Ferguson]

Hi:

> where does the initial response of >perl -V come from?

Simplistically, the output of '-V' represents the major Perl configuration variable values as set during the compilation of the Perl binary. The *current* contents of the @INC array are also shown in the response.

Regards!

...JRF...

[schniela]

Would I be correct in assuming that reinstalling Perl be of no benefit then? Since I received the same output from from Perl 5.8.3 and 5.8.8.

[Steven E. Protter]

Shalom,

Yes, I do not believe reinstalling perl would be of any value here.

What could be happening is a runtime environment error, where the wrong version of perl is being picked up by the test, or perhaps the environment, PATH, SHLIB_PATH was wrong when you built the perl module.

SEP

[James R. Ferguson]

Hi (again):

A better answer to your original question can be found in the 'Config' module documentation:

http://perldoc.perl.org/Config.html

It notes that "Because this information is not stored within the perl executable itself it is possible (but unlikely) that the information does not relate to the actual perl binary which is being used to access it."

Regards!

...JRF...