New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dlang update #44904
Dlang update #44904
Conversation
Disabled tests on Darwin for now
Needed to switch to ldc as bootstrap compiler to fix the compilation
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: dmd, dtools, dub, ldc Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: dmd, dtools, dub, ldc Partial log (click to expand)
|
Let's try to get it to build on Darwin too. @GrahamcOfBorg build ldc dmd dtools dub |
Success on x86_64-linux (full log) Attempted: ldc, dmd, dtools, dub Partial log (click to expand)
|
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: ldc, dmd, dtools, dub Partial log (click to expand)
|
Don't know why it's not building on Darwin but I tested it on my machine without any problems. So this is ready to be merged. |
@GrahamcOfBorg build ldc dmd dtools dub |
darwin is limited to trusted user since we do not have a sandbox on macOS. |
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: ldc, dmd, dtools, dub Partial log (click to expand)
|
Failure on x86_64-darwin (full log) Attempted: ldc, dmd, dtools, dub Partial log (click to expand)
|
Unexpected error: command failed with exit code 1 on x86_64-linux (full log) Attempted: ldc, dmd, dtools, dub Partial log (click to expand)
|
For the Darwin build we once again have the problem with the shared tmp dirs. See #41099 (comment) for reference. Why the Linux build was done again is funny, the previous build package must have been erased from the binary cache or something because my second build run just used a cached build. Nevertheless this problem already occured and I opened NixOS/nix#2155 but closed it because it seemed to be fixed in nix 2.0.2. Has someone access to that very same build machine to check the nix version? |
The build before was executed on a different machine. I would ignore this for the moment. |
Motivation for this change
Bump versions for various dlang related packages.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)