emscripten: 2.0.10 -> 2.0.26#133217
emscripten: 2.0.10 -> 2.0.26#1332177c6f434c merged 8 commits intoNixOS:masterfrom yu-re-ka:feature/emscripten-2-0-26
Conversation
|
@ofborg build emscriptenPackages.zlib |
|
@ofborg build emscriptenPackages.zlib emscriptenPackages.json-c emscriptenPackages.libxml2 |
|
@ofborg build emscriptenPackages.json_c |
|
I am running the build on darwin and it fails with the following how do you feel about staying on 12 ? |
|
Have you tried if using |
|
sure, let me try and update you. |
|
From the changelog, it looks like the last version change mentions updating to llvm 12 However building it with version 12 fails with the following feel free to mark it as broken. |
|
I marked it as broken on darwin, |
|
@happysalada please try what I have pushed now 🙂 |
|
I've got the same failure I'm not sure why it's trying to biuld that. |
|
Yes, it should not attempt to build that on darwin with the current state of my branch. How did you start the build, from a local checkout or maybe the tar was cached? |
|
I am running |
|
Ah yes of course: |
|
Okay, went back to marking darwin as broken |
|
@primeos it would be awesome if you could give some feedback on the LLVM changes |
|
The LLVM changes look ok to me. I'm not sure if it's a good idea to pass trough |
Do you know who might be able to tell us how to implement it properly? I could expose it as
Changed it to the GitHub link, so it should work for you now |
|
Result of 6 packages marked as broken and skipped:
11 packages failed to build:
27 packages built:
|
Not sure, sorry :o
I would've probably exposed it as Anyway, I hope my comment didn't seem like a request to change that part, it was just meant as a FYI that this might potentially cause problems that would need to be addressed later. Actually, I just took a brief look at So the current approach might be fine (bundling the exposed attributes in an attribute set like And sorry for the delay, I was a bit busy and lost track of this. |
|
Okay! I did understand it as a request to change the way release_version is exposed, but if that is not the case thanks for the hint and I will look out for breakage after the merge 🙂 |
|
How much effort would be to go directly to 2.0.27 as it is released now? :P |
|
In particular, with LLVM12 on Linux (NixOS): |
Emscripten requires LLVM 13 release candidates: |
|
|
Nevermind, sorry, it was due to me, but I'm getting errors like this with a simple project (GMP): I tried to change the cache using |
|
Is this problem introduced by the changes in this PR? |
I'm not getting it using emscripten 2.0.10 (but other errors related to the mismatch with the LLVM version… invalid symbols JSON is generated by wasm-finalize). EDIT: to be precise, I suppose there must be a knob to say to emscripten, store these cached libs in some mutable path. |
Co-authored-by: Alexander Khovansky <[email protected]>
Co-authored-by: Alexander Khovansky <[email protected]>
|
@RaitoBezarius can you provide the full expression that builds on nixpkgs master, but not on this branch? |
On master, I don't know. On nixpkgs unstable (more or less recent versions of it), https://github.com/RaitoBezarius/nixexprs/blob/master/pkgs/science/lean/emscripten.nix shows two very different errors with the emscripten 2.0.10 and the emscripten on this branch. The first one fails due to LLVM version mismatches (very late), the second one fails due to being unable to write in the default cache directory of emscripten which is a nix store path (very early). To reproduce this, having a local checkout of my repository and doing All in all, I do not want this to be a blocking point of this pull request, if people are okay with it, I prefer to move on and see what can be done to fix it. |
|
@happysalada hmm, it looks like you reported new Darwin failures in straight |
|
Our packaging of LLVM 13 release candidates never worked on darwin. Also see here. |
Motivation for this change
This uses some of the fixes from #130706
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)