-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Improve error message when missing remote building feature forbids build #2238
Comments
The second option seems much more user friendly to me. An error along these lines would have been the most helpful for me:
|
Similarly for local builds: #2238 |
I hit another variant of this, sort of. It's easy to make a syntax error and not notice or be warned, unless your Nix evaluator contains a @lheckemann who might then point it out. For those who don't, maybe this will help: For example, this will work for building my system configuration:
But this will not:
(Why my system needs kvm to build is a different question for another day...) |
Fixed! |
I'm stumped again. Why does it seem like it's not even trying the remote builder I'm offering up?
|
You need to specify that it's aarch64 in the builders string: |
You need to specify that it's aarch64 in the builders string: Originally posted by @lheckemann in #2238 (comment) This was what I needed in my ~/.config/nix/nix.conf (or any of the other possible alternative config locations), had |
I tried today to build a big package (chromium) remotely on a powerful machine with
but it would build only locally. Trying to force the remote build with
-j0
:got me:
unable to start any build; either increase '--max-jobs' or enable remote builds
But I have remote build enabled --
--builders
is given right there!On IRC I learned that it's because chromium has
requiredSystemFeatures = [ "big-parallel" ];
, and I need to declare that my remote machine isbig-parallel
.Solution:
But ideally we would improve the error message, perhaps
or enable remote builds
when it's enabledbig-parallel
The text was updated successfully, but these errors were encountered: