[Bug 2100598] Re: SIGILL on s390x
Andreas Hasenack
2100598 at bugs.launchpad.net
Fri Feb 28 13:39:40 UTC 2025
I did a revert of [2], and uploaded to this PPA[3]. The PPA has proposed
enabled.
Building started.
1. https://git.launchpad.net/~ahasenack/ubuntu/+source/gzip/commit/?id=389a495334db07cc37b1e2a2fa2d51f2c83fddd3
2. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
3. https://launchpad.net/~ahasenack/+archive/ubuntu/gzip-sigill
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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
More information about the foundations-bugs
mailing list