Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
Before:
```
otool -D result-dev/lib/libwasmtime.dylib
result-dev/lib/libwasmtime.dylib:
/private/tmp/nix-build-wasmtime-9.0.2.drv-0/source/target/aarch64-apple-darwin/release/deps/libwasmtime.dylib
```
After:
```
otool -D result-dev/lib/libwasmtime.dylib
result-dev/lib/libwasmtime.dylib:
/nix/store/bz6l7dr60izrq6vga83df9y2p1mgh5hw-wasmtime-9.0.2-dev/lib/libwasmtime.dylib
```
|
|
|
|
|
|
|
|
https://github.com/bytecodealliance/wasmtime/blob/v9.0.0/RELEASES.md
|
|
Run tests depending on the platform features reported by stdenv.
|
|
Fixes CVE-2023-30624.
https://github.com/bytecodealliance/wasmtime/blob/v8.0.1/RELEASES.md
|
|
|
|
https://github.com/bytecodealliance/wasmtime/blob/b5a2d536acb2a8a8a505116302b36173bb713748/RELEASES.md
|
|
Fixes CVE-2023-26489 and CVE-2023-27477.
https://github.com/bytecodealliance/wasmtime/blob/v6.0.1/RELEASES.md
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* build wasmtime c-api libraries & headers as the "dev" output.
* bump wasmtime source version to 0.40.0.
|
|
Remove tests on x86_64-darwin to avoid specific false errors due to
the way Hydra runners are set up for this architecture.
On this platform, on Hydra runners we see: `SIMD support requires
SSE3, SSSE3, SSE4.1, and SSE4.2 on x86_64.` present in all failing
tests.
Thus, do not run tests on this platform to avoid false reports of this
derivation being broken, because Hydra runners are set up in a way
that this CPU features are not available.
An example of automation marking this derivation as broken because the
Hydra runs were reporting failures: 03bc5717445bbccda21d10eeecb6ded4c12d08fe.
|
|
https://github.com/bytecodealliance/wasmtime/blob/v0.39.1/RELEASES.md
Fixes CVE-2022-31146 and CVE-2022-31169.
|
|
|
|
Also, add `ereslibre` as a maintainer
|
|
|
|
Re-enable darwin platform.
|
|
|
|
|
|
Provide a specific path for the v8 project, so `wasmtime` dependency
`rusty_v8` can find it and does not need to download the static
library, what would break build hermetism.
|
|
|
|
|
|
Since aliases are disallowed in nixpkgs, this makes usage of Python 2
which is EOL more explicit.
|
|
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in
which cargo vendor erroneously changed permissions of vendored
crates. This was fixed in Rust
1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all
cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are
potentially broken.
This change updates cargoSha256/cargoHash tree-wide.
Fixes #121994.
|
|
Also begin to start work on cross compilation, though that will have to
be finished later.
The patches are based on the first version of
https://reviews.llvm.org/D99484. It's very annoying to do the
back-porting but the review has uncovered nothing super major so I'm
fine sticking with what I've got.
Beyond making the outputs work, I also strove to re-sync the packages,
as they have been drifting pointlessly apart for some time.
----
Other misc notes, highly incomplete
- lvm-config-native and llvm-config are put in `dev` because they are
tools just for build time.
- Clang no longer has an lld dep. That was introduced in
db29857eb391ed002046090851a44c452b80bdbd, but if clang needs help
finding lld when it is used we should just pass it flags / put in the
resource dir. Providing it at build time increases critical path
length for no good reason.
----
A note on `nativeCC`:
`stdenv` takes tools from the previous stage, so:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.stdenv.cc`: `(?0, ?1, x)`
while:
1. `pkgsBuildBuild`: `(?1, x, x)`
2. `pkgsBuildBuild.targetPackages`: `(x, x, ?2)`
3. `pkgsBuildBuild.targetPackages.stdenv.cc`: `(?1, x, x)`
|
|
|
|
+ use fetchFromGithub where possible
|
|
|
|
|
|
https://github.com/bytecodealliance/wasmtime/releases/tag/v0.18.0
|
|
https://github.com/bytecodealliance/wasmtime/releases/tag/v0.17.0
|
|
The issue https://github.com/bytecodealliance/wasmtime/issues/1556
appears to be fixed.
|
|
|
|
no regression over `master` where the test suite didn’t run at all
|