Bug#1126312: golang-1.25: FTBFS on s390x: TestTSAN: ThreadSanitizer: CHECK failed: tsan_platform_linux.cpp:571
Tianon Gravi <[email protected]>
| Newsgroups | gmane.linux.debian.devel.bugs.general,gmane.linux.debian.ports.s390 |
|---|---|
| Message-ID | <CAHnKnK3WgRA6F=7udXCuU8ji84KHk5Hb6cA1ZxH7Nif+Kz+x9g@mail.gmail.com> |
On Thu, 29 Jan 2026 at 02:35, Pranav P <[email protected]> wrote: > I was going through goenv.sh and found out that a > s390x-linux-gnu-g(cc/++) cross compiler is being used for compilation. > We verified the same failure is seen in the upstream repo even on other > distributions when using a cross-compiler. Why is the cross-compiler needed and > not the native compiler enough? Is there a specific need. > Because this failure is not seen with the native compiler (other than for a segfault > seen in tsan8 testcase which we will be working on) > Also, for reference I had checked Ubuntu's packaging. They are also using the native > compiler. Thanks for taking a look! To clarify, the cross-compiler is *only* used when cross compiling, which isn't something the official buildds will ever invoke (and that's where I'm pulling that failure from). Within Debian, "s390x-linux-gnu-g(cc/++)" is a native compiler when on the native architecture. So unless something is going very wrong, the build logs I've provided should be from the native compiler (with CGO_ENABLED=1 explicitly enabled). ♥, - Tianon