From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/gdb: really fix build with GCC 15.x by using external readline
Date: Sun, 24 Aug 2025 15:41:39 +0200 [thread overview]
Message-ID: <20250824154139.56786f08@windsurf> (raw)
In-Reply-To: <ced67667-9a6e-4d76-a715-0f13cf31b4d7@smile.fr>
On Sun, 24 Aug 2025 15:38:01 +0200
Romain Naour <romain.naour@smile.fr> wrote:
> I'm agree on the principle but what about gdb TUI option (BR2_PACKAGE_GDB_TUI)?
> gdb TUI seems really requires ncurses [1].
>
> ncurses package should be selected by gdb TUI.
Note that our readline package does select ncurses. However, if GDB's
tui uses ncurses directly, then we should also have a "select
BR2_PACKAGE_NCURSES" for this option.
Indeed, readline can potentially *not* use ncurses: it can use the
termcap library instead of ncurses. This is not the choice we've made
in Buildroot, but it's a possible option.
I'll rework the patch accordingly.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-08-24 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 21:22 [Buildroot] [PATCH] package/gdb: really fix build with GCC 15.x by using external readline Thomas Petazzoni via buildroot
2025-08-24 13:38 ` Romain Naour via buildroot
2025-08-24 13:41 ` Thomas Petazzoni via buildroot [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=20250824154139.56786f08@windsurf \
--to=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.