Khen1950fx: I ran your program. Here is the output:
Database was generated on Wed, 08 May 2013 21:53:13 GMT
Term::ReadLine is up to date (1.10).
Running install for module 'Term::ReadLine::Gnu'
Running make for H/HA/HAYASHI/Term-ReadLine-Gnu-1.20.tar.gz
Fetching with LWP:
http://cpan.strawberryperl.com/authors/id/H/HA/HAYASHI/Term-ReadLine-G
+nu-1.20.tar.gz
Fetching with LWP: http://cpan.strawberryperl.com/authors/id/H/HA/HAYA
+SHI/CHECKSUMS
Checksum for F:\...\SBPerl\cpan\sources\authors\id\H\HA\HAYASHI\Term-R
+eadLine-Gnu-1.20.tar.gz ok
CPAN.pm: Building H/HA/HAYASHI/Term-ReadLine-Gnu-1.20.tar.gz
Could not find neither libtermcap.a, libncurses.a, or libcurses.
Warning: No success on command[F:\...\SBPerl\perl\bin\perl.exe Makefil
+e.PL]
HAYASHI/Term-ReadLine-Gnu-1.20.tar.gz
F:\...\SBPerl\perl\bin\perl.exe Makefile.PL -- NOT OK
Stopping: 'install' failed for 'Term::ReadLine::Gnu'.
What to do?
Many TIA - Helen
Update:
I ran your program with Term::ReadLine::Perl instead of: Term::ReadLine::Gnu, and it responded with:
Database was generated on Wed, 08 May 2013 21:53:13 GMT
Term::ReadLine is up to date (1.10).
Term::ReadLine::Perl is up to date (1.0303).
Term::UI is up to date (0.34).
So this looks ok.
And now, when I run cpanp, it's not complaining that "terminal is not fully functional". Which is good.
Correction: sorry, that problem is still there.
But this was not the main, original problem. The main problem was, that CPANPLUS was not recognizing the new Perl installation, although I've changed the "PATH" in the right way.
I'll try using cpanp again, and report back.
Many thanks - Helen
-
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.