From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
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:41:36 +0100 [thread overview]
Message-ID: <ZXoXAGjMvtSoahwd@landeda> (raw)
In-Reply-To: <CAOf5uwkdWm8kWZT2y_ZHO9H26hUri9jZgYHj37ah1VjhNm4LmQ@mail.gmail.com>
Micheal, All,
On 2023-12-13 21:32 +0100, Michael Nazzareno Trimarchi spake thusly:
> Il mer 13 dic 2023, 21:24 Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ha scritto:
> > 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.
> I don't think that I enable any option and I just run an other kernel
> target. Yes but definitely I understand your point. My idea was to keeps
> some tools build as option as the serial proxy.
Thomas' point is pretty fair, in fact, and it should have hit me as well
when I reviewed v1: if one wants to do kernel debugging, they should be
responsible for enabling all appropriate options in their kernel. One
such option will have this script installed.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-13 20:41 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
2023-12-13 20:32 ` Michael Nazzareno Trimarchi
2023-12-13 20:41 ` Yann E. MORIN [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=ZXoXAGjMvtSoahwd@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=michael@amarulasolutions.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox