From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH V2] package: gdb: Add helping kernel gdb functions compilation
Date: Wed, 13 Dec 2023 21:24:16 +0100 [thread overview]
Message-ID: <20231213212416.642d5dab@windsurf> (raw)
In-Reply-To: <CAOf5uw=zfi=zOPh=K-kaT5MmScBxqod3okjxtnK600qn4_sZpA@mail.gmail.com>
On Wed, 13 Dec 2023 21:17:34 +0100
Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:
> My V1 was addressing your concern?
No, your v1 was just adding a Buildroot option that allows to enable a
kernel option. This is useless, as you can simply enable the kernel
option in question, and it doesn't make any sense for Buildroot to
replicate 1:1 each kernel option as a Buildroot option. It only makes
sense to do so when enabling the kernel option requires that Buildroot
builds additional host tools/libraries. But for something as simple as
enabling CONFIG_GDB_SCRIPTS, just enable it in your kernel config.
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
next prev parent reply other threads:[~2023-12-13 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 21:49 [Buildroot] [PATCH V2] package: gdb: Add helping kernel gdb functions compilation Michael Trimarchi
2023-12-13 20:08 ` Thomas Petazzoni via buildroot
2023-12-13 20:17 ` Michael Nazzareno Trimarchi
2023-12-13 20:24 ` Thomas Petazzoni via buildroot [this message]
2023-12-13 20:32 ` Michael Nazzareno Trimarchi
2023-12-13 20:41 ` Yann E. MORIN
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=20231213212416.642d5dab@windsurf \
--to=buildroot@buildroot.org \
--cc=michael@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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