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

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

> 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.

well, I do look. iirc, mutt's use of default colors was done first with
ncurses. Some people use that. I originally came up with the idea since
it was a good way to make my directory editor work (it uses curses to
manage only part of the screen). So I do use the feature often, but not
in the context of mutt.

>> 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?

I suspect there is a defect in the package. Many packages do not run the
configure script, but provide specific ifdef's. It is also possible that
the system on which a configure script could have some other problems.

If it hadn't worked out-of-the-box, I would have looked further, to see
what the problem was. Mutt's configure script is a little weak in detecting
conflicts - this is aggravated on Solaris by the sunfreeware package, which
puts ncurses conflicting with Sun's curses.

> 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:

I have local copies of the sources for the interesting releases of mutt
(since I occasionally have some reason to test it). So I just unpacked
the most recent one and built it. My Debian has 1.5.4; I built 1.5.6.
That might be a factor.

> (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

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

Hi,

> I have local copies of the sources for the interesting releases of mutt
> (since I occasionally have some reason to test it). So I just unpacked
> the most recent one and built it. My Debian has 1.5.4; I built 1.5.6.
> That might be a factor.

you're totally right. It works just like a charm for me under Debian,
too.

Thomas

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

>> I have local copies of the sources for the interesting releases of mutt
>> (since I occasionally have some reason to test it). So I just unpacked
>> the most recent one and built it. My Debian has 1.5.4; I built 1.5.6.
>> That might be a factor.

> you're totally right. It works just like a charm for me under Debian,
> too.

For Solaris, I occasionally do test-compiles (on this host for instance,
which has the sunfreeware package installed). I use a script for setting
up this, e.g.,

cfg-curses is

#!/bin/sh
# work-around broken sfw package for ncurses, as well as Sun's broken headers.
CPPFLAGS="-I/usr/include \
-D_XOPEN_SOURCE=500 \
-D_XOPEN_VERSION=4" \
CC=cc-curses cfg-normal $*

cc-curses is

#!/bin/sh
cc \
-D_XOPEN_SOURCE=500 \
-D_XOPEN_VERSION=4 \
-I/usr/include $* -L/usr/lib -lcurses

and cf-normal is

#!/bin/sh
OUT=configure.out
cat >>$OUT <<EOF/
** `date`
** node: `hostname`
** user: `id`
** conf: $*
EOF/
rm -f config.status config.cache
../configure --verbose \
--disable-echo \
--disable-overwrite \
--enable-warnings \
--with-warnings \
--prefix=$HOME \
--exec-prefix=$HOME $* 2>&1 | tee -a $OUT

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

In article <pan.2004.04.08.16.33.16.599962@yahoo.com>,
Dave Uhring <daveuhring@yahoo.com> wrote:
>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
>

Thanks to whoever, about a week ago, posted here or emailed me,
I forget which, that there was an ncurses right there on
the solaris-9 (12/3) companion-cd -- and indeed there is!

SFWWncur is its name.

pkgadd on it, and vim, lynx, etc all work just fine!


But you have to add it by-hand -- at least none of the
"clusters" (eg "desktop applications", "editors", ...) that
*I* installed from that cd included it -- which is of course
a mistake.



FINAL QUESTION: who's the guy who builds that CD? And, how
to get to him/her, to tell about this, so they can
include it in the depends next time?



And thanks for all the feedback you gave!

David

PS: well, one more: what's the "W" stand for, in
"SUNWxyz...", "SFCWabc", etc?

On Tue, 13 Apr 2004 20:33:20 +0000, David Combs wrote:

>
> PS: well, one more: what's the "W" stand for, in
> "SUNWxyz...", "SFCWabc", etc?

SUNW is the stock exchange symbol for Sun Microsystems, Inc.

In article <pan.2004.04.14.00.57.59.481225@yahoo.com>,
Dave Uhring <daveuhring@yahoo.com> wrote:
>
>SUNW is the stock exchange symbol for Sun Microsystems, Inc.

I didn't know.

If I'd had any brains 15, 20 years ago -- well, I'd sure
have known what SUNW meant, and I'd be a rich man, too!

Cheers

DaVid

Maybe I already said this, but it turns out that
that .so file *is* on the companion-cd, but not
included in any of the clusters that I installed (and
that was most of them).

I think the lower-case part of the package name is or
contains "ncur". Just pkgadd it, and all works fine!

(Was it someone from here who emailed me to do that?
If so, thanks!)

David