I tried to run several tasks (written in perl) on a 8-core node (divided into 8 tasks), but encounter an error for finding a perl module. I tested single task on one thread, no such problem occurred. The weird thing is that the module path is already in ENV path when checking with perl -V.
The perl file that gives error begins like this:
#!/usr/bin/perl
use strict;
use warnings;
use XML::Parser; ...
Error message is like this:
Can't locate XML/Parser.pm in @INC (@INC contains: ... /usr/lib64/per
+l5 /usr/share/perl5 .) at ./blast_parser.pl line 4.
BEGIN failed--compilation aborted at ./blast_parser.pl line 4.
[blastall] FATAL ERROR: File write error
The interesting thing is that XML::Parser.pm is in the path of /usr/lib64/perl5 that is listed in above @INC and in %ENV (I checked). I tried to include this path in perl file (use lib ), but got same error message. Couldn't figure out where is wrong and how to solve.
The perl version: v5.10.1 (*) built for x86_64-linux-thread-multi.
Linux version: 2.6.32-358.2.1.el6.x86_64
Thanks for any suggestions.
Wayne
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|