From: Eli Zaretskii <eliz@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] configure check for curses library
Date: Sun, 16 May 2004 05:43:00 -0000 [thread overview]
Message-ID: <ubrkoooon.fsf@gnu.org> (raw)
In-Reply-To: <20040516051748.GG566@tausq.org>
> Date: Sat, 15 May 2004 22:17:48 -0700
> From: Randolph Chung <randolph@tausq.org>
>
> on this particular HPUX system where i'm doing the gdb build,
> there are both ncurses headers and native HPUX curses headers. The
> include search path for GCC is such that the build
> picks up the ncurses curses.h header which does the wattron() ->
> wattr_on() translation. :-(
>
> so i guess my fix is not really correct; we should make configure use
> the correct header. But how?
Your idea might still be correct, if we could find a symbol that isn't
in termcap library (nor in any other library) and isn't converted by
some preprocessor macro.
next prev parent reply other threads:[~2004-05-16 5:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 18:01 Randolph Chung
2004-05-16 5:02 ` Eli Zaretskii
2004-05-16 5:17 ` Randolph Chung
2004-05-16 5:43 ` Eli Zaretskii [this message]
2004-05-16 6:09 ` Randolph Chung
2004-05-16 8:06 Michael Elizabeth Chastain
2004-05-16 10:29 ` Eli Zaretskii
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=ubrkoooon.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox