Perl error?

[Bob Isaac]

We have two version of Perl on our server:
Perl 5.8.5 at /home/csperl/bin/perl
System Perl 5.6.0 at /usr/bin/perl

We can use either it is just you cannot upgrade system Perl on our type of server.

We do not have perl at:
/usr/local/bin/perl

So why do most of the .pm files have #!/usr/local/bin/perl at the top. Some have #!perl and one has #!perl -wc, and others have the correct path of /usr/bin/perl.

???

[NormanRouxel]

All the Perl scripts that Actinic uploads have their hash bang line (the first line e.g. #!/usr/bin/perl) set to the entry in Advanced / Network Setup / Path to the Perl Shell.

Best check to see what's in there.

[Bob Isaac]

The hash bangs are there, just didn't bother to put them in the message. The entry in Network Setup is /usr/bin/perl, so where the heck did usr/local/bin/perl come from.

[NormanRouxel]

Maybe they're non-Actinic files (you didn't name any) or obsolete ones left from earlier testing.

[Bob Isaac]

These are dated 24 May after a refresh:

dc000001.pm - has #!perl -wc

ac000001.pm - has #!perl

ad000001.pm - has #!/usr/local/bin/perl

Bob

[NormanRouxel]

Now I see. You only see this on .pm files and not .pl ones.

These look like relics from the writing and testing of these Modules. The #! line isn't needed on a module (.pm's are loaded by other .pl scripts and by then the system knows the language it's running) and is probably being interpreted simply as a comment.

[zmagyar]

These look like relics from the writing and testing of these Modules.

Correct. The shebang line is ignored by perl in pm files. But our developers are using it to check the syntax before the code is checked in to the repository. So basically the shebang line tells you where is the perl located on the developer's server who last changed the file.

Regards,

[Bob Isaac]

It still does not answer why a non existent path to Perl is shown - /usr/local/bin/perl - or am I missing something.

Bob

[NormanRouxel]

Zoltan just accurately answered you (it was as I expected) above.