-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
zfs.meta.platforms: restrict to upstream-supported $TARGET_CPUs #194148
Conversation
Sounds like it would be better to list those four platforms explicitly then? |
Done: #194148 (comment) |
Rebased. |
@alyssais, you marked your review comment as "resolved". Are there any other changes you would like to request? |
`hasUnsupportedPlatform` was not updated with #37395, so it does not understand attrsets in `meta.[bad]platforms`. In particular, attrsets in `meta.badPlatforms` will "fail open" and be ignored. Let's use `lib.meta.availableOn` instead of duplicating its logic. Thanks to @alyssais for [noticing][1]. [1][#194148 (comment)] Co-authored-by: sternenseemann <sternenseemann@systemli.org>
`hasUnsupportedPlatform` was not updated with #37395, so it does not understand attrsets in `meta.[bad]platforms`. In particular, attrsets in `meta.badPlatforms` will "fail open" and be ignored. Let's use `lib.meta.availableOn` instead of duplicating its logic. Thanks to @alyssais for [noticing][1]. [1][NixOS/nixpkgs#194148 (comment)] Co-authored-by: sternenseemann <sternenseemann@systemli.org>
`hasUnsupportedPlatform` was not updated with #37395, so it does not understand attrsets in `meta.[bad]platforms`. In particular, attrsets in `meta.badPlatforms` will "fail open" and be ignored. Let's use `lib.meta.availableOn` instead of duplicating its logic. Thanks to @alyssais for [noticing][1]. [1][NixOS/nixpkgs#194148 (comment)] Co-authored-by: sternenseemann <sternenseemann@systemli.org>
Fixed merge conflict. |
`hasUnsupportedPlatform` was not updated with NixOS#37395, so it does not understand attrsets in `meta.[bad]platforms`. In particular, attrsets in `meta.badPlatforms` will "fail open" and be ignored. Let's use `lib.meta.availableOn` instead of duplicating its logic. Thanks to @alyssais for [noticing][1]. [1][NixOS#194148 (comment)] Co-authored-by: sternenseemann <sternenseemann@systemli.org>
Rebased. |
1 similar comment
Rebased. |
`hasUnsupportedPlatform` was not updated with #37395, so it does not understand attrsets in `meta.[bad]platforms`. In particular, attrsets in `meta.badPlatforms` will "fail open" and be ignored. Let's use `lib.meta.availableOn` instead of duplicating its logic. Thanks to @alyssais for [noticing][1]. [1][NixOS/nixpkgs#194148 (comment)] Co-authored-by: sternenseemann <sternenseemann@systemli.org>
@amjoseph-nixpkgs Can you provide some more detail on what breaks when building ZFS on platforms other than these five? I've been running ZFS on |
It's explained in the comment which this PR added. See the link to the ZFS source code.
Great, submit a PR. The only reason I wrote this PR is that forcibly breaking ZFS on platforms where it won't build is the only way to get a NixOS ISO to build for those platforms, because NixOS forcibly enables ZFS: nixpkgs/nixos/modules/tasks/filesystems/zfs.nix Lines 214 to 215 in e3cbd65
|
BTW, I confirmed that zfs does in fact build on armv7. So we should add it to the allowed platforms. Or, even better, go back to enumerating the Or, best of all, let people turn off ZFS. |
Description of changes
ZFS on linux has a lot of manual integrations with the platform-specific build machinery inside the kernel, and this has only been performed for four architectures.
Things done