I understand that there can be a mixing of the versions. But, this is slightly unconvincing because, my perl script already populates @INC variable in the start of the script. Thus, the execution has to go with 5.6.1 now. The prolem here is when i do the same in a small test script and execute it with 5.6.1 it works. but not in the actual perl script. How can that be???
Also, there are other perl scripts, containing shell commands and getting executed with perl 5.6.1. SO, i wouldn't say that the installation of 5.6.1 is flawed.
Can there be any other reason???
| [reply] |
Well, if there is no "mixing of versions", we could not see an error message mentioning perl 5.8 when running in a 5.6.1 environment, can it? The fact that the error only occurs in a one script, but not in others, could have several reasons. First, as it seems to be a problem with a shared lib, maybe the library is only located at run time (for instance, when your script dynamically loads a module which only *then* needs that symbol, or if you shell out from your script using system, and accidentally call an external perl program using perl 5.8, but now from within a 5.6.1 environment.
Can you located the statement(s) in the code where the error occurs?
--
Ronald Fischer <ynnor@mm.st>
| [reply] |