M-Labs/nix-scripts
9
0
Fork 9
Code Issues 6 Pull Requests Releases Wiki Activity

installing board firmware on non-Linux-x86_64 should not trigger a rebuild #2

New Issue
Closed
opened 2019-04-19 13:23:10 +08:00 by sb10q · 3 comments
sb10q commented 2019-04-19 13:23:10 +08:00
Owner
Copy Link

Currently installing a board package (e.g. nix-env -f "<sinara-systems>" -iA artiq-board-kasli-berkeley) triggers a rebuild if the host is not Linux x86_64.
Nix is unaware that the package simply contains firmware that is independent of the system that was used to build it, sees that inputs such as the Rust compiler have changed, and attempts a rebuild.
I don't know if there is a Nix feature to handle this special case, or if that needs some hack.

Currently installing a board package (e.g. ``nix-env -f "<sinara-systems>" -iA artiq-board-kasli-berkeley``) triggers a rebuild if the host is not Linux x86_64. Nix is unaware that the package simply contains firmware that is independent of the system that was used to build it, sees that inputs such as the Rust compiler have changed, and attempts a rebuild. I don't know if there is a Nix feature to handle this special case, or if that needs some hack.
astro commented 2019-05-13 23:29:55 +08:00
Contributor
Copy Link

One idea that comes to mind: putting dependencies like the Rust compiler into sandboxPaths so that it is no longer an input, perhaps through the host's configuration.nix. Good idea?

One idea that comes to mind: putting dependencies like the Rust compiler into `sandboxPaths` so that it is no longer an input, perhaps through the host's `configuration.nix`. Good idea?
sb10q commented 2019-05-14 11:57:56 +08:00
Author
Owner
Copy Link

No. We do want to manage the Rust compiler with Nix, especially as we are using our own modified version. The "Nix firmware package installed on non-x86_64" case is niche enough that it is less important.

Vivado is using the sandbox hack mostly because it is a PITA to load tens of GB into the Nix store.

No. We do want to manage the Rust compiler with Nix, especially as we are using our own modified version. The "Nix firmware package installed on non-x86_64" case is niche enough that it is less important. Vivado is using the sandbox hack mostly because it is a PITA to load tens of GB into the Nix store.
sb10q commented 2022-02-05 17:55:23 +08:00
Author
Owner
Copy Link

obsoleted by AFWS

obsoleted by AFWS
sb10q closed this issue 2022-02-05 17:55:23 +08:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nix-scripts#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?