Added a patch to Galios to protect from MINSTKSZ calling sysconf #4
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
In the Galios submodule, the file
lonestar/scientific/cpu/longestedge/test/catch.hpparound line
10732, astatic constexpis declared that depends on the MINSIGSTKSZThis all works unless a clever set of system headers in
signal.hexpandsMINSIGSTKSZtosysconf ( SIGSTKSZ ).When that happens, a very obscure bug throws an error when the Galios package runs a check.
This pull request adds a patch to check if MINSIGSTKSZ is defined and is a number, not a call. It that is not the case, then the constant is set to 32K.
There are some gratuitous spaces at the ends of line in ./build, but the key addition is the additional patch
extra/Galois5