[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#954568: marked as done (gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE')

Your message dated Wed, 25 Mar 2020 10:57:41 +0100
with message-id <82cca473-f6bb-da29-ced8-3b277ad6188d@debian.org>
and subject line Re: Bug#954568: gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE'
has caused the Debian Bug report #954568,
regarding gcc-10-cross: FTBFS: x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
954568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954568
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: gcc-10-cross
Version: 4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[5]: Entering directory '/<<PKGBUILDDIR>>/gcc/build/gotools'
> /<<PKGBUILDDIR>>/gcc/build/./gcc/gccgo -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include -isystem /<<PKGBUILDDIR>>/gcc/build/sys-include   -g -O2 -I ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o go ../../src/gotools/../libgo/go/cmd/go/alldocs.go ../../src/gotools/../libgo/go/cmd/go/go11.go ../../src/gotools/../libgo/go/cmd/go/main.go ../x86_64-linux-gnu/libgo/libgotool.a  
> /<<PKGBUILDDIR>>/gcc/build/./gcc/gccgo -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include -isystem /<<PKGBUILDDIR>>/gcc/build/sys-include   -g -O2 -I ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o gofmt ../../src/gotools/../libgo/go/cmd/gofmt/doc.go ../../src/gotools/../libgo/go/cmd/gofmt/gofmt.go ../../src/gotools/../libgo/go/cmd/gofmt/internal.go ../../src/gotools/../libgo/go/cmd/gofmt/rewrite.go ../../src/gotools/../libgo/go/cmd/gofmt/simplify.go ../x86_64-linux-gnu/libgo/libgotool.a  
> echo 'package main' > zdefaultcc.go.tmp
> /<<PKGBUILDDIR>>/gcc/build/./gcc/gccgo -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include -isystem /<<PKGBUILDDIR>>/gcc/build/sys-include   -g -O2 -I ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o vet ../../src/gotools/../libgo/go/cmd/vet/doc.go ../../src/gotools/../libgo/go/cmd/vet/main.go ../x86_64-linux-gnu/libgo/libgotool.a  
> echo 'func defaultGCCGO(goos, goarch string) string { return "/usr/bin/x86_64-linux-gnu-gccgo-10" }' >> zdefaultcc.go.tmp
> echo 'func defaultCC(goos, goarch string) string { return "x86_64-linux-gnu-gcc-10" }' >> zdefaultcc.go.tmp
> echo 'func defaultCXX(goos, goarch string) string { return "x86_64-linux-gnu-g++-10" }' >> zdefaultcc.go.tmp
> echo 'const defaultPkgConfig = "pkg-config"' >> zdefaultcc.go.tmp
> /bin/bash ../../src/gotools/../move-if-change zdefaultcc.go.tmp zdefaultcc.go
> echo timestamp > s-zdefaultcc 
> /<<PKGBUILDDIR>>/gcc/build/./gcc/gccgo -B/<<PKGBUILDDIR>>/gcc/build/./gcc/ -B/usr/x86_64-linux-gnu/bin/ -B/usr/x86_64-linux-gnu/lib/ -isystem /usr/x86_64-linux-gnu/include -isystem /usr/x86_64-linux-gnu/sys-include -isystem /<<PKGBUILDDIR>>/gcc/build/sys-include   -g -O2 -I ../x86_64-linux-gnu/libgo -static-libstdc++ -static-libgcc -Wl,-z,relro -L ../x86_64-linux-gnu/libgo -L ../x86_64-linux-gnu/libgo/.libs -o buildid ../../src/gotools/../libgo/go/cmd/buildid/buildid.go ../../src/gotools/../libgo/go/cmd/buildid/doc.go ../x86_64-linux-gnu/libgo/libgotool.a  
> /usr/bin/x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/gcc-10-cross_4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message --- 
On 3/22/20 8:24 AM, Lucas Nussbaum wrote:
>> /usr/bin/x86_64-linux-gnu-ld: /lib/x86_64-linux-gnu/libpthread.so.0: undefined reference to `__twalk_r@GLIBC_PRIVATE'
>> collect2: error: ld returned 1 exit status

fixed with the rebuild cross-toolchain-base.

--- End Message ---
Reply to: