From: Paul Smith <psmith@gnu.org>
To: gdb@sourceware.org
Subject: Building gdb without ncursesw?
Date: Sat, 17 Oct 2020 14:35:44 -0400 [thread overview]
Message-ID: <fce3cd418084779b786395aceefd4a8f68de6cf1.camel@gnu.org> (raw)
Hi all;
Is there a way to force gdb to build against ncurses, not ncursesw,
even if ncursesw headers/libraries do exist on the system?
The problem with ncursesw is that not all distributions put it onto the
system by default (everyone has ncurses by default) so if I compile GDB
against ncursesw then I have to get everyone to install extra packages.
There's really no need (that I can see) for ncursesw since we just
always uses utf8 all the time for everything.
But, I can't find any configure option or even cache setting I can use
to force the use of ncurses.
Cheers!
next reply other threads:[~2020-10-17 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 18:35 Paul Smith [this message]
2020-10-17 22:22 ` Paul Smith
2020-10-19 14:21 ` Simon Marchi
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=fce3cd418084779b786395aceefd4a8f68de6cf1.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).