Haining,
What I generally do is to build the module in place. Typically that just
means expanding the tar file, which typically creates a subdirectory
anyway, SETting DEFAULT to that subdirectory, and then
$ perl makefile.pl
$ mmk
$ mmk test ! If there is one
$ ! Privilege may be needed for the install.
$ mmk install
This is definitely the low-tech way to go, but it keeps you out of trying
to out-think DCL's and C's case-changing rules. I can't definitely say that
it will solve your build problem, though - I'm just offering a bit of
philosophy for what it's worth.
For actually _solving_ the problem, I defer to Craig Berry's last
paragraph. You might also want to say which "C" you're using (name and
version), and which IP stack you're using. Your letter implies you're using
MMS. True? Which version?
Cutting and pasting from actual command output is the best way I know to
get the build errors (etc) reported accurately - but you might want to edit
the output before you post it, to hide things like actual computer names,
and maybe even usernames or directory names. Don't change directory nesting
depth, though - it may be important expecially if you're not at VMS 7.2 or
above.
I have assumed from your mailing address that you have given your name in
Western order. If in error, I apologize.
Tom Wyant
Haining Yao <[EMAIL PROTECTED]> on 10/28/2002 04:41:45 PM
To: [EMAIL PROTECTED]
cc:
Subject: install perl module locally
Hello,
I am trying to use a perl script which works on Unix system on VMS. But
there are some modules not included in standard Perl lib. The person who
used the perl script on Unix suggested me to install the modules I need
locally, because he did so.
I've downloaded the modules from CPAN. But i had problems when i tried to
install them locally. I also tried to install them on Linux system and
there is no problem on Linux.
Under Linux /tmp, i did
linux>perl Makefile.pl PREFIX=/tmp
then after "make install", the folds
/tmp/lib/site_perl/5.6.0/i386-linux/xxxx, etc were automatically created
for me.
But on VMS, things are different.
vms>perl Makefile.pl prefix=disk$user:[usr.perlmod]
This looks good. But when i do this
vms>mms
I got abort messages like these:
%MMS-F-ABORT, For target VECTOR.OBJ, CLI returned abort status: %X10B91260.
May I use the same way like on Linux to install modules on VMS, like 'perl
Makefile.pl PREFIX=path'? Has anybody done the installation locally before?
Thanks very much for any help.
Regards,
Haining Yao
This communication is for use by the intended recipient and contains
information that may be privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender
by return e-mail and delete this e-mail from your system. Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer. This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.
Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean
http://www.DuPont.com/corp/email_disclaimer.html
