* pytorch-0.3 with optional cuda and cudnn
* pytorch tests reenabled if compiling without cuda
* pytorch: Conditionalize cudnn dependency on cudaSupport
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Compile with the same GCC version used by CUDA if cudaSupport
Fixes this error:
In file included from /nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/host_config.h:50:0,
from /nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/cuda_runtime.h:78,
from <command-line>:0:
/nix/store/gv7w3c71jg627cpcff04yi6kwzpzjyap-cudatoolkit-9.1.85.1/include/crt/host_config.h:121:2: error: #error -- unsupported GNU version! gcc versions later than 6 are not supported!
#error -- unsupported GNU version! gcc versions later than 6 are not supported!
^~~~~
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Build with joined cudatoolkit
Similar to #30058 for TensorFlow.
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: 0.3.0 -> 0.3.1
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Patch for “refcounted file mapping not supported” failure
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Skip distributed tests
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
* pytorch: Use the stub libcuda.so from cudatoolkit for running tests
Signed-off-by: Anders Kaseorg <andersk@mit.edu>
The latest update of `yowsup` (https://github.com/tgalal/yowsup/releases/tag/v2.5.7)
contains the following fixes:
* Updated tokens
* Fixedtgalal/yowsup#1842: Bug in protocol_groups RemoveGroupsNotificationProtocolEntity
* Other minor bug fixes
The `argparse-dependency.patch` required a rebase onto the latest
version of `setup.py` and ensures that `argparse` won't be needed as
extra dependency as our `python3` package ships `argparse` by default.
A short note to Python 2 support:
the actual issue related to Python 2.x support has been resolved
(https://github.com/tgalal/yowsup/issues/2325#issuecomment-354533727),
however this relies on `six==1.10` which isn't support by `nixpkgs` as
`six` has been bumped to `1.11`. When trying to inject a patched version
of our `six` package based on `six==1.10` you'll run into issues with
duplicated libraries in your closure as further build dependencies
(`pytest` in this case) use the latest `six` version. As Python 2.7 will
die in 2020 (https://pythonclock.org/) and patching around in the
dependencies of `pytest` to get `yowsup` running isn't worth the effort
in my opinion I decided to keep the Python 2.x build disabled for now.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/apktool/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool -h’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool help’ got 0 exit code
- ran ‘/nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3/bin/apktool --version’ and found version 2.3.3
- found 2.3.3 with grep in /nix/store/x2im0ff8abgj4zp2al9v7339b4lqm7y2-apktool-2.3.3
- directory tree listing: https://gist.github.com/442f8aae9c8a9a0f7594fc049c97fe51
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/opendht/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtnode help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat --help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtchat help’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner -h’ got 0 exit code
- ran ‘/nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1/bin/dhtscanner --help’ got 0 exit code
- found 1.7.1 with grep in /nix/store/jaqkxg2ypkyh45w215kl1px7p8bvjvza-opendht-1.7.1
- directory tree listing: https://gist.github.com/a3f2bc9f76c4720e3fec78139e60c160
To mitigate Spectre Variant 2, GCC needs to have retpoline
support (-mindirect-branch and -mfunction-return arguments on amd64
and i386).
Patches were pulled from H.J. Lu's backport branch to
4.9 (hjl/indirect/gcc-4_9-branch), available at
https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc-4_9-branch/master. Upstream
GCC does not apply patches to anything older than the
gcc-6-branch. H.J. Lu is the author of the upstream retpoline commits
as well.
Several Linux distributions already backported these patches to GCC 4
branches and some old kernels (3.13 for instance) have been recompiled
with these GCC patches. These kernels only allow to load kernel
modules that are compiled with the retpoline support.
References:
- Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261
- Ubuntu package: https://launchpad.net/ubuntu/+source/gcc-4.8/4.8.4-2ubuntu1~14.04.4Fixes#38394
blank-canvas-0.6.3 depends on base-compat-batteries-0.10, which
depends on base-compat-0.10. This conflicts with the rest of the LTS
set, which uses base-compat-0.9. No base-compat-batteries-0.9 exists.
blank-canvas-0.6.2 only depends on base-compat >= 0.8 && < 0.10.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/umockdev/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-run --version’ and found version 0.11.3
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record -h’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --help’ got 0 exit code
- ran ‘/nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3/bin/umockdev-record --version’ and found version 0.11.3
- found 0.11.3 with grep in /nix/store/lzgyyshqfl8ma25ixvldaz40pscq30h4-umockdev-0.11.3
- directory tree listing: https://gist.github.com/3dcf7f53d51ca4a9c739e567456cb16f
For details on the patches applied, see:
https://sources.debian.org/patches/ltrace/0.7.3-6/
Disabling '-Werror' may be a problem in the future again,
but for now keep things simple now that they're fixed.
"platforms.gnu" has been linux-only since at least 17.03:
$ nix eval -f channel:nixos-17.03 lib.platforms.gnu
[ "i686-linux" "x86_64-linux" "armv5tel-linux" "armv6l-linux" "armv7l-linux" "aarch64-linux" "mips64el-linux" ]
Unlike platforms.linux, platforms.gnu indicates "must use glibc"
which for the most part is not intended.
Replacing platforms.gnu with platforms.linux would be the same "today"
but let's err on preserving existing behavior and be optimistic
about platforms these packages work on.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/kotlin/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41/bin/kotlin -h’ got 0 exit code
- ran ‘/nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41/bin/.kotlin-wrapped -h’ got 0 exit code
- found 1.2.41 with grep in /nix/store/5byxycv5j3gvwvr87qpv08a7347fxv9q-kotlin-1.2.41
- directory tree listing: https://gist.github.com/927e0c1e045ca7c165603ae8b1961beb
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/spidermonkey/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 -h’ got 0 exit code
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 --help’ got 0 exit code
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 -v’ and found version 52.7.4
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52 --version’ and found version 52.7.4
- ran ‘/nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4/bin/js52-config --version’ and found version 52.7.4
- found 52.7.4 with grep in /nix/store/47rbdzbgccrrdc63fnsnwklria9clmms-spidermonkey-52.7.4
- directory tree listing: https://gist.github.com/7e5182415a0a1bce8071576312c08a3a
I still feel weird about doing this because it seems a little hacky
but this was requested by @Mic92 and seems understandable to not want
to mix up libressl outputs with netcat stuff.
@7c6f434c wrote in [1]:
Maybe copy-paste the upstream "Alkimia is the infrastructure for
common storage and business logic that will be used by all financial
applications in KDE. The target is to share financial related
information over application bounderies." as longDescription for
Alkimia? The current description makes me want to look up the
homepage to find out what it actually is (then I do, and despair).
[1]: https://github.com/NixOS/nixpkgs/pull/39647#issuecomment-385169261
Signed-off-by: aszlig <aszlig@nix.build>
This is used by KMyMoney and also the reason why I needed to add C++
support to MPIR in the parent commit.
The reason why I didn't add myself as a maintainer is because I'm not
personally using KMyMoney and thus Alkimia.
Signed-off-by: aszlig <aszlig@nix.build>
This is one of the requirements of KMyMoney and packaging is quite
straightforward with no unexpected traps.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @ttuegel
This is needed by Alkimia which I'm going to package soon as part of
KMyMoney.
I enabled this by default, because it doesn't increase the closure size
a whole lot (only around 150 KiB):
$ nix-store -q --size /nix/store/...old...-mpir-3.0.0
1223248
$ nix-store -q --size /nix/store/...new...-mpir-3.0.0
1377136
Introducing an option for enabling/disabling this is not worth it,
because it doesn't conflict with anything and the size increase is the
only drawback and we can still make it configurable if we want someday.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @7c6f434c
Apparently, without this patch `NT_PRSTATUS` is not found. So the patch
adds the include apparently necessary. `NT_PRSTATUS` is also defined in
`<linux/ptrace.h>`, which would likely have been a better name, were it
not in the `linux/` directory, which is a priori not stable.
The need to do that is kind of weird (the change was introduced in [1],
and fedora apparently didn't need this additional import), but I'll try
to upstream it.
[1] https://github.com/SimonKagstrom/kcov/pull/239
Unfortunately I haven't found a way for nose to disable doctests and the
-e/--exclude flag only works on unit tests.
So I'm using sed in postPatch to remove the doctests without mangling
the whole docstring.
I've built weboob and it now succeeds.
Signed-off-by: aszlig <aszlig@nix.build>
OpenSSL is needed for gct-tool and libgpgerror for RSA key utilities
(src/crypt3/cryptkeyrsa.c).
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
So far we used only the defaults, which are gtk2 and qt5. However
nowadays most applications have already switched to Qt 5 and Gtk 3, so
let's aim for that instead.
The reason Gtk 2 is still there is because GnuCash in nixpkgs is using
the Gtk 2 interface, so we can drop it as soon as a newer GnuCash has
landed in nixpkgs.
Right now the only package that depends on this is GnuCash (and
aqbanking of course), so I've tested this by not only building
gwenhywfar and aqbanking but also GnuCash. I did however not test
whether HBCI functionality works, only whether GnuCash starts up.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu, @peti, @domenkozar
This is to make sure that we don't get a disparity between the version
in sources.nix and the version in the package expression and it's mostly
to get the package expression in par with aqbanking and gwenhywfar.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Upstream changes in 5.7.8:
* Update bank information files for German banks because the format of
ZKA files has changed in the meantime.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=03&release=217
Upstream changes in 5.7.7:
* Fix of manually adding new HBCI accounts (for example using
KMyMoney).
* Fix wrong truncation of account numbers in some turnovers of the
SWIFT parser.
* Simplified code for inserting new account data while fetching HBCI
accounts.
* Update information for German banks.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=03&release=216
As with the gwenhywfar update, the updater script (update.sh) actually
didn't get the right file to download, so I temporarily modified it to
download file number 2 because file number 1 is the GPG signature. The
reason why I didn't fix the updater is because the upstream site will
have different URLs in the next upcoming version, so our updater is
basically end-of-life for now.
I also changed the package expression to use the version from
sources.nix instead of a hardcoded value.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Upstream changes in 4.20.0:
* Update bank information files for German banks because the format of
ZKA files has changed in the meantime.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=208
Upstream changes in 4.19.0:
* Add frontend for GTK3.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=207
Upstream changes in 4.18.0:
* Show hashes for MD5, SHA1 and SHA512 in SSL certificates because
some bank servers display different hashing variants.
* Let GNUTLS handle the localisation of TrustStore certificates.
Upstream release notes in German:
https://www.aquamaniac.de/sites/download/releasenote.php?package=01&release=206
The updater script (update.sh) actually didn't get the right file to
download, so I temporarily modified it to download file number 2 because
file number 1 is the GPG signature. The reason why I didn't fix the
updater is because the upstream site will have different URLs in the
next upcoming version, so our updater is basically end-of-life for now.
I also changed the package expression to use the version from
sources.nix instead of a hardcoded value.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @goibhniu
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/cgal/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_CMakeLists -h’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_CMakeLists help’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_cmake_script -h’ got 0 exit code
- ran ‘/nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12/bin/cgal_create_cmake_script --help’ got 0 exit code
- found 4.12 with grep in /nix/store/7py5j9ixfljnic4dr3ij97msnj0wahv6-cgal-4.12
- directory tree listing: https://gist.github.com/35067880611978f76a8e3f3adac7f12a
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fastjet/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config -h’ got 0 exit code
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config --help’ got 0 exit code
- ran ‘/nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1/bin/fastjet-config --version’ and found version 3.3.1
- found 3.3.1 with grep in /nix/store/y8mkgp5xlcfik6fb5r1dzb93n6xm1f9r-fastjet-3.3.1
- directory tree listing: https://gist.github.com/aa455f4d0802d2b2b76678ecccfe3eab
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/jruby/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby --help’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby.bash -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/jruby.bash --help’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/ruby -h’ got 0 exit code
- ran ‘/nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0/bin/ruby --help’ got 0 exit code
- found 9.1.17.0 with grep in /nix/store/g4a83h4462412zd3cf95j5ny19bxgha6-jruby-9.1.17.0
- directory tree listing: https://gist.github.com/20468ca63db765e0d42a1c93191f0901
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libmwaw/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwawFile -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwawZip -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2csv -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2html -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2raw -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2raw --version’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2svg -v’ and found version 0.3.14
- ran ‘/nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14/bin/mwaw2text -v’ and found version 0.3.14
- found 0.3.14 with grep in /nix/store/a9gm0j8p8v4i0psq5jx3kyxvphhpz8rs-libmwaw-0.3.14
- directory tree listing: https://gist.github.com/e6bf3abafc8b9634a51796eb8969b268
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/libwps/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2html -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2raw -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2raw --version’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wps2text -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2csv -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2raw -v’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2raw --version’ and found version 0.4.9
- ran ‘/nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9/bin/wks2text -v’ and found version 0.4.9
- found 0.4.9 with grep in /nix/store/ffxxsf65d1lgwg2v456z97waagpn3ng0-libwps-0.4.9
- directory tree listing: https://gist.github.com/a3fdf5973402ddf0aa6d1a0ecd058d41
Yeah yeah, I want parallel glob expansion but you get what I mean.
These two packages like getting upgraded together so to minimize
incompatibilities I'm upgrading them both in the same commit.
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
(cherry picked from commit ba52ae5048)
Following legacy packing conventions, `isArm` was defined just for
32-bit ARM instruction set. This is confusing to non packagers though,
because Aarch64 is an ARM instruction set.
The official ARM overview for ARMv8[1] is surprisingly not confusing,
given the overall state of affairs for ARM naming conventions, and
offers us a solution. It divides the nomenclature into three levels:
```
ISA: ARMv8 {-A, -R, -M}
/ \
Mode: Aarch32 Aarch64
| / \
Encoding: A64 A32 T32
```
At the top is the overall v8 instruction set archicture. Second are the
two modes, defined by bitwidth but differing in other semantics too, and
buttom are the encodings, (hopefully?) isomorphic if they encode the
same mode.
The 32 bit encodings are mostly backwards compatible with previous
non-Thumb and Thumb encodings, and if so we can pun the mode names to
instead mean "sets of compatable or isomorphic encodings", and then
voilà we have nice names for 32-bit and 64-bit arm instruction sets
which do not use the word ARM so as to not confused either laymen or
experienced ARM packages.
[1]: https://developer.arm.com/products/architecture/a-profile
On GNU/Linux the build references these files, so let's fetch them from
the Chromium repository. I haven't checked whether they are heavily
patched or whether we can use the version from LLVM, but when looking at
the changes, they do seem to divert a bit from upstream LLVM.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
The tarball from upstream seems to be generated on the fly, so the
output is not deterministic and using fetchzip makes this more reliable
as we have a recursively hashed output path without any of the
non-determinisms in tarballs.
Unfortunately, the build still fails on NixOS systems, because we need a
few more stuff in the build tree.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @matthewbauer, @stesie
Fixes#39334
and Fixes#36729
Also, Fixes#36932 (hopefully it's still building)
(This might be able to be able to be cherry-picked to 18.03 but be
careful - chromium is extremely touchy. Probably best to wait for it
to be built successfully on Hydra a few times.)
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/eccodes/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/codes_info -v’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_histogram -h’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_histogram --help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_merge -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib2ppm -h’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib2ppm --help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_set -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_get_data -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_index_build help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_index_build -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_set -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_index_build help’ got 0 exit code
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_index_build -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/gts_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_dump -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_ls -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_compare -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_get -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/metar_copy -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/grib_to_netcdf -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/codes_bufr_filter -V’ and found version 2.7.3
- ran ‘/nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3/bin/bufr_filter -V’ and found version 2.7.3
- found 2.7.3 with grep in /nix/store/i6m5cl0plmsnll3n90h88vcnjc269vh9-eccodes-2.7.3
- directory tree listing: https://gist.github.com/f485bc3b3d6105246360c970ac7462e1
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/grib-api/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_histogram -h’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_histogram --help’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_info -v’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_filter -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_ls -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_dump -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib2ppm -h’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib2ppm --help’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_set -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_get -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_get_data -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_copy -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_packing help’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_compare -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_index_build help’ got 0 exit code
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_index_build -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_to_netcdf -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys -V’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys -v’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys --version’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys version’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys -h’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys --help’ and found version 1.26.1
- ran ‘/nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1/bin/grib_list_keys help’ and found version 1.26.1
- found 1.26.1 with grep in /nix/store/60krazh9fxzn8n99nx9rxx8mi78hf9sx-grib-api-1.26.1
- directory tree listing: https://gist.github.com/e201ebaf6d3662af211ceca919f68df1
