I'll look into that. Next server I upgrade I will pay more attention to the
details on each step to see where the @INC is getting altered.
Thanks,
STH
On 07-Jan-2004 Tim Bunce wrote:
> Maybe your CPAN.pm config is altering @INC somehow.
>
> Tim.
>
> On Wed, Jan 07, 2004 at 01:08:00PM -0600, [EMAIL PROTECTED] wrote:
>>
>> On 07-Jan-2004 Tim Bunce wrote:
>> > On Wed, Jan 07, 2004 at 11:03:23AM -0600, [EMAIL PROTECTED] wrote:
>> >>
>> >> Has anyone done a 5.8.1 install, then use CPAN to install Bundle::DBI with a
>> >> 5.6.1
>> >> perl installed on the server? When I install perl 5.8.1 on the server then use a
>> >> CPAN script to install modules, the serever will hang or on an alpha it will run
>> >> out
>> >> of swap space, when the make test portion of DBI is running.
>> >
>> > You've not provided enough information about your PATH settings and which perl was
>> > run at each step.
>>
>> --The PERL5LIB is set to local directories that do not contian DBI.
>> --When I install 5.8.1, I use the default config, 'sh Configure -de'.
>> --Then I use CPAN to install Bundle::DBI, as well as other modules.
>>
>> Perl -V :
>>
>> Summary of my perl5 (revision 5.0 version 8 subversion 1) configuration:
>> Platform:
>> osname=dec_osf, osvers=5.1a, archname=alpha-dec_osf
>> uname='osf1 demosource.allantgroup.com v5.1 1885 alpha '
>> config_args='-de'
>> hint=recommended, useposix=true, d_sigaction=define
>> usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
>> useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
>> use64bitint=define use64bitall=define uselongdouble=undef
>> usemymalloc=n, bincompat5005=undef
>> Compiler:
>> cc='cc', ccflags ='-std -D_INTRINSICS -fprm d -ieee -I/usr/local/include
>> -DLANGUAGE_C',
>> optimize='-O4',
>> cppflags='-std -D_INTRINSICS -fprm d -ieee -I/usr/local/include -DLANGUAGE_C'
>> ccversion='V6.4-014', gccversion='', gccosandvers=''
>> intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
>> 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='ld', ldflags =' -L/usr/local/lib'
>> libpth=/usr/local/lib /usr/shlib /usr/ccs/lib /usr/lib/cmplrs/cc /usr/lib
>> /var/shlib
>> libs=-ldbm -ldb -lm -lutil
>> perllibs=-lm -lutil
>> libc=/usr/shlib/libc.so, so=so, useshrplib=true, libperl=libperl.so
>> gnulibc_version=''
>> Dynamic Linking:
>> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='
>> -Wl,-rpath,/usr/local/lib/perl5/5.8.1/alpha-dec_osf/CORE'
>> cccdlflags=' ', lddlflags='-shared -expect_unresolved "*" -O4 -msym -std -s
>> -L/usr/local/lib'
>>
>>
>> Characteristics of this binary (from libperl):
>> Compile-time options: USE_64_BIT_INT USE_64_BIT_ALL USE_LARGE_FILES
>> Built under dec_osf
>> Compiled at Dec 29 2003 15:37:16
>> %ENV:
>>
>> PERL5LIB="/usr/local/bin/tools:/usr/local/lib/tools/perlmodules:"
>> @INC:
>> /mnt/emssrv5/home/dots/Perllib/Tag
>> /usr/local/bin/tools
>> /usr/local/lib/tools/perlmodules/alpha-dec_osf
>> /usr/local/lib/tools/perlmodules
>> /usr/local/lib/perl5/5.8.1/alpha-dec_osf
>> /usr/local/lib/perl5/5.8.1
>> /usr/local/lib/perl5/site_perl/5.8.1/alpha-dec_osf
>> /usr/local/lib/perl5/site_perl/5.8.1
>> /usr/local/lib/perl5/site_perl/5.6.1
>> /usr/local/lib/perl5/site_perl
>> .
>>
>> ..Although I don't see ../5.6.1/alpha-dec_osf in the @INC, I was not able to
>> compile DBI
>> without moving the 5.6.1 dir to temp name.
>>
>>
>>
>>
>> >
>> > Posting the perl -V output of the 5.8.1 perl would confirm if it's looking
>> > in .../site_perl/5.6.1. Env vars like PERL5LIB may also be involved.
>> >
>> > Tim.
>> >
>> >> I finally was able to
>> >> resolve this by renaming /usr/local/lib/perl5/site_perl/5.6.1 to a temp name.
>> >> So 5.8.1
>> >> was using the old binaries, I was sure that I read that 5.8.1 would not use any
>> >> old XS
>> >> compiled modules. I can keep renaming the 5.6.1 dir, but I am sure there is a
>> >> better way
>> >> to do this. Sorry if this is OT, since it fails on the DBI tests, I wanted to
>> >> know if
>> >> others have run into this.
>> >>
>> >> Thanks,
>> >> STH
>> >>
>> >> --
>> >> ----------------------------------
>> >> E-Mail: [EMAIL PROTECTED]
>> >> Date: 07-Jan-2004
>> >> Time: 10:45:45
>> >> ----------------------------------
>>
>> --
>> ----------------------------------
>> E-Mail: [EMAIL PROTECTED]
>> Date: 07-Jan-2004
>> Time: 12:52:59
>> ----------------------------------
--
----------------------------------
E-Mail: [EMAIL PROTECTED]
Date: 08-Jan-2004
Time: 10:01:47
----------------------------------
