Package: libgcc1 Version: 1:10-20200202-1 Severity: serious Justification: FTBFS Tags: ftbfs Control: affects -1 src:glib2.0 src:xterm src:hdrmerge src:esorex
https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=s390x&ver=2.62.4-2&stamp=1580755175&file=log > Package versions: [with linebreaks added for legibility, quoting only the most libgcc-adjacent packages] > gcc_4:9.2.1-3.1 > gcc-10-base_10-20200202-1 > gcc-9_9.2.1-25 > gcc-9-base_9.2.1-25 > libgcc-9-dev_9.2.1-25 > libgcc-s1_10-20200202-1 > libgcc1_1:10-20200202-1 ... > Sanity check compiler command line: cc > /<<PKGBUILDDIR>>/debian/build/deb/meson-private/sanitycheckc.c > -o /<<PKGBUILDDIR>>/debian/build/deb/meson-private/sanitycheckc.exe > -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pipe > -D_FILE_OFFSET_BITS=64 -Wl,-z,relro -Wl,-z,now -Wl,-z,defs > -Wl,--no-as-needed -Wl,-O1 > Sanity check compile stdout: > > ----- > Sanity check compile stderr: > /usr/bin/ld: cannot find -lgcc_s > collect2: error: ld returned 1 exit status > > ----- > > meson.build:1:0: ERROR: Compiler cc can not compile programs. Presumably the dependencies and Breaks should be such that it isn't possible to get into a situation where libgcc_s can't be linked. Recent builds of xterm, hdrmerge and esorex show similar symptoms. smcv