From: adrian.freihofer@gmail.com
To: hongxu.jia@windriver.com,
openembedded-core@lists.openembedded.org,
mathieu.dubois-briand@bootlin.com
Subject: Re: [OE-core] [PATCH v7 1/6] distro/include: rework debug friendly optimization
Date: Mon, 05 Jan 2026 22:30:13 +0100 [thread overview]
Message-ID: <8de5abb6a9506f76032d2427e8a3d62a1e18ed23.camel@gmail.com> (raw)
In-Reply-To: <20251222145403.3688113-1-hongxu.jia@windriver.com>
Hi Hongxu, hi Mathieu
I guess this series is not complete. If I do a git grep on today's
master-next branch with this series applied:
openembedded-core$ git grep DEBUG_BUILD
scripts/lib/devtool/ide_sdk.py:
self.debug_build = recipe_d.getVar('DEBUG_BUILD')
scripts/lib/devtool/ide_sdk.py:
'You might want to add DEBUG_BUILD = "1" to %s. '
scripts/lib/devtool/standard.py:
f.write('DEBUG_BUILD = "1"\n')
scripts/lib/devtool/standard.py:
parser_modify.add_argument('--debug-build', action="store_true",
help='Add DEBUG_BUILD = "1" to the modified recipe')
This breaks the patch from
https://lists.openembedded.org/g/openembedded-core/message/228633
which tries to add a test for remote debugging.
The issue looks like this:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3070
Breaking scripts/lib/devtool/standard.py:
f.write('DEBUG_BUILD = "1"\n')
is at least an explanation for this issue. Since TDEBUG_BUILD = "1" is
now without any effect, the compiler removes the code where the test
adds the break point.
@Mathieu: would you mind
- dropping this series from your master-next branch until this is fixed
- bring the patch from my v1 series back?
(v2 seams to be worse than v1)
https://patchwork.yoctoproject.org/project/oe-core/patch/20251230084720.2371227-14-adrian.freihofer@siemens.com/
Of course, I can also send a v3 if this would be easier for you.
Thank you.
Regards,
Adrian
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#228304):
> https://lists.openembedded.org/g/openembedded-core/message/228304
> Mute This Topic: https://lists.openembedded.org/mt/116902148/4454582
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-core/unsub [
> adrian.freihofer@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2026-01-05 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 14:53 [PATCH v7 1/6] distro/include: rework debug friendly optimization Hongxu Jia
2025-12-22 14:53 ` [PATCH v7 2/6] debug-optimize.inc: collect debug optimization tuning configuration Hongxu Jia
2025-12-22 14:54 ` [PATCH v7 3/6] debug-optimize.inc: override MESON_BUILDTYPE for target Hongxu Jia
2025-12-22 14:54 ` [PATCH v7 4/6] debug-optimize.inc: override CARGO_BUILD_MODE and CARGO_BUILD_DIR " Hongxu Jia
2025-12-22 14:54 ` [PATCH v7 5/6] Clean up compiler optimization variable FULL_OPTIMIZATION Hongxu Jia
2025-12-22 14:54 ` [PATCH v7 6/6] Clean up compiler optimization variable DEBUG_OPTIMIZATION Hongxu Jia
2026-01-05 21:30 ` adrian.freihofer [this message]
2026-01-06 4:54 ` [PATCH] devtool: clean up debug build Hongxu Jia
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=8de5abb6a9506f76032d2427e8a3d62a1e18ed23.camel@gmail.com \
--to=adrian.freihofer@gmail.com \
--cc=hongxu.jia@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.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