Re: Installing Perl Modules on a PC?
by gube (Parson) on Aug 04, 2005 at 01:39 UTC
|
| [reply] |
Re: Installing Perl Modules on a PC?
by Anonymous Monk on Aug 04, 2005 at 02:29 UTC
|
| [reply] |
Re: Installing Perl Modules on a PC?
by rvosa (Curate) on Aug 04, 2005 at 01:47 UTC
|
Is it the __ftol2 call that fails? Maybe it works if you change the makefile to include the /QIfist switch. | [reply] |
|
| [reply] [d/l] |
Re: Installing Perl Modules on a PC?
by gellyfish (Monsignor) on Aug 04, 2005 at 08:04 UTC
|
| [reply] |
|
ppm
install TermReadKey
That's it!
-----------------------------------
Washizu
Odd Man In: Guns and Game Theory
| [reply] [d/l] |
Re: Installing Perl Modules on a PC?
by holli (Abbot) on Aug 04, 2005 at 07:33 UTC
|
If you just want to clone your home installation, copy the perl/html, perl/lib and perl/site/lib directories on your usb stick and from there over the fresh installation.
| [reply] |
|
I'm not really sure what the level of expertise/confidence with perl of the OP is, but to be safe it may be worth to remind him that if the modules to install comprise binary ones, then the two versions of Perl must be the same. Who knows? Maybe he has 5.6.1 at home and has installed 5.8.7 at his friend's...
| [reply] |
Re: Installing Perl Modules on a PC?
by rjsaulakh (Beadle) on Aug 04, 2005 at 08:56 UTC
|
I dont know how will u like my reply but i have tried this way once i find it difficult to install modules by standard methods
what you can do is download the module copy nmake and nmake.err files into the module folder (after unzipping
) then type perl makefile.pl , nmake , nmake test , nmake intall
please let me know if that helps u
| [reply] |
|
| [reply] |
Re: Installing Perl Modules on a PC?
by hawtin (Prior) on Aug 04, 2005 at 14:00 UTC
|
I had to do this today (new laptop running XP rather than Win 2000). Previously I had
a 5.6 but I decided to move up to 5.8. What I found was
that I needed to also set an environment variable to get
Term::ReadKey to work for me. I set TERM to dumb in the
System control panel and everything seems to be working
again.
| [reply] |
|
I'd be surprised by this, Term::ReadKey itself does not reference $ENV{TERM} at all and uses a lower level device interface (POSIX termios mostly, but the Console interface on windows) that doesn't need to know what the terminal type is, particularly on Windows where there is no real notion of varying terminal types. I can only assume that you are also using some other module that does care about the terminal type.
Of course if you are convinced of this I would love for you to send me some test code that demonstrates this so I can work out what is going on and fix it.
/J\
| [reply] [d/l] |