public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jean-Pierre Radley <jpr@jpr.com>
To: EGCS Developers <egcs@cygnus.com>
Subject: Re: mutt: slight problem
Date: Sun, 14 Dec 1997 19:41:00 -0000	[thread overview]
Message-ID: <19971214224105.51653@jpr.com> (raw)
In-Reply-To: <19971214133153.00315@dgii.com>

Robert Lipe telecommunicated (on 14Dec):
| > Mutt is my MUA; until today, I've been compiling it with Robert
| > Lipe's port of gcc for SCO OpenServer 5.
| 
| Thanx to you, Mutt is my MUA, too.   
| 
| > Having just now compiled and dejagnu-tested the 1.0 release of
| > egcs-gcc, the first program I tried to recompile was mutt
| 
| I'm on egcs 1127 and am likely to remain so for at least a few
| more days.
| 
| > All actions having to do with color or inverse video are
| > non-functional.  I'm using the same curses library under either
| > compilation.
| 
| Since I can't see this problem, we must be doing something 
| different.   My Mutt uses color and inverse video just fine
| and my screens look identical on either OpenServer or Linux.
| 
| Would you be using slang, ncurses, or the native curses?   I 
| use only native.

Native SCO curses library.

| For me, the generated config.h's for both "CC=/bin/cc -blf" configure"
| and "configure" are identical.   Are they for you?    I suppose the
| single most obvious place to look is for the entry:
| /* Does your curses library support color? */
| #define HAVE_COLOR 1

Yes, I have that too.

| Does config.log tell you anything you didn't already know?
 
Nope.

| 
| We can take it private if you like and just put the final solution 
| back on the list.      I'll send you my generated config.h suitable
| for diffing.

Which Robert did do, and the diffs were both trivial and unrelated to
terminals or colors.

-- 
Jean-Pierre Radley   jpr@jpr.com   XC/XT Custodian   Sysop, CompuServe SCOForum

  reply	other threads:[~1997-12-14 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-13 14:41 Jean-Pierre Radley
1997-12-14 11:32 ` Robert Lipe
1997-12-14 19:41   ` Jean-Pierre Radley [this message]
1997-12-14 20:14   ` Jean-Pierre Radley
1997-12-14 21:22     ` "helpful" include additions, was: " Robert Lipe
1997-12-15  3:41     ` local_prefix a mistake Andrew Fitzgibbon
1997-12-15  7:49       ` H.J. Lu
1997-12-15 11:43         ` Jean-Pierre Radley
1997-12-15  9:38       ` J. Kean Johnston
1997-12-16  8:45         ` Andrew Fitzgibbon

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

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

  git send-email \
    --in-reply-to=19971214224105.51653@jpr.com \
    --to=jpr@jpr.com \
    --cc=egcs@cygnus.com \
    /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.
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).