Quoting Carlos from the upstream ticket: “ Upstream glibc 2.34 will release with a non-constant value of PTHREAD_STACK_MIN. This is because hardware vendors like Intel and Arm want to have scalable vector extensions whose size can no longer be determined at compile time. The minimum thread stack size in almost all cases has been really too small. By switching to sysconf we can directly pipe the kernel's expected minimum stack size to the process. This will need to be fixed in stress-ng. If you need help writing the change please reach out! ” The error looks like this: CC stress-pthread.c In file included from /usr/include/bits/local_lim.h:81, from /usr/include/bits/posix1_lim.h:161, from /usr/include/dirent.h:233, from stress-ng.h:50, from stress-pthread.c:25: stress-pthread.c: In function 'stress_pthread': stress-pthread.c:403:26: error: missing binary operator before token "(" 403 | #if DEFAULT_STACK_MIN == PTHREAD_STACK_MIN | ^~~~~~~~~~~~~~~~~ In file included from stress-pthread.c:25: stress-ng.h:844:35: warning: comparison of integer expressions of different signedness: 'long long unsigned int' and 'long int' [-Wsign-compare] 844 | #define STRESS_MAXIMUM(a,b) (((a) > (b)) ? (a) : (b)) | ^ stress-pthread.c:406:35: note: in expansion of macro 'STRESS_MAXIMUM' 406 | const size_t stack_size = STRESS_MAXIMUM(DEFAULT_STACK_MIN, PTHREAD_STACK_MIN); | ^~~~~~~~~~~~~~ stress-ng.h:844:50: warning: operand of '?:' changes signedness from 'long int' to 'long long unsigned int' due to unsignedness of other operand [-Wsign-compare] 844 | #define STRESS_MAXIMUM(a,b) (((a) > (b)) ? (a) : (b)) | ^~~ stress-pthread.c:406:35: note: in expansion of macro 'STRESS_MAXIMUM' 406 | const size_t stack_size = STRESS_MAXIMUM(DEFAULT_STACK_MIN, PTHREAD_STACK_MIN); | ^~~~~~~~~~~~~~ make[1]: *** [Makefile:372: stress-pthread.o] Error 1
Thanks Florian, fixed 3 days ago upstream: https://github.com/ColinIanKing/stress-ng/commit/f839de283c44ffe46a2d14bfdf854c145abd8ed6 Will update when a release is pushed that includes this.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
Hit another bug regarding how we handle verbosity in the Makefile. Upstream has fixed this so added temp fix in spec file to resolve.
FEDORA-2021-86c58df665 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-86c58df665
FEDORA-2021-86c58df665 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-86c58df665` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-86c58df665 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-86c58df665 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.