I have run into a problem starting GRass5.0Beta_linux.tar.gz
I am currently runmning Red Hat 6.2 and using Gnome.
Upon startup, I recieve the same message that was discuused in Decmeber
with the Libcurses.so.5 directory not being found.
I have installed that Linux RPM and I stilll have the problem.
One erson has responded by indicating that the libcurses library needs
to be linked.
I am lost, any suggestions to solve this problem
Kirk Schmidt
On Thu, Feb 08, 2001 at 08:55:47AM -0500, Kirk Schmidt wrote:
I have run into a problem starting GRass5.0Beta_linux.tar.gz
I am currently runmning Red Hat 6.2 and using Gnome.
Upon startup, I recieve the same message that was discuused in Decmeber
with the Libcurses.so.5 directory not being found.
I have installed that Linux RPM and I stilll have the problem.
One erson has responded by indicating that the libcurses library needs
to be linked.
I am lost, any suggestions to solve this problem
Kirk,
check your Linux CDROMs for the "ncurses 5" library. Install it and enjoy
GRASS. I am wondering that ncurses was not installed by default...
Hope this helps
Markus Neteler
Just an update for the record.
I verified that ncurses.so.5 was installed on my system, I checked in the
usr/lib/ directory and a file called libncurses.so.4.0 was present. I
copied the file and called it libncurses .so.5 and my problems were solved.
Kirk
Markus Neteler wrote:
On Thu, Feb 08, 2001 at 08:55:47AM -0500, Kirk Schmidt wrote:
> I have run into a problem starting GRass5.0Beta_linux.tar.gz
> I am currently runmning Red Hat 6.2 and using Gnome.
>
> Upon startup, I recieve the same message that was discuused in Decmeber
> with the Libcurses.so.5 directory not being found.
>
> I have installed that Linux RPM and I stilll have the problem.
>
> One erson has responded by indicating that the libcurses library needs
> to be linked.
>
> I am lost, any suggestions to solve this problem
Kirk,
check your Linux CDROMs for the "ncurses 5" library. Install it and enjoy
GRASS. I am wondering that ncurses was not installed by default...
Hope this helps
Markus Neteler
On Fri, 9 Feb 2001, Kirk Schmidt wrote:
I verified that ncurses.so.5 was installed on my system, I checked in the
usr/lib/ directory and a file called libncurses.so.4.0 was present. I
copied the file and called it libncurses .so.5 and my problems were solved.
I have a similar problem, but it has so far resisted a solution. My RH 6.2
system (actually 6.1 with all the packages upgraded to the latest and
greatest) has libncurses.so.4 installed (plus the old glibc5 versions of 3
and 1.x). But, when I try to install ncurses-5.2-5.i386.rpm, I cannot.
If I use the upgrade (-U) option, I'm told that too many apps require the
.4 version. So, I tried the install option (-i) to add the new version, too.
That failed because of conflicts with a version (ncurses-5.0-2) that cannot
be found in any form on my system.
I know this is a linux problem, not a GRASS problem, and I've asked for
help from the local users group. My frustration is that it should be a
no-brainer to add a new version of the ncurses library without removing the
older version. Turns out to be a major project. Sigh.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
On Mon, 12 Feb 2001, Rich Shepard wrote:
If I use the upgrade (-U) option, I'm told that too many apps require the
.4 version. So, I tried the install option (-i) to add the new version, too.
That failed because of conflicts with a version (ncurses-5.0-2) that cannot
be found in any form on my system.
I know this is a linux problem, not a GRASS problem, and I've asked for
help from the local users group. My frustration is that it should be a
no-brainer to add a new version of the ncurses library without removing the
older version. Turns out to be a major project. Sigh.
It sounds like an RPM problem rather than an actual linux problem.
Ignoring probable problems with version compatibility, you could just
create a softlink to libncurses4.0 and call it libncurses5.0.
Alternatively you could find the binary in a non-RPM package and install
it where it needs to be, or you could get the source package, compile it
and install it where it needs to be.
Personally I try to get everything as source code and compile if for my
system because in the past I frequently lost capabilities and had minor
incompatibilities in pre-compiled binaries. Things *are* improving now
and I doubt those problems are as common as they once were.
Roger Miller
Lee Wilson and Associates
Have you tried just making a link (ln -s) from your old library file to
the file name that your application (GRASS) wants?
Peter Earle
Biology Department
Memorial University
St. John's, NF
Canada
A1B 3X9
On Mon, 12 Feb 2001, Rich Shepard wrote:
On Fri, 9 Feb 2001, Kirk Schmidt wrote:
> I verified that ncurses.so.5 was installed on my system, I checked in the
> usr/lib/ directory and a file called libncurses.so.4.0 was present. I
> copied the file and called it libncurses .so.5 and my problems were solved.
I have a similar problem, but it has so far resisted a solution. My RH 6.2
system (actually 6.1 with all the packages upgraded to the latest and
greatest) has libncurses.so.4 installed (plus the old glibc5 versions of 3
and 1.x). But, when I try to install ncurses-5.2-5.i386.rpm, I cannot.
If I use the upgrade (-U) option, I'm told that too many apps require the
.4 version. So, I tried the install option (-i) to add the new version, too.
That failed because of conflicts with a version (ncurses-5.0-2) that cannot
be found in any form on my system.
I know this is a linux problem, not a GRASS problem, and I've asked for
help from the local users group. My frustration is that it should be a
no-brainer to add a new version of the ncurses library without removing the
older version. Turns out to be a major project. Sigh.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
On Mon, 12 Feb 2001, Peter Earle wrote:
Have you tried just making a link (ln -s) from your old library file to
the file name that your application (GRASS) wants?
Peter,
No, I didn't. Perhaps I'm wrong, but I assume that the newer version of
the library has changes that the GRASS-beta-11.2 requires.
Thanks for the idea,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
On Mon, 12 Feb 2001, Roger S. Miller wrote:
Personally I try to get everything as source code and compile if for my
system because in the past I frequently lost capabilities and had minor
incompatibilities in pre-compiled binaries. Things *are* improving now
and I doubt those problems are as common as they once were.
Thanks, Roger. I've had a number of SysAdmins here tell me that they
always get the source package and rebuild it on their systems. I'm trying to
be lazy because I have too much to do as it is. However, this appears to be
the most parsimonious solution.
I shall go forth and hunt down the .src.rpm and rebuild it in house.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
On Mon, Feb 12, 2001 at 09:28:12AM -0800, Rich Shepard wrote:
On Mon, 12 Feb 2001, Peter Earle wrote:
> Have you tried just making a link (ln -s) from your old library file to
> the file name that your application (GRASS) wants?
Peter,
No, I didn't. Perhaps I'm wrong, but I assume that the newer version of
the library has changes that the GRASS-beta-11.2 requires.
Rich,
the libncurses5 is the same since month. I build the linux binaries
of GRASS-beta-11.2 on the same linux box as GRASS-beta-11.1 as
GRASS-beta-10 (maybe GRASS-beta-9 as well). So there was no change
in libncurses as far as I can remember (ah yes, installed 30. Jul 2000).
Simply get the ncurses5.rpm and feel happy...
http://rpmfind.net/linux/rpm2html/search.php?query=ncurses
Markus