-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
edk2: fix build on x86_64-darwin #199940
edk2: fix build on x86_64-darwin #199940
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as we were already hardcoding LLVM toolchain.
I ended up adding OVMF and edk2-uefi-shell to the PR since they depend on edk2. I can split them out, but the separate PRs wouldn’t be buildable until this one landed. |
Seems fair to me. |
Can someone check why ofBorg is unhappy? |
For Darwin:
It seems unrelated to the PR and more an ofborg issue itself. For aarch64-linux, just after VM boot, the command pipe is broken, I do not have aarch64 to reproduce, but it could be some regression due to this PR building a corrupted OVMF firmware, we should investigate. |
Looking at the full log, there’s a message about running out of space. Is that expected?
|
This is a classical issue with these macOS builders I think, cc @grahamc |
@reckenrode edk2-uefi-shell still seems to be failing on hydra for aarch64-darwin. I don't have a darwin machine, are you able to look into it? |
@LunNova I’ll take a look at it. The other edk2 packages don’t support aarch64-darwin, so the fix may be to limit edk2-uefi-shell similarly. |
I checked the job report for nixpkgs-22.05-darwin, but I don’t see any failures for edk2-uefi-shell. It also won’t build locally due to being an unsupported platform, which is what I should expect. Can you help point me in the right direction to where you’re seeing the failure on Hydra? |
Sorry that should've been x86_64-darwin not arrch64-darwin. |
It really seems to be an orthogonal issue due to the Apple environment, I think. |
I was able to reproduce the problem by disabling sandboxing. |
ZHF #199919
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes