Since we only depend on pythonImportsCheckHook when building with
Python, the pythonImportsCheck attribute will just be ignored when not
building with Python support.
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper
this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
checkInputs used to be added to nativeBuildInputs. Now we have
nativeCheckInputs to do that instead. Doing this treewide change allows
to keep hashes identical to before the introduction of
nativeCheckInputs.
Done with the help of https://github.com/Mindavi/nixpkgs-mark-broken
Tool is still WIP but this is one of the first results.
I manually audited the results and removed some results that were not valid.
Note that some of these packages maybe should have more constrained platforms set
instead of broken set, but I think not being perfectly correct is better than
just keep trying to build all these things and never succeeding.
Some observations:
- Some darwin builds require XCode tools
- aarch64-linux builds sometimes suffer from using gcc9
- gcc9 is getting older and misses some new libraries/features
- Sometimes tools try to do system detection or expect some explicit settings for
platforms that are not x86_64-linux
Changelog at https://www.nikhef.nl/~h24/qcdnum/QcdnumDownload.html says:
Same as qcdnum-17-01/15 with a few minor fixes.
One of these fixes is to replace real*16 with double precision for a few
variables to be standards compliant. This resolves following error:
Error: Old-style type declaration REAL*16 not supported at (1)
Workaround build failure on -fno-common toolchains like upstream
gcc-10. Otherwise build fails as:
ld: libpacklib.a(kedit.o):kuip/klink1.h:11: multiple definition of `klnkaddr';
libzftplib.a(zftpcdf.o):zftp/zftpcdf.c:155: first defined here
