Forum Moderators: bakedjake

Message Too Old, No Replies

Problem with MyTOP

problem with required perl module

         

AprilS

7:24 am on Jul 27, 2004 (gmt 0)

10+ Year Member



I installed MyTOP - which was quite easy. However, when installing I got a warning:
Warning: prerequisite Term::ReadKey 2.1 not found.

So I first looked to see if it was on the system..nope. So then I installed it from cpan:
perl -MCPAN -e shell
install Term::ReadKey

It installed and then confirmed it was up to date. So I then went back to MyTOP and reinstalled...but I got the SAME warning that Rerm::ReadKey 2.1 was not installed. So then I went into 3 perl directories and added a directory "Term" and put the module there (out of desparation) - that did not work. So then I just took the line out of the Makefil.PL that checks for Term::ReadKey... thinking MyTop would see it and that the Makefile was just being anal.

Well, then I finished the install and tried MyTOP, but got the following error:

Can't locate loadable object for module Term::ReadKey in @INC (@INC contains: /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 .) at /usr/bin/mytop line 169

I couldn't figure it out, so then I downloaded the module from the developer along with his Makefile.PL and installed it manually. I got the SAME error with MyTOP - it couldn't see the module.

Then I rebooted the server...just in case. But, that did not help.

So then I went into MyTOP itself and added the following line of code to show it EXACTLY where the Termm::ReadKey module was located:

BEGIN {
unshift (@INC, "/usr/lib/perl5/5.8.0");
}

With perl this USUALLY works...especially for those who don't know how to install modules, or can't, or just don't want to take the time to install.... but THIS didn't even work!

I have NEVER had such an issue with a perl module before.

Anyone have thoughts as to what is causing the problem here? I'm using a new install of RedHat Enterprise ES.

bakedjake

1:47 pm on Jul 28, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Does the program run? It's possible it was a bug in the installation system, and just didn't detect things properly.

AprilS

6:05 pm on Jul 28, 2004 (gmt 0)

10+ Year Member



Nope, it won't run because it doesn't see that perl module. It is completely frustrating - it's there!

bakedjake

6:27 pm on Jul 28, 2004 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Is the module installed? Yes, I know you did the install from CPAN, but did you check if the actual module is installed?

AprilS

7:16 pm on Jul 28, 2004 (gmt 0)

10+ Year Member



Yep, it is installed. In fact, since it didn't seem to work after doing the auto install from CPAN - I then downloaded it and installed it manually.... and it was installed... but the mytop script can't see it... not even when I show it EXACTLY where it is with:

BEGIN {
unshift (@INC, "/usr/lib/perl5/5.8.0");
}

It appears to have installed properly because the perl man pages for Term::Readkey are even there and readable through perldoc