This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1886814
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to make-dfsg in Ubuntu.
https://bugs.launchpad.net/bugs/1886814
Title:
posix_spawn usage in gnu make causes failures on s390x
Status in Ubuntu on IBM z Systems:
New
Status in glibc package in Ubuntu:
New
Status in linux package in Ubuntu:
Incomplete
Status in make-dfsg package in Ubuntu:
New
Bug description:
posix_spawn usage in gnu make causes failures on s390x
Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
started to use posix_spawn, instead of fork()/exec().
This has caused failure of an unrelated package flatpak-builder
autopkgtests on s390x only, like so
echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127
Julian Klaude investigated this in-depth. His earlier research also
indicated that this is a heisenbug, if one tries to print to stderr
before printing to stdout, no issue occurs.
We are configuring GNU make to be build with --disable-posix-spawn on
s390x only. We passed these details to Debian https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=964541 too.
But I do wonder, if there is something different or incorrect about
posix_spawn() implementation in either glibc, or linux kernel, on
s390x. Or gnu-make's usage of posix_spawn().
As otherise, using posix_spawn() in gnu-make works on other
architectures, and flatpak-builder autopkgtests pass too.
It seems very weird that stdout does not appear to be functional,
unless stderr was opened/written to, from gnu-make execution compiled
with posix-spawn feature.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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
