BEGIN {
          
          push(@INC,"/opt/perl5/lib/5.6.1");
  }

#rest of code follows
[download]

You need to change @INC in a BEGIN block in order for it to affect use commands, since they take effect at BEGIN-time. But Octavian is using require 'timelocal.pl';, which takes place at run time (Octavian: you seem to be using some old code with some old syntax; are you sure there isn't something newer that might be easier to use?). So Beatnik's change of @INC at run time is enough, as long as it takes place before the require.

Yet More Ways of setting @INC before your script starts running (and thus in time to affect both use and require):

1. Add them to your shebang line:

   #!/path/to/perl -w -I/opt/perl5/lib/5.6.1
   [download]

2. use lib:

   use lib qw(/opt/perl5/lib/5.6.1);
   [download]

   (this also works in a module, of course)
Use either, not both!

Either is preferable to manipulating @INC directly: it's clearer, and you get nicer behaviour simpler (e.g. beatnik's and Azatoth's code above adds the new directory as the last directory to be searched; you'd usually want to search it first).

I noticed this problem further down the page after I posted this....I see it is not just myself that is having a problem....does HP11.11 not play nice with perl or something? and I cant do your fix just yet, because I am also having a problem with the @ symbol...seems I cant type it on this friggen system....it kind of acts like a Ctrl-W key or something...it is really messed up *sigh*

Your @ woes are UN*X-related, not Perlish.

You know it's a UNIX system when backspace does something else.

In your case, stty sane (typed at the shell!) should fix things). If not, stty werase ^w should help.

Bonus old fart points for remembering which key deletes just one character!

Update: As noted below you can't fix this with hand-editing. You can find out what your INC path is with perl -V.

Much better is to put perl where Config.pm expects it to be, or recompile perl. You need the ANSI C compiler to compile perl on HP-UX, though.

You can see what is in Config.pm by inspecting the code in the module, or with this code:

#!/opt/perl5/bin/perl
use strict;
use Config;
for (keys %Config)
{
  print "$_ = $Config{$_}\n";
}
[download]

You can use the INC path methods above to get the use Config line to work.

It should work perfectly the first time! - toma

You should recompile Perl not because Config.pm is hard to edit by hand but because the values for @INC are compiled into the perl binary, not read from Config.pm! Otherwise, how would Perl find Config.pm? (:

Now, MakeMaker does read Config.pm so you can affect where modules get installed by modifying that file.

        - tye (but my friends call me "Tye")