All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Ziegler <br025@umbiko.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/mpd: implement BR2_ENABLE_RUNTIME_DEBUG
Date: Sun, 25 Oct 2026 19:00:49 +0100	[thread overview]
Message-ID: <at5DqzNZnCORf3pF@windsurf> (raw)
In-Reply-To: <20261025104130.1580635-1-br025@umbiko.net>

On Sun, Oct 25, 2026 at 11:41:28AM +0100, Andreas Ziegler wrote:
> MPD started during version 0.19 (2015) to insert runtime debug
> statements into the codebase. These are enclosed in preprocessor
> instructions:
> 
>   #ifndef NDEBUG
>   #endif
> 
> Fix the MPD build to observe the BR2_ENABLE_RUNTIME_DEBUG option. 
> 
> Signed-off-by: Andreas Ziegler <br025@umbiko.net>

Series applied, thanks! To be honest, I wasn't quite sure about PATCH
1/2, because I couldn't find any documentation about this NDEBUG
define, but I assume you're familiar with the mpd code base :-)

Best regards,

Thomas Petazzoni
-- 
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

  parent reply	other threads:[~2026-10-25 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-25 10:41 [Buildroot] [PATCH 1/2] package/mpd: implement BR2_ENABLE_RUNTIME_DEBUG Andreas Ziegler
2026-10-25 10:41 ` [Buildroot] [PATCH 2/2] package/mpd: update version to 0.24.17 Andreas Ziegler
2026-10-25 18:00 ` Thomas Petazzoni via buildroot [this message]
2026-10-26  3:43   ` [Buildroot] [PATCH 1/2] package/mpd: implement BR2_ENABLE_RUNTIME_DEBUG Andreas Ziegler

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=at5DqzNZnCORf3pF@windsurf \
    --to=buildroot@buildroot.org \
    --cc=br025@umbiko.net \
    --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.