Craig A. Berry wrote:
Show quoted text>
> On Apr 10, 2009, at 4:20 PM, Michael G Schwern wrote:
Show quoted text> GNV should not be assigning that logical name and later versions than
> the one they've got there don't. It should be safe just to deassign it.
>
> $ @gnv$gnu:[lib]gnv_setup.com
> $ show log bin
> "BIN" = "GNV$GNU:[BIN]" (LNM$PROCESS_TABLE)
> $ deassign bin
> $ sh log bin
> %SHOW-S-NOTRAN, no translation for logical name BIN
I was not aware of a later version than what I put on Encompasserve.
While I submitted the code to the maintainer for rebuilding the kit, I
had not heard of any new releases.
The version of GNV on Encompasserve puts the BIN logical in the process
table instead of the system table as the HP version did at the time I
installed it, so deassigning it to run Perl is the thing to do.
I will have to go to the HP web site to get a later GNV to see if they
put in all the changes I submitted.
Show quoted text> I don't think there's much MakeMaker can or should do about it unless
> you want to put C<$ENV{bin} = undef> in a BEGIN block or something.
I do not think you want to do that. Won't that delete the first logical
name "BIN" in the default logical search list, if the person has
sufficient privilege?
We really need logical name handling as part of PERL on VMS so that
tests can work around these issues.
The best generic work around that I can think of is to check to see if
$ENV{bin} exists on VMS and if so create a new defintion that is needed
for the test.
Unfortunately without true logical name support, there is no generic way
to clean it up inside of Perl.
Regards,
-John
wb8tyw@qsl.net
Personal Opinion Only
