public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: psmith@gnu.org, gdb@sourceware.org
Subject: Re: Building gdb without ncursesw?
Date: Mon, 19 Oct 2020 10:21:25 -0400	[thread overview]
Message-ID: <9e754414-577e-f279-6418-b675b0c124ac@simark.ca> (raw)
In-Reply-To: <395a06fee09377bfe6c03a6a761be6e02b9a538b.camel@gnu.org>

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.
>
> I should clarify that by this I mean, _I_ (and the folks I work with)
> have no need for it in our environment: I'm not suggesting everyone
> should use utf8 and no one has any need for ncursesw.

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.

Simon

  reply	other threads:[~2020-10-19 14:21 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 [this message]
2020-10-19 14:56     ` Paul Smith

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=9e754414-577e-f279-6418-b675b0c124ac@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb@sourceware.org \
    --cc=psmith@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.
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).