>Hmm.  I also noted the following information while running:
>Logical name T found in environment as 
>DYM$SOURCE:[DYMAX.PERL5006_ACTIVE.PERL-5_6_1.HARNESS]
> deassign before building perl5
>A:..ACTIVE.PERL-5_6_1>

 I expect you may have already looked at this;
 no offense intended, but is there even a small chance
 the (process/job) environment differs between the systems
 you mentioned?
 
 I bring this up because I was bitten a few time
 by conflicts w/ cli symbols, process/job/group logicals.

 Notably, "TMP", "LIB", "T",  and probably others.
 often enough on the core install and tests, but
 more often when building extensions.
 
 such that I now use a 'special' account, which is 
 a member of an otherwise unused UIC group, logged 
 via <username/NOCOMMAND,  w/ $delete/sym/glob *, 
 $delete/sym/local * to a achieve an account environment 
 w/ a bare minimum of existing symbols, logicals, etc.

 sometimes, I'll use the same account to 
 when troubleshooting errant perl scripts, to rule out 
 some dependency/conflict w/ symbols/logicals

Reply via email to