unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Casper Gripenberg <casper.gripenberg@kotiportti.fi>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Crash in tparam.c on OpenBSD
Date: Fri, 2 Jan 2004 15:43:35 +0200	[thread overview]
Message-ID: <20040102134335.GA10658@zoidberg.homeip.net> (raw)
In-Reply-To: <7494-Fri02Jan2004112527+0200-eliz@elta.co.il>

On Fri, Jan 02, 2004 at 11:25:27AM +0200, Eli Zaretskii wrote:
> It means that your Emacs was compiled for termcap, but the TERM entry
> it gets fed is for terminfo, which is a newer method of specifying
> terminal capabilities.  Emacs as compiled on your machine cannot
> handle terminfo entries, so it barfs.
> 
> There should be an entry in the PROBLEMS file named "Emacs aborts
> inside the function `tparam1'" which tells you more, including
> suggested ways to solve this problem.

Thanks. You are correct about the location of the problem.
After a bit of wrestling back and forth with the source, and 
not really getting anywhere, I figured out to check the newer 
OBSD 3.4 ports tree. In there was 21.3 patched the following 
way:

$OpenBSD: patch-src_s_openbsd_h,v 1.1 2003/07/05 00:27:08 naddy Exp $
--- src/s/openbsd.h.orig        Wed Mar 22 13:08:18 2000
+++ src/s/openbsd.h     Fri Jun 27 01:17:51 2003
@@ -9,3 +9,8 @@
 /*  David Mazieres <dm@reeducation-labor.lcs.mit.edu> says this
     is necessary.  Otherwise Emacs dumps core when run -nw.  */
 #undef LIBS_TERMCAP
+
+/*  Idea From the FreeBSD port. Seems to work well.
+    Needs testing and then commiting to emacs developers */
+#define TERMINFO
+#define LIBS_TERMCAP -lncurses

Looks simple enough. Close to what I tried, but I was probably
editing the wrong files (manually patching config.h). 

Anyway the 3.4 port works beautifully. I get color in the
terminal too, which I did not get before. Happy now :)

Regards,
  Casper

  reply	other threads:[~2004-01-02 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 22:54 Crash in tparam.c on OpenBSD Casper Gripenberg
2004-01-02  9:25 ` Eli Zaretskii
2004-01-02 13:43   ` Casper Gripenberg [this message]
     [not found] ` <mailman.868.1073039641.868.bug-gnu-emacs@gnu.org>
2004-01-02 11:01   ` Thomas Dickey
2004-01-03 11:48     ` Eli Zaretskii
     [not found]     ` <mailman.897.1073134721.868.bug-gnu-emacs@gnu.org>
2004-01-04  2:25       ` Thomas Dickey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040102134335.GA10658@zoidberg.homeip.net \
    --to=casper.gripenberg@kotiportti.fi \
    --cc=bug-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).