David Mertens wrote: > David Mertens wrote: > > Anyway, this is only a problem in that one stale terminal window. I've > closed it now and I have no trouble. The cause of this problem is a > convoluted mess, hard for others to duplicate even if they wanted to, so > hopefully it won't be a problem for anybody else. > > David > > P.S. Do you think I should file a bug report with the bash folks?
David- I'm glad you resolved your problem. It sounds like it was the version skew between the already installed PDL and your newly installed via CPAN version. We've seen problems with PDL testing where a couple of tests fail but were never installed in the newer PDL---but the original, older version was found in the system perl paths. As long as your @INC path has the directories with the new PDL first you should not have problems. No, this is not a bug with bash. To speed performance, bash caches the locations of the executables in the path rather than searching the file system everytime you type a command name. As you discovered, a clean bash system has everything up to date and working. --Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
