niXforums Forum Index
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   PreferencesPreferences   Log in to check your private messagesLog in to check your private messages   Log inLog in 
·  nixdoc.net ·  man pages ·  Linux HOWTOs ·  FreeBSD Tips ·  Forums
navigation Forum index » Not Unix » VMS » vmsperl
[BUG] option for shared perl_root is broken
Post new topic   Reply to topic Page 1 of 1 [2 Posts] View previous topic :: View next topic
Author Message
Frans Slothouber
*nix forums beginner


Joined: 12 Jan 2006
Posts: 5

PostPosted: Mon Jan 16, 2006 12:14 pm    Post subject: [BUG] option for shared perl_root is broken Reply with quote

One of the questions that configure.com ask is:

"Will you be sharing your PERL_ROOT with a VAX or Alpha? [n]"

this in theory allows you to build perl on a VAX, Alpha, and IX
and let them share a common root-directory for the libs and docs.
It does this by creating a perl executable with a different postfix
for each type of machine.

Since our shop runs Perl on all these machines it seemed it nice
idea to try this out.

The problem is that the build fails with:

MCR Sys$Disk:[]miniperl.ixe "-I[.lib]" -"I[-.lib]" [.POD]PODSELECT.PL
Extracting podselect.com (with variable substitutions)
Copy/NoConfirm/Log [.pod]podselect.com [.lib.pods]
%COPY-S-COPIED, DISK$PROSY_USER:[PROSY.FRANS.PERL.POD]PODSELECT.COM;1
copied to
DISK$PROSY_USER:[PROSY.FRANS.PERL.LIB.PODS]PODSELECT.COM;1 (6 blocks)
%DCL-W-ACTIMAGE, error activating image SYS$DISK:[]MINIPERL.EXE
-CLI-E-IMAGEFNF, image file not found
$1$DGA22:[PROSY.FRANS.PERL]MINIPERL.EXE;
%MMS-F-ABORT, For target EXTRA.PODS, CLI returned abort status: %X100388B2.

This can be fixed and the build can run until completion.
However, a
mms /macro=("IXE=1") test
then reports a lot of failed tests for the IX and Alpha, as there
are a number of test scripts that hard-coded the name of the
perl executable to be perl.exe


Maybe it is a good idea for the upcomming release to skip
the shared root question as it is currently pretty broken.
(So we don't waste people time by letting them try something
that does not work).


Have fun,
Frans.
Back to top
Craig A. Berry
*nix forums Guru Wannabe


Joined: 27 May 2005
Posts: 143

PostPosted: Tue Jan 17, 2006 1:53 pm    Post subject: Re: [BUG] option for shared perl_root is broken Reply with quote

At 1:14 PM +0100 1/16/06, Frans Slothouber wrote:
Quote:
One of the questions that configure.com ask is:

"Will you be sharing your PERL_ROOT with a VAX or Alpha? [n]"

this in theory allows you to build perl on a VAX, Alpha, and IX
and let them share a common root-directory for the libs and docs.
It does this by creating a perl executable with a different postfix
for each type of machine.

Since our shop runs Perl on all these machines it seemed it nice
idea to try this out.

The problem is that the build fails with:

MCR Sys$Disk:[]miniperl.ixe "-I[.lib]" -"I[-.lib]" [.POD]PODSELECT.PL
Extracting podselect.com (with variable substitutions)
Copy/NoConfirm/Log [.pod]podselect.com [.lib.pods]
%COPY-S-COPIED, DISK$PROSY_USER:[PROSY.FRANS.PERL.POD]PODSELECT.COM;1
copied to
DISK$PROSY_USER:[PROSY.FRANS.PERL.LIB.PODS]PODSELECT.COM;1 (6 blocks)
%DCL-W-ACTIMAGE, error activating image SYS$DISK:[]MINIPERL.EXE
-CLI-E-IMAGEFNF, image file not found
$1$DGA22:[PROSY.FRANS.PERL]MINIPERL.EXE;
%MMS-F-ABORT, For target EXTRA.PODS, CLI returned abort status: %X100388B2.

Yes, there is a bug in the way we generate extra_pods.com from
configure.com. A manual edit of extra_pods.com should get you going
again, as you perhaps have already figured out.

Quote:
This can be fixed and the build can run until completion.
However, a
mms /macro=("IXE=1") test
then reports a lot of failed tests for the IX and Alpha, as there
are a number of test scripts that hard-coded the name of the
perl executable to be perl.exe


Maybe it is a good idea for the upcomming release to skip
the shared root question as it is currently pretty broken.
(So we don't waste people time by letting them try something
that does not work).

I'm reluctant to take away the ability to do shared roots just
because we don't have all the pieces working (and possibly never
will). I would vote more in favor of a documentation update.

Thanks for the report.
--
________________________________________
Craig A. Berry
mailto:craigberry@mac.com

"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
Back to top
Google

Back to top
Display posts from previous:   
Post new topic   Reply to topic Page 1 of 1 [2 Posts] View previous topic :: View next topic
The time now is Sat Nov 22, 2008 1:47 pm | All times are GMT
navigation Forum index » Not Unix » VMS » vmsperl
Jump to:  

Similar Topics
Topic Author Forum Replies Last Post
No new posts pflogsumm broken again? cnschulz Postfix 0 Wed May 14, 2008 2:28 am
No new posts pflogsumm broken again? cnschulz Postfix 0 Wed May 14, 2008 2:27 am
No new posts database Share Memory Limit (2 GB ) in a Instance is tota... sadanjan@gmail.com IBM DB2 0 Fri Jul 21, 2006 12:57 pm
No new posts ImportError: libclntsh.so.10.1: cannot open shared object... gmax2006 python 2 Thu Jul 20, 2006 7:05 pm
No new posts Help! Shared memory is getting deleted after process is k... Anuradha apps 3 Thu Jul 20, 2006 8:42 am

Free Advertising | Credit Cards | Lighting | Mortgage Calculator | Share Prices
Copyright © 2004-2005 DeniX Solutions SRL
 
Other DeniX Solutions sites: Unix/Linux blog |  electronics forum |  medicine forum |  science forum | 
Privacy Policy


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1852s ][ Queries: 16 (0.0960s) ][ GZIP on - Debug on ]