Your message dated Fri, 18 Sep 2020 10:50:35 +0200
with message-id <da4fcab0-f52d-c16e-5df0-d01c37650...@debian.org>
and subject line Re: gcc-9-cross: FTBFS: checking ...
has caused the Debian Bug report #954513,
regarding gcc-9-cross: FTBFS: checking whether .eh_frame section should be
read-only... /usr/bin/x86_64-linux-gnu-ld:
/usr/x86_64-linux-gnu/lib/../lib/libpthread.so.0: undefined reference to
`__libc_vfork@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 ow...@bugs.debian.org
immediately.)
--
954513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-9-cross
Version: 19
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):
> /bin/bash ./libtool --tag=CC --mode=compile
> /<<PKGBUILDDIR>>/gcc/build/./gcc/xgcc -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 -DHAVE_CONFIG_H -I.
> -I../../../../src/libgfortran -iquote../../../../src/libgfortran/io
> -I../../../../src/libgfortran/../gcc
> -I../../../../src/libgfortran/../gcc/config
> -I../../../../src/libgfortran/../libquadmath -I../../.././gcc
> -I../../../../src/libgfortran/../libgcc -I../../libgcc
> -I../../../../src/libgfortran/../libbacktrace -I../../libbacktrace
> -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -Wextra -Wwrite-strings
> -Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
> -ffunction-sections -fdata-sections -g -O2 -m32 -MT pow_r10_i8.lo -MD -MP
> -MF .deps/pow_r10_i8.Tpo -c -o pow_r10_i8.lo `test -f
> '../../../../src/libgfortran/generated/pow_r10_i8.c' || echo
> '../../../../src/libgfortran/'`../../../../src/libgfortran/generated/pow_r10_i8.c
> yes
> checking assembler supports pc related relocs... yes
> checking toolchain supports unwind section type... libtool: compile:
> /<<PKGBUILDDIR>>/gcc/build/./gcc/xgcc -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 -DHAVE_CONFIG_H -I.
> -I../../../../src/libgfortran -iquote../../../../src/libgfortran/io
> -I../../../../src/libgfortran/../gcc
> -I../../../../src/libgfortran/../gcc/config
> -I../../../../src/libgfortran/../libquadmath -I../../.././gcc
> -I../../../../src/libgfortran/../libgcc -I../../libgcc
> -I../../../../src/libgfortran/../libbacktrace -I../../libbacktrace
> -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -Wextra -Wwrite-strings
> -Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
> -ffunction-sections -fdata-sections -g -O2 -m32 -MT pow_r10_i8.lo -MD -MP -MF
> .deps/pow_r10_i8.Tpo -c ../../../../src/libgfortran/generated/pow_r10_i8.c
> -fPIC -DPIC -o .libs/pow_r10_i8.o
> yes
> checking whether .eh_frame section should be read-only...
> /usr/bin/x86_64-linux-gnu-ld:
> /usr/x86_64-linux-gnu/lib/../lib/libpthread.so.0: undefined reference to
> `__libc_vfork@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-9-cross_19_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 ---
That built with a new build.
--- End Message ---
