Hi Zaxo,
Thanks for the quick reply!
The code works great on my machine with Perl 5.8...but, I am trying to run on a machine that has this version of perl!
(This all runs in a "modified" DOS cmd window that sets all kinds of PATH's for the custom application)
C:\Perl\Weir_scripts>perl -c import_prod.pl
Ambiguous use of eval => resolved to "eval" => at ..\lib/re.pm line 81.
Perl 5.006 required--this is only version 5.00307, stopped at ..\lib/File/Basena
me.pm line 142.
BEGIN failed--compilation aborted at ..\lib/File/Basename.pm line 142.
BEGIN failed--compilation aborted at import_prod.pl line 3.
C:\Perl\Weir_scripts>perl -v
This is perl, version 5.003_07
So, I installed 5.8 & now have "two" versions of perl on this machine.
But, some consultants came in and installed this "old" version on the machine for use with their exisiting scripts!
Can I still upgrade without causing harm to the old stuff?
I know I can remove the old paths in the enviroment section in Windoze.
But, the application may not know where to look....sigh.
I need these ENV vars:
C:\Perl\Weir_scripts>set IMAN
IMAN_BIN=c:\ugs\tceng912\bin
IMAN_DATA=c:\ugs\imandata\testdata
IMAN_DB_CONNECT=infodba:tbwiabd@test
IMAN_DISABLE_FLASH=true
IMAN_HELP_FILE=c:\ugs\tceng912\web\htdocsimanhelp\imanhelp.hlp
IMAN_INCLUDE=c:\ugs\tceng912\include
IMAN_INIT_DIR=C:\DOCUME~1\ADMINI~1.WIL\LOCALS~1\Temp\1
IMAN_LANGUAGE=c:\ugs\tceng912\lang
IMAN_LIBRARY=c:\ugs\tceng912\lib
IMAN_LOCALIZATION_DIR=en
IMAN_LOG=c:\ugs\imandata\testdata\log_wilmsntch5_test
IMAN_MSG_ROOT=c:\ugs\tceng912\lang\textserver
IMAN_PRINTER=lpr.exe
IMAN_ROOT=c:\ugs\tceng912
IMAN_SYS_UID_DIR=c:\ugs\tceng912\lang\vt100
IMAN_TMP_DIR=C:\DOCUME~1\ADMINI~1.WIL\LOCALS~1\Temp\1
IMAN_TRACEBACK=ON
IMAN_UG_DEFAULT_PART=c:\ugs\imandata\testdata\blank_english.prt
IMAN_USER_TOOLS=c:\ugs\tceng912\local\tools
IMAN_XML_ENCODING=ISO-8859-1
C:\Perl\Weir_scripts>set ORACLE
ORACLE_HOME=c:\ugs\tceng912
ORACLE_SERVER=wilmsntch5
ORACLE_SID=test
Here is where they store and access the perl binary:
C:\UGS\tceng912\bin>dir perl.exe
Volume in drive C has no label.
Volume Serial Number is 0CF2-5BB1
Directory of C:\UGS\tceng912\bin
07/02/1998 03:32 PM 87,040 perl.exe
1 File(s) 87,040 bytes
0 Dir(s) 12,339,765,248 bytes free
C:\UGS\tceng912\bin>perl -v
This is perl, version 5.003_07
What can I do?
I am afraid that I can;t jsut copy the new 5.8 Perl binary(perl.exe) to this dirsctory and go from there.
Or can I?
Are there depends, dll's or the like to worry about?
Even application depends too?
Any help is greatly appreciated!!
Thank-you.
| [reply] |
Besides shooting the consultants?
Perl 5.003_07 is old! Perl 5.004 was released in May 1997, if my reckoning is right. Did those guys clobber your 5.8 binary? If that's all, you can move theirs to /path/to/perl5_003_07.exe and recopy your proper binary back in. With ActiveState, the binary is version-labeled, so they probably didn't bother to clobber that unless they uninstalled the whole thing. Shooting's too good for them if they did that.
I'm not too familiar with winders, but you might be able to associate just their crusty script with their old perl, and let your modern installation handle everything else. On unix, all you would need to do is change the splatline.
I wonder if their old perl is even a complete installation?
You have a better chance of running old scripts on new perl than the reverse. If the contractor script won't run on new perl, you should take a hard look at its quality. If the consultants haven't updated their script in eight years of improvements to perl, consider their quality.
Update: Sorry, there's not much more I can say without looking at the scripts and the details of your installation. You can make output like that look better on pm by enclosing it in <code> . . . </code> tags. They are sort of super pre tags.
| [reply] |
Zaxo,
Yep, very old indeed.
No, their Perl installation was their first with the app installation.
I installed a new version afterwards but their application ENV points at their version only in PATHing.
I tryed moving their binary to _bak and the new 5.8 to their bin dir, but my scripts are not running right?
At least any scripts that have use <mod> in them?
Am I doing something wrong?
Their version is an "old" active state as mine is new.
I sent an email to their support at support.ugs.com.
Unfortuantely, a group in our company already hired and paid them to do their work....
I am not sure how complete the installation is for sure...
Location of the Application's version of Perl distro & bin dir:
C:\UGS\tceng912\bin>dir perl*
Volume in drive C has no label.
Volume Serial Number is 0CF2-5BB1
Directory of C:\UGS\tceng912\bin
12/13/2004 09:52 AM 41,033 perl.exe
07/02/1998 03:32 PM 87,040 perl.exe_bak
07/02/1998 03:35 PM 564,736 perl300.dll
07/02/1998 03:34 PM 30,720 perlglob.exe
C:\UGS\tceng912\perl5>dir bin
Volume in drive C has no label.
Volume Serial Number is 0CF2-5BB1
Directory of C:\UGS\tceng912\perl5\bin
11/02/1999 03:53 PM 50,688 perl.exe
11/02/1999 03:53 PM 524,288 perlcore.dll
11/01/1999 09:53 PM 277,504 PerlCRT.dll
Sorry about the mess below here....is there an easier way to add paragraphs and breaks in the html?
An editor or ?
C:\UGS\tceng912\perl5>dir lib
Volume in drive C has no label.
Volume Serial Number is 0CF2-5BB1
Directory of C:\UGS\tceng912\perl5\lib
>br>
01/24/2005 03:45 PM <DIR> .
01/24/2005 03:45 PM <DIR> ..
01/24/2005 03:45 PM <DIR> auto
11/01/1999 09:53 PM 10,275 AutoLoader.pm
11/01/1999 09:53 PM 10,577 Carp.pm
01/24/2005 03:45 PM <DIR> CGI
11/01/1999 04:53 PM 197,132 CGI.pm
08/19/2002 04:26 PM 137,333 Config.pm
11/01/1999 03:53 PM 10,280 Cwd.pm
11/02/1999 03:53 PM 24,422 DynaLoader.pm
11/01/1999 09:53 PM 14,579 Exporter.pm
11/01/1999 09:52 PM 2,990 Fcntl.pm
01/24/2005 03:45 PM <DIR> File
11/01/1999 03:53 PM 7,044 FileHandle.pm
01/24/2005 03:45 PM <DIR> iman
01/24/2005 03:45 PM <DIR> IO
11/01/1999 03:53 PM 3,844 lib.pm
11/01/1999 03:53 PM 3,942 re.pm
11/01/1999 03:53 PM 1,102 SelectSaver.pm
11/01/1999 04:53 PM 928 shellwords.pl
11/01/1999 03:53 PM 7,873 sigtrap.pm
01/18/2038 09:14 PM 2,271 strict.pm
11/01/1999 03:53 PM 3,893 Symbol.pm
01/24/2005 03:45 PM <DIR> Sys
11/01/1999 09:53 PM 2,473 vars.pm
Any other suggestions?
Thanks for any help on this issue.
Scott
| [reply] |