solaris /sfw/'s vim, mutt, lynx, ... need libncurses.so.5. HELP!

Yes, I've looked at my own similar question of over
a year ago (to comp.unix.solaris), and I've also
done a google-groups search on it (libncurses),
and saw refs to a faq (Dickey's) on the problem -- but it
wasn't there -- and several other people have had
the same question (re mutt and postgreSQL).

But no real answer as to what to actually do.

(QUESTION: why the hell doesn't SUN supply the
damn thing!)

Google finds these "RPM" things (whatever *they* are), eg:

19 [14]RPM resource libncurses.so.4
20 RPM resource libncurses.so.4. Provided by. ncurses-5.0-9.ppc, A CRT
21 screen handling and optimization package. Yellow Dog PPC. ncurses ...

David Combs wrote:
> Yes, I've looked at my own similar question of over
> a year ago (to comp.unix.solaris), and I've also
> done a google-groups search on it (libncurses),
> and saw refs to a faq (Dickey's) on the problem -- but it
> wasn't there -- and several other people have had
> the same question (re mutt and postgreSQL).

But not the cd's themseleves? :-) It would seem to
be there on Solaris 9.

> But no real answer as to what to actually do.
>
> (QUESTION: why the hell doesn't SUN supply the
> damn thing!)

My home system with just stuff installed that is in the
Solaris 9 box has this library. A quick look at
/var/sadm/install/contents shows it came as part of
the SFWncur package:

home-u60:~> grep ncurses /var/sadm/install/contents
/opt/sfw/include/ncurses.h=curses.h s none SFWncur
/opt/sfw/lib/libcurses.so=libncurses.so.5.2 s none SFWncur
/opt/sfw/lib/libncurses++.a f none 0444 root bin 248112 2544 1017237034 SFWncur
/opt/sfw/lib/libncurses.a f none 0444 root bin 459676 18768 1017237016 SFWncur
/opt/sfw/lib/libncurses.so=libncurses.so.5 s none SFWncur
/opt/sfw/lib/libncurses.so.5=libncurses.so.5.2 s none SFWncur
/opt/sfw/lib/libncurses.so.5.2 f none 0755 root bin 344276 27898 1017237016 SFWncur
/opt/sfw/lib/libncurses_g.a f none 0444 root bin 3473716 48101 1017237016 SFWncur
/opt/sfw/man/man3/ncurses.3x f none 0444 bin bin 34621 13902 1017237008 SFWncur


I've never need to know it's there - everything seems to be compiled
correctly to find it themselves.

Gavin

On Thu, 08 Apr 2004 12:16:01 -0400, David Combs wrote:

> Yes, I've looked at my own similar question of over
> a year ago (to comp.unix.solaris), and I've also
> done a google-groups search on it (libncurses),
> and saw refs to a faq (Dickey's) on the problem -- but it
> wasn't there -- and several other people have had
> the same question (re mutt and postgreSQL).

$ pkgchk -l -p /opt/sfw/lib/libncurses.so.5.2
Pathname: /opt/sfw/lib/libncurses.so.5.2
Type: regular file
Expected mode: 0755
Expected owner: root
Expected group: bin
Expected file size (bytes): 344276
Expected sum(1) of contents: 27898
Expected last modification: Mar 27 07:50:16 2002
Referenced by the following packages:
SFWncur
Current status: installed

For Solaris 9: http://wwws.sun.com/software/solaris/freeware/

For Solaris 8: http://wwws.sun.com/software/solaris.../download.html

Hi,

* David Combs <dkcombs@panix.com>:
> Yes, I've looked at my own similar question of over
> a year ago (to comp.unix.solaris), and I've also
> done a google-groups search on it (libncurses),
> and saw refs to a faq (Dickey's) on the problem -- but it
> wasn't there -- and several other people have had
> the same question (re mutt and postgreSQL).

there are nice packaged software available from blastwave.org which
works out of the box.

There is also a working mutt version available which is linked against
slang which is better to work with.

Thomas

In article <c53umd$3pj$1@new-usenet.uk.sun.com>,
Gavin Maltby <G_a_v_i_n.M_a_l_t_b_y@sun.com> wrote:
snip
>>
>> (QUESTION: why the hell doesn't SUN supply the
>> damn thing!)
>
>My home system with just stuff installed that is in the
>Solaris 9 box has this library. A quick look at
>/var/sadm/install/contents shows it came as part of
>the SFWncur package:
>
>home-u60:~> grep ncurses /var/sadm/install/contents
>/opt/sfw/include/ncurses.h=curses.h s none SFWncur
>/opt/sfw/lib/libcurses.so=libncurses.so.5.2 s none SFWncur
>/opt/sfw/lib/libncurses++.a f none 0444 root bin 248112 2544 1017237034 SFWncur
>/opt/sfw/lib/libncurses.a f none 0444 root bin 459676 18768 1017237016 SFWncur
>/opt/sfw/lib/libncurses.so=libncurses.so.5 s none SFWncur
>/opt/sfw/lib/libncurses.so.5=libncurses.so.5.2 s none SFWncur
>/opt/sfw/lib/libncurses.so.5.2 f none 0755 root bin 344276 27898 1017237016 SFWncur
>/opt/sfw/lib/libncurses_g.a f none 0444 root bin 3473716 48101 1017237016 SFWncur
>/opt/sfw/man/man3/ncurses.3x f none 0444 bin bin 34621 13902 1017237008 SFWncur
>
>
>I've never need to know it's there - everything seems to be compiled
>correctly to find it themselves.
>
>Gavin
>


Here's what I get when giving the same grep-cmd:


YOURS: home-u60:~> grep ncurses /var/sadm/install/contents



588 ==/dkcjunk==> grep ncurses /var/sadm/install/contents
/opt/sfw/kde/share/apps/quanta/tags/php/ncurses.tag f none 0444 root bin 15390 26791 1062881266 SFWkde
589 ==/dkcjunk==> file /opt/sfw/kde/share/apps/quanta/tags/php/ncurses.tag
/opt/sfw/kde/share/apps/quanta/tags/php/ncurses.tag: ascii text
590 ==/dkcjunk==> wc !$
wc /opt/sfw/kde/share/apps/quanta/tags/php/ncurses.tag
356 1066 15390 /opt/sfw/kde/share/apps/quanta/tags/php/ncurses.tag
591 ==/dkcjunk==>


Suggestions?

David

David Combs wrote:

> Suggestions?

Install SFWncur from the companion CD (the same CD you used
to install the other /sfw packages)

In comp.mail.mutt Thomas Glanzmann <sithglan@stud.uni-erlangen.de> wrote:

> There is also a working mutt version available which is linked against
> slang which is better to work with.

I recall asking for an example to substantiate this remark before,
but saw none.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Hi Thomas,

* Thomas Dickey <dickey@saltmine.radix.net>:
> I recall asking for an example to substantiate this remark before,
> but saw none.

I often use xoverlay to look at videoes/tv. However I usually put a
xtern with the xoverlay color on top of mplayer to be able to work while
I keep watching whatever. Usually I have a light background while
watching tv/video I have a dark background. However to be able to work
with the xoverlay stuff the background of my application always has to
be the 'default' background color of the xterm.

It isn't possible to obtain that with ncurses, but with slang.

(faui03) [~] cat .mutt/colors
# colors
color normal default default
color attachment red default
color hdrdefault cyan default
color indicator default cyan
color markers green default
color quoted green default
color signature cyan default
color status brightgreen blue
color tilde blue default
color tree red default

color header red default ^From:
color header red default ^Date:
color header red default ^To:
color header red default ^Reply-To:
color header red default ^Cc:
color header red default ^Subject:

color body blue default [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+
color body blue default (https?|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+
color body red default ^[+-].*
color body blue default ^[-].*

color index red default "~N"

note the default entry. So it is possible to read text on bright and
dark backgrounds while also be able use the xoverlay trick at demand.

Apart from that I remember only one benefit (a bug in ncurses which
doesn't trigger in slang, but I don't remeber the details). However the
feature described above is vital for me!

Thomas

In comp.mail.mutt Thomas Glanzmann <sithglan@stud.uni-erlangen.de> wrote:
> Hi Thomas,

> * Thomas Dickey <dickey@saltmine.radix.net>:
>> I recall asking for an example to substantiate this remark before,
>> but saw none.

> I often use xoverlay to look at videoes/tv. However I usually put a
> xtern with the xoverlay color on top of mplayer to be able to work while
> I keep watching whatever. Usually I have a light background while
> watching tv/video I have a dark background. However to be able to work
> with the xoverlay stuff the background of my application always has to
> be the 'default' background color of the xterm.

> It isn't possible to obtain that with ncurses, but with slang.

hmm - no. ncurses and slang are equivalent in their capabilities here.
For ncurses, it is activated by function calls, e.g., use_default_colors.

You're either describing a difference in the way mutt is coded, or some
other configuration issue. Just checking, for example (with lynx where
those aren't a factor, I see the so-called transparency, while Debian's
mutt 1.5.4i with libncursesw doesn't).

Looking a little further (compiling 1.5.6 myself), I do indeed get the
transparency. Perhaps you should file a bug report against the appropriate
package - whatever problem is actually there isn't in the original sources.

> Apart from that I remember only one benefit (a bug in ncurses which
> doesn't trigger in slang, but I don't remeber the details). However the
> feature described above is vital for me!

> Thomas

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Hi,

> hmm - no. ncurses and slang are equivalent in their capabilities
> here. For ncurses, it is activated by function calls, e.g.,
> use_default_colors.

I didn't dive that deep into ncurses / slang to know, but it makes
sense of course.

> You're either describing a difference in the way mutt is coded, or
> some other configuration issue. Just checking, for example (with lynx
> where those aren't a factor, I see the so-called transparency, while
> Debian's mutt 1.5.4i with libncursesw doesn't).

If I use a ncurses enabled mutt. He doesn't know about the 'default' -
color I described earlier in that thread, while a slang enabled mutt
does. So I never really cared.

> Looking a little further (compiling 1.5.6 myself), I do indeed get the
> transparency. Perhaps you should file a bug report against the
> appropriate package - whatever problem is actually there isn't in the
> original sources.

Was it possible for you to get the transparency with ncurses and mutt?
If this is true for you, how?

When I compile mutt from cvs against the most recent version of ncurses.
I get the following errors on startup and after that I have default
colors for the 'default' stuff:

(faui03) [~/work/mutt/mutt] ./mutt
Error in /home/cip/adm/sithglan/.mutt/colors, line 2: default: no such color
....
Error in /home/cip/adm/sithglan/.mutt/colors, line 25: default: no such color
Error in /home/cip/adm/sithglan/.muttrc, line 10: source: errors in /home/cip/adm/sithglan/.mutt/colors
source: errors in /home/cip/adm/sithglan/.muttrc

However I will bring this to mutt-dev.

Thomas