From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] glibc: Forward -ffile-prefix-map option to assembler flags
Date: Fri, 18 Apr 2025 12:24:47 +0200 [thread overview]
Message-ID: <D99OWQOPZ9JM.B2KF6VS4BV01@bootlin.com> (raw)
In-Reply-To: <20250417173332.554656-1-raj.khem@gmail.com>
On Thu Apr 17, 2025 at 7:33 PM CEST, Khem Raj via lists.openembedded.org wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
Hi Khem,
Thanks for your series.
I believe it is breaking go on the autobuilder:
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/plugin.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/net.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/internal/testpty.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
NOTE: Setscene tasks completed
NOTE: Running task 10301 of 11005 (/srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-extended/at/at_3.2.5.bb:do_package_write_ipk)
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/os/user.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
NOTE: Running task 10303 of 11005 (/srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-core/systemd/systemd-compat-units.bb:do_package_write_ipk)
NOTE: recipe sysklogd-2.7.2-r0: task do_package_write_ipk: Succeeded
NOTE: Running task 10307 of 11005 (/srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-devtools/python/python3-pluggy_1.5.0.bb:do_create_package_spdx)
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/runtime/cgo.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
NOTE: Task /srv/pokybuild/yocto-worker/genericarm64-alt/build/meta/recipes-extended/sysklogd/sysklogd_2.7.2.bb:do_package_write_ipk unihash changed to 69e6baca1186c873e5da11893803e9919551e88bbb951cc484649b725d81e7bd
NOTE: recipe python3-pluggy-1.5.0-r0: task do_create_package_spdx: Started
NOTE: recipe at-3.2.5-r0: task do_package_write_ipk: Started
ERROR: go-runtime-1.24.2-r0 do_package_qa: QA Issue: File /usr/lib/go/pkg/linux_arm64_dynlink/crypto/internal/sysrand/internal/seccomp.a in package go-runtime-dev contains reference to TMPDIR [buildpaths]
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/1406
Can you have a look at this please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-04-18 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 17:33 [PATCH 1/2] glibc: Forward -ffile-prefix-map option to assembler flags Khem Raj
2025-04-17 17:33 ` [PATCH 2/2] bitbake.conf: Switch prefix mapping to use -ffile-prefix-map Khem Raj
2025-04-18 10:24 ` Mathieu Dubois-Briand [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=D99OWQOPZ9JM.B2KF6VS4BV01@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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