Re: Seeking help

2000-06-13 Thread Thomas Dickey

On Tue, Jun 13, 2000 at 08:26:35AM +0200, Kasopa Wilbroad Chisanga wrote:
 
 I am running hp-ux 10.20 on my hp box and I would like to install mutt, but
 the following are the error messages I have got. How can I go round it as I
 desperately want to install this software. Thanking you in advance
 Regards, Wilbroad.
 
 keymap.c:69: `KEY_END' undeclared here (not in a function)

This is what stopped the build - HP has a different flavor of cursess
which should define this (curs_colr), but mutt's configure script
doesn't recognize that (doesn't generate -I and -L options for the
makefile to make it use the newer library).

-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://dickey.his.com
ftp://dickey.his.com



Re: Seeking help

2000-06-13 Thread Lars Hecking


  keymap.c:69: `KEY_END' undeclared here (not in a function)
 
 This is what stopped the build - HP has a different flavor of cursess
 which should define this (curs_colr), but mutt's configure script
 doesn't recognize that (doesn't generate -I and -L options for the
 makefile to make it use the newer library).

 The only HP-UX 10.20 box I have access to has no man pages, and
 a compiler that truely sucks (no -g, no ansi). I cannot install
 anything on this machine.

 Which means that someone else will have to look into this ...




Re: Seeking help

2000-06-13 Thread Kasopa Wilbroad Chisanga

Hello Thomas,

Does your explanation mean that I can not install it on the hp-ux?

Wilbroad.

- Original Message -
From: "Thomas Dickey" [EMAIL PROTECTED]
To: "Kasopa Wilbroad Chisanga" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, June 13, 2000 11:08 AM
Subject: Re: Seeking help


 On Tue, Jun 13, 2000 at 08:26:35AM +0200, Kasopa Wilbroad Chisanga wrote:

  I am running hp-ux 10.20 on my hp box and I would like to install mutt,
but
  the following are the error messages I have got. How can I go round it
as I
  desperately want to install this software. Thanking you in advance
  Regards, Wilbroad.
 
  keymap.c:69: `KEY_END' undeclared here (not in a function)

 This is what stopped the build - HP has a different flavor of cursess
 which should define this (curs_colr), but mutt's configure script
 doesn't recognize that (doesn't generate -I and -L options for the
 makefile to make it use the newer library).

 --
 Thomas E. Dickey [EMAIL PROTECTED]
 http://dickey.his.com
 ftp://dickey.his.com





Re: Seeking help

2000-06-13 Thread Thomas Dickey

On Tue, Jun 13, 2000 at 10:38:32AM +0100, Lars Hecking wrote:
 
   keymap.c:69: `KEY_END' undeclared here (not in a function)
  
  This is what stopped the build - HP has a different flavor of cursess
  which should define this (curs_colr), but mutt's configure script
  doesn't recognize that (doesn't generate -I and -L options for the
  makefile to make it use the newer library).
 
  The only HP-UX 10.20 box I have access to has no man pages, and
  a compiler that truely sucks (no -g, no ansi). I cannot install
  anything on this machine.

I have a few scraps, from tin and lynx (my configure script usually works
for this case, though I get occasional reports of problems).

-- 
Thomas E. Dickey [EMAIL PROTECTED]
http://dickey.his.com
ftp://dickey.his.com



Re: Seeking help

2000-06-13 Thread Charles Curley

On Tue, Jun 13, 2000 at 10:38:32AM +0100, Lars Hecking wrote:
- 
-   keymap.c:69: `KEY_END' undeclared here (not in a function)
-  
-  This is what stopped the build - HP has a different flavor of cursess
-  which should define this (curs_colr), but mutt's configure script
-  doesn't recognize that (doesn't generate -I and -L options for the
-  makefile to make it use the newer library).
- 
-  The only HP-UX 10.20 box I have access to has no man pages, and
-  a compiler that truely sucks (no -g, no ansi). I cannot install
-  anything on this machine.
- 
-  Which means that someone else will have to look into this ...

You can pay HP for an ANSI HP-UX 10.20 compiler, possibly upgrade to a
later version of HP-UX which may have an ANSI compiler, or you can get gcc
for HP-UX at the usual location and usual price. It should compile
painlessly even on 10.20's KR compiler.

-- 

-- C^2

No windows were crashed in the making of this email.

Looking for fine software and/or web pages?
http://w3.trib.com/~ccurley



Re: Seeking help

2000-06-13 Thread Lars Hecking


 -  The only HP-UX 10.20 box I have access to has no man pages, and
 -  a compiler that truely sucks (no -g, no ansi). I cannot install
 -  anything on this machine.
 - 
 -  Which means that someone else will have to look into this ...
 
 You can pay HP for an ANSI HP-UX 10.20 compiler, possibly upgrade to a
 later version of HP-UX which may have an ANSI compiler, or you can get gcc
 for HP-UX at the usual location and usual price.

 *I* can't. I have none of these options, the machine is not under
 my authoritah.

  It should compile
 painlessly even on 10.20's KR compiler.




Re: Seeking help

2000-06-13 Thread Thomas E. Dickey

On Tue, 13 Jun 2000, Lars Hecking wrote:

 
  -  The only HP-UX 10.20 box I have access to has no man pages, and
  -  a compiler that truely sucks (no -g, no ansi). I cannot install
  -  anything on this machine.
  - 
  -  Which means that someone else will have to look into this ...
  
  You can pay HP for an ANSI HP-UX 10.20 compiler, possibly upgrade to a
  later version of HP-UX which may have an ANSI compiler, or you can get gcc
  for HP-UX at the usual location and usual price.
 
  *I* can't. I have none of these options, the machine is not under
  my authoritah.

as I pointed out, there are configure macros which I've written for tin
and lynx which check for the HP curses library.  It wouldn't be that
hard to incorporate those into mutt's configure script...

(I don't have an HPUX 10.x either) 

-- 
T.E.Dickey [EMAIL PROTECTED]
http://dickey.his.com
ftp://dickey.his.com




Re: Seeking help

2000-06-13 Thread Lars Hecking


 as I pointed out, there are configure macros which I've written for tin
 and lynx which check for the HP curses library.  It wouldn't be that
 hard to incorporate those into mutt's configure script...

 The cur_colr stuff ... ok, I'll see what I can do :)




Re: Seeking help

2000-06-13 Thread Gary Johnson

I compiled earlier versions of mutt (= 1.0) on HP-UX 10.20 by hacking
the Makefile to get it to use the HP-UX color curses.  I also had to use
GNU make.  The same hack would not work for mutt 1.2, so I installed
slang.  That worked fine.  I don't need GNU make anymore, either, since
that problem in mutt's Makefiles was fixed.  I have always used gcc to
compile it.

Gary

-- 
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | RF Communications Product Generation Unit
 | Spokane, Washington, USA



Re: Seeking help

2000-06-13 Thread Benjamin Korvemaker

On Tue, Jun 13, 2000 at 10:38:32AM +0100, Lars Hecking wrote:
 
   keymap.c:69: `KEY_END' undeclared here (not in a function)
  
  This is what stopped the build - HP has a different flavor of cursess
  which should define this (curs_colr), but mutt's configure script
  doesn't recognize that (doesn't generate -I and -L options for the
  makefile to make it use the newer library).
 
  The only HP-UX 10.20 box I have access to has no man pages, and
  a compiler that truely sucks (no -g, no ansi). I cannot install
  anything on this machine.
 
  Which means that someone else will have to look into this ...

My sympathy... Back when I last worked on an HP box, life
was more dismal. (HP-UX v.OLD compiler didn't even want to
compile g++) I heard rumors the compiler was intended for
recompiling the kernel only.

If you are allowed (this is important!) to install a version
of gcc into your own space (and your space is big enough),
then you can use gcc.

simplified steps:
 1. install gcc to $HOME/tmp/gcc
 2. install mutt (with CC=$HOME/tmp/gcc)
 3. delete $HOME/tmp/gcc [*]
 4. use mutt

[*] optionally, install gcc and keep it, and stay saner.

That said, if you spend much time working on your HP-UX box,
I suggest you ask the admins for a better compiler.

Ben
-- 
Benjamin Korvemaker
[EMAIL PROTECTED]



Patch for better curses detection [was: Re: Seeking help]

2000-06-13 Thread Lars Hecking


 This is what stopped the build - HP has a different flavor of curses
 which should define this (curs_colr), but mutt's configure script
 doesn't recognize that (doesn't generate -I and -L options for the
 makefile to make it use the newer library).

 Try this patch. It's relative to mutt-cvs, but should work with 1.3.x,
 maybe even 1.2.x. Minor ugliness (?): I haven't changed the macro, so
 it uses LIBS instead of MUTTLIBS.

 Autogenerated files are not included, so you need the environment
 described in doc/devel-notes.txt, especially autoconf and automake.

 I hope I managed not to break anything :-)

 If this works, thank T.E.D :-))

diff -urN mutt-cvs/ChangeLog mutt-1.3.3/ChangeLog
--- mutt-cvs/ChangeLog  Sat Jun 10 06:30:29 2000
+++ mutt-1.3.3/ChangeLogTue Jun 13 20:17:01 2000
@@ -1,3 +1,11 @@
+2000-06-13  Lars Hecking  [EMAIL PROTECTED]
+
+   * configure.in: Use CF_CURSES_LIBS macro for better detection
+   of platform-specific curses libraries.
+
+   * m4/curslib.m4: New file, contains Tom Dickey's CF_CURSES_LIBS
+   macro from lynx.
+
 Fri Jun  9 11:34:26 2000  Thomas Roessler  [EMAIL PROTECTED]
 
* po/ru.po, po/sk.po, po/sv.po, po/uk.po, po/zh_TW.Big5.po,
diff -urN mutt-cvs/configure.in mutt-1.3.3/configure.in
--- mutt-cvs/configure.in   Tue Jun 13 06:30:17 2000
+++ mutt-1.3.3/configure.in Tue Jun 13 20:08:45 2000
@@ -183,7 +183,7 @@
fi
AC_CHECK_HEADERS(ncurses.h)],
 
-   [MUTTLIBS="$MUTTLIBS -lcurses"])
+   [CF_CURSES_LIBS])
 
old_LIBS="$LIBS"
LIBS="$LIBS $MUTTLIBS"
diff -urN mutt-cvs/m4/curslib.m4 mutt-1.3.3/m4/curslib.m4
--- mutt-cvs/m4/curslib.m4  Thu Jan  1 01:00:00 1970
+++ mutt-1.3.3/m4/curslib.m4Tue Jun 13 16:43:47 2000
@@ -0,0 +1,83 @@
+dnl ---
+dnl Look for the curses libraries.  Older curses implementations may require
+dnl termcap/termlib to be linked as well.
+AC_DEFUN([CF_CURSES_LIBS],[
+AC_CHECK_FUNC(initscr,,[
+case $host_os in #(vi
+freebsd*) #(vi
+   AC_CHECK_LIB(mytinfo,tgoto,[LIBS="-lmytinfo $LIBS"])
+   ;;
+hpux10.*|hpux11.*)
+   AC_CHECK_LIB(cur_colr,initscr,[
+   LIBS="-lcur_colr $LIBS"
+   CFLAGS="-I/usr/include/curses_colr $CFLAGS"
+   ac_cv_func_initscr=yes
+   ],[
+   AC_CHECK_LIB(Hcurses,initscr,[
+   # HP's header uses __HP_CURSES, but user claims _HP_CURSES.
+   LIBS="-lHcurses $LIBS"
+   CFLAGS="-D__HP_CURSES -D_HP_CURSES $CFLAGS"
+   ac_cv_func_initscr=yes
+   ])])
+   ;;
+linux*) # Suse Linux does not follow /usr/lib convention
+   LIBS="$LIBS -L/lib"
+   ;;
+esac
+
+if test ".$With5lib" != ".no" ; then
+if test -d /usr/5lib ; then
+   # SunOS 3.x or 4.x
+   CPPFLAGS="$CPPFLAGS -I/usr/5include"
+   LIBS="$LIBS -L/usr/5lib"
+fi
+fi
+
+if test ".$ac_cv_func_initscr" != .yes ; then
+   cf_save_LIBS="$LIBS"
+   cf_term_lib=""
+   cf_curs_lib=""
+
+   # Check for library containing tgoto.  Do this before curses library
+   # because it may be needed to link the test-case for initscr.
+   AC_CHECK_FUNC(tgoto,[cf_term_lib=predefined],[
+   for cf_term_lib in termcap termlib unknown
+   do
+   AC_CHECK_LIB($cf_term_lib,tgoto,[break])
+   done
+   ])
+
+   # Check for library containing initscr
+   test "$cf_term_lib" != predefined  test "$cf_term_lib" != unknown  
+LIBS="-l$cf_term_lib $cf_save_LIBS"
+   for cf_curs_lib in cursesX curses ncurses xcurses jcurses unknown
+   do
+   AC_CHECK_LIB($cf_curs_lib,initscr,[break])
+   done
+   test $cf_curs_lib = unknown  AC_ERROR(no curses library found)
+
+   LIBS="-l$cf_curs_lib $cf_save_LIBS"
+   if test "$cf_term_lib" = unknown ; then
+   AC_MSG_CHECKING(if we can link with $cf_curs_lib library)
+   AC_TRY_LINK([#include ${cf_cv_ncurses_header-curses.h}],
+   [initscr()],
+   [cf_result=yes],
+   [cf_result=no])
+   AC_MSG_RESULT($cf_result)
+   test $cf_result = no  AC_ERROR(Cannot link curses library)
+   elif test "$cf_term_lib" != predefined ; then
+   AC_MSG_CHECKING(if we need both $cf_curs_lib and $cf_term_lib 
+libraries)
+   AC_TRY_LINK([#include ${cf_cv_ncurses_header-curses.h}],
+   [initscr(); tgoto((char *)0, 0, 0);],
+   [cf_result=no],
+   [
+   LIBS="-l$cf_curs_lib -l$cf_term_lib $cf_save_LIBS"
+   AC_TRY_LINK([#include ${cf_cv_ncurses_header-curses.h}],
+   [initscr()],
+   [cf_result=yes],
+   [cf_result=error])
+