Bugzilla – Bug 1184995
gasnet build varies between hosts
Last modified: 2022-03-14 08:51:58 UTC
While working on reproducible builds for openSUSE, I found that when building gasnet on different hosts, there were differences between build results: --- old//usr/include/gasnet_config.h 2020-06-07 00:00:00.000000000 +0000 +++ new//usr/include/gasnet_config.h 2020-06-07 00:00:00.000000000 +0000 @@ -397,8 +397,8 @@ #define GASNETI_PAGESHIFT 12 /* auto-detected shared data cache line size */ -#define GASNETI_CACHE_LINE_BYTES 64 -#define GASNETI_CACHE_LINE_SHIFT 6 +#define GASNETI_CACHE_LINE_BYTES 128 +#define GASNETI_CACHE_LINE_SHIFT 7 and variations in binaries. My analysis shows this comes from configure.in detect_cachesz To reproduce, I do one build with osc build --build-opt=--vm-custom-opt="-cpu kvm64,l3-cache=on" Please allow identical binaries to be produced on different build hosts to facilitate verification of builds.
This could be easy enough to fix. But: - Reading GASnet upstream reply to your request ( https://bitbucket.org/berkeleylab/gasnet/pull-requests/253/allow-to-not-store-build-date-user-and/activity ) - Seeing that GASnet seems EOL (Last upstream release was 2018 and there seem toi be a "new" GASnetEX library) - Seeing that the only user of GASnet in Factory is legion which is not really maintained in OBS anyway. I strongly suggest that we drop both GASnet and Legion from Factory. I'll keep them in science:HPC as gasnet has to be maintained for SLES for a while. I'll keep legion as such (it is not in any SLES) in case someone ever wants to pick it up. Christoph, as you were the one who packaged them first, any feedback on this ?
As per discussion with legion upstream in https://github.com/StanfordLegion/legion/issues/941#issuecomment-751531028 let's drop them.
Delete request sent: https://build.opensuse.org/request/show/887075 Legion has already been dropped from Factory
gasnet and legion were dropped from Factory