From: Paul Smith <psmith@gnu.org>
To: gdb@sourceware.org
Subject: Re: Building gdb without ncursesw?
Date: Mon, 19 Oct 2020 10:56:17 -0400 [thread overview]
Message-ID: <69cd93ba5f8d0049cea98dfad396cb4ed3071afc.camel@gnu.org> (raw)
In-Reply-To: <9e754414-577e-f279-6418-b675b0c124ac@simark.ca>
On Mon, 2020-10-19 at 10:21 -0400, Simon Marchi wrote:
> On 2020-10-17 6:22 p.m., Paul Smith via Gdb wrote:
> > On Sat, 2020-10-17 at 14:35 -0400, Paul Smith via Gdb wrote:
> > > There's really no need (that I can see) for ncursesw since we
> > > just always uses utf8 all the time for everything.
>
> Looking at configure.ac, the library is chosen using this line:
>
> AC_SEARCH_LIBS(waddstr, [ncursesw ncurses cursesX curses])
>
> Then, looking at my config.cache, I see this line:
>
> ac_cv_search_waddstr=${ac_cv_search_waddstr=-lncursesw}
>
> So I suppose that if you pass ac_cv_search_waddstr=-lncurses to
> configure, it will just use that instead of probing.
Seems a bit dodgy. Also, there are other places where ncursesw is
checked before ncurses:
AC_SEARCH_LIBS(tgetent, [termcap tinfow tinfo curses ncursesw ncurses])
...
AC_CHECK_HEADERS(curses.h cursesX.h ncurses.h ncursesw/ncurses.h ncurses/ncurses.h ncurses/term.h)
For my system luckily I don't need tgetent. And, I'm not 100% sure if
the HAVE_NCURSESW_* config options will be set properly in this
situation.
It would be nice if there were a configure option to either ignore
ncursesw, or else to specifically set the library and headers location.
Oh well, I will hack at it; thanks!
prev parent reply other threads:[~2020-10-19 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 18:35 Paul Smith
2020-10-17 22:22 ` Paul Smith
2020-10-19 14:21 ` Simon Marchi
2020-10-19 14:56 ` Paul Smith [this message]
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=69cd93ba5f8d0049cea98dfad396cb4ed3071afc.camel@gnu.org \
--to=psmith@gnu.org \
--cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).