]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core.git/commit
bitbake.conf: remove DEBUG_PREFIX_MAP from TARGET_LDFLAGS
authorRandolph Sapp <rs@ti.com>
Thu, 22 Jan 2026 19:50:00 +0000 (13:50 -0600)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 29 Jan 2026 10:08:55 +0000 (10:08 +0000)
commit1797741aad02b8bf429fac4b81e30cdda64b5448
treef6a739a6c4bca25ca92c5614804b0900eee9699d
parentf0d8ff0bfbe9fdff794d4845bdde7122e8ef0e88
bitbake.conf: remove DEBUG_PREFIX_MAP from TARGET_LDFLAGS

Now that the previous bug affecting binary reproducibility has been
addressed [1], we can revert this patch. This will resolve issues with
cgo applications becoming unreprodcible.

Currently go considers link arguments to be sacred, meaning any change
should produce a different binary output. They ensure this by baking
link arguments into the intermediary output, changing the content ID of
that step. As such, the marco prefixes inadvertently end up adding build
paths to the output binary instead of removing them if they are passed
as link arguments to cgo applications.

These paths are later stripped out again, but at this point the content
ID of the dependency has changed and thus the build ID of the end
application will be affected by the cascade of hash changes. See the
upstream bug for more information [2].

This reverts commit fddaecc88979967d0e00e2fafdbaaabec030da9f.

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473
[2] https://github.com/golang/go/issues/77218

Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
meta/conf/bitbake.conf