Ok, the straight revert, with plucky-proposed, got an FTBFS[1]:
gcc -DHAVE_CONFIG_H -I. -I.. -I./lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=3
-DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e -g -O2
-Werror=implicit-function-declaration -mbackchain
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security
-fno-stack-clash-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/gzip-1.13-1ubuntu3~ppa1 -Wall -MT
dfltcc.o -MD -MP -MF $depbase.Tpo -c -o dfltcc.o ../dfltcc.c &&\
mv -f $depbase.Tpo $depbase.Po
../dfltcc.c:87:17: error: expected declaration specifiers or '...' before
numeric constant
87 | char alignas (8) aligned;
| ^
../dfltcc.c:88:1: warning: no semicolon at end of struct or union
88 | };
| ^
../dfltcc.c:139:17: error: expected declaration specifiers or '...' before
numeric constant
139 | char alignas (8) aligned;
| ^
../dfltcc.c:140:1: warning: no semicolon at end of struct or union
140 | };
| ^
make[3]: *** [Makefile:1946: dfltcc.o] Error 1
1.
https://launchpadlibrarian.net/779322722/buildlog_ubuntu-plucky-s390x.gzip_1.13-1ubuntu3~ppa1_BUILDING.txt.gz
** Summary changed:
- SIGILL on s390x
+ dfltcc.c FTBFS on s390x
** Description changed:
I'm still gathering information about this bug.
+
+ UPDATE #1: see comment #2, this started out as an FTBFS.
Reportedly there was a SIGILL on gzip/s390x such that the hardware
acceleration on that platform for gzip had to be disabled in an
upload[1].
I found a matrix thread[2] about it.
Looks like it happened during a PPA build[3]:
(...)
/usr/bin/make check-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>/builddir'
Making check in lib
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir/lib'
/usr/bin/make check-am
make[4]: Entering directory '/<<PKGBUILDDIR>>/builddir/lib'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib'
Making check in doc
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir/doc'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir/doc'
Making check in .
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir'
/usr/bin/make check-local
make[4]: Entering directory '/<<PKGBUILDDIR>>/builddir'
./gzip < ../gzip.doc >gzip.doc.gz-t && mv gzip.doc.gz-t gzip.doc.gz
PATH=.:$PATH; { test '..' != . \
- || zdiff gzip.doc.gz; }
+ || zdiff gzip.doc.gz; }
PATH=.:$PATH; zdiff ../gzip.doc ../gzip.doc
PATH=.:$PATH; zdiff ../gzip.doc gzip.doc.gz
Illegal instruction (core dumped)
(...)
Apparently it hapepns[4] when "#define <stdalign.h>" is added? Perhaps
to fix an FTBFS in plucky?
"""
if you want to reproduce, take the upload Simon just sponsored, re-enable the
DFLTCC instruction in debian/rules, then add #define <stdalign.h> to the
includes at the top of dfltcc.c as a Quilt patch so that the code actually
builds, then build it in a PPA with s390x enabled, and that'll happen. Probably
you can unearth the ~danger2 build from my PPA though
"""
1. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
2.
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$XXeSHgSv1gpBMQ2fG_8S9ZJWjP31rsXY8qY2cCmFkrI?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
3.
https://launchpadlibrarian.net/776055235/buildlog_ubuntu-plucky-s390x.gzip_1.13-1ubuntu2~danger2_BUILDING.txt.gz
4.
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$QuKmfVGi7rtB8LXGC5fkiBDsg2ydqABLB3eWEtthgVw?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
** Also affects: gzip (Ubuntu Plucky)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/2100598
Title:
dfltcc.c FTBFS on s390x
Status in Ubuntu on IBM z Systems:
New
Status in gzip package in Ubuntu:
New
Status in gzip source package in Plucky:
New
Bug description:
I'm still gathering information about this bug.
UPDATE #1: see comment #2, this started out as an FTBFS.
Reportedly there was a SIGILL on gzip/s390x such that the hardware
acceleration on that platform for gzip had to be disabled in an
upload[1].
I found a matrix thread[2] about it.
Looks like it happened during a PPA build[3]:
(...)
/usr/bin/make check-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>/builddir'
Making check in lib
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir/lib'
/usr/bin/make check-am
make[4]: Entering directory '/<<PKGBUILDDIR>>/builddir/lib'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib'
make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib'
Making check in doc
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir/doc'
make[3]: Nothing to be done for 'check'.
make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir/doc'
Making check in .
make[3]: Entering directory '/<<PKGBUILDDIR>>/builddir'
/usr/bin/make check-local
make[4]: Entering directory '/<<PKGBUILDDIR>>/builddir'
./gzip < ../gzip.doc >gzip.doc.gz-t && mv gzip.doc.gz-t gzip.doc.gz
PATH=.:$PATH; { test '..' != . \
|| zdiff gzip.doc.gz; }
PATH=.:$PATH; zdiff ../gzip.doc ../gzip.doc
PATH=.:$PATH; zdiff ../gzip.doc gzip.doc.gz
Illegal instruction (core dumped)
(...)
Apparently it hapepns[4] when "#define <stdalign.h>" is added? Perhaps
to fix an FTBFS in plucky?
"""
if you want to reproduce, take the upload Simon just sponsored, re-enable the
DFLTCC instruction in debian/rules, then add #define <stdalign.h> to the
includes at the top of dfltcc.c as a Quilt patch so that the code actually
builds, then build it in a PPA with s390x enabled, and that'll happen. Probably
you can unearth the ~danger2 build from my PPA though
"""
1. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
2.
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$XXeSHgSv1gpBMQ2fG_8S9ZJWjP31rsXY8qY2cCmFkrI?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
3.
https://launchpadlibrarian.net/776055235/buildlog_ubuntu-plucky-s390x.gzip_1.13-1ubuntu2~danger2_BUILDING.txt.gz
4.
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$QuKmfVGi7rtB8LXGC5fkiBDsg2ydqABLB3eWEtthgVw?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2100598/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
