-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Hardcoded check for GNU Coreutils on MacOS #868
Comments
Hi @cloud8421! Thanks for bringing this up and sorry for the late reply. I was pretty busy this week. We have references to |
Thank you - no worries we're all busy! Following what you said it makes me think of an alternative. fully-forged/robo_clock@09e4481 worked very well for me paired with a temporary extension of I'm thinking if I extend the EDIT: the approach described above works well and it's completely self-contained inside Nix (see fully-forged/robo_clock@9bc94dd) |
I like that approach a lot! It sounds very simple and is a quick way to help other Nix users running into this. Yes, could you please submit a PR. Thanks! |
Environment
I'm running on MacOS Ventura, using a
flake.nix
file to provision the environment for the project.Here's the file, which is adapted from the
shell.nix
file provided at https://hexdocs.pm/nerves/installation.html#for-nixos-or-nix-package-manager.Current behavior
Running
nix develop
produces a valid environment, and I'm able to work on the project. Trying to build a firmware results in this error:I traced this down to
nerves/lib/mix/nerves/preflight.ex
Line 26 in d3d6970
gstat
.The problem is that on Nix the
coreutils
package doesn't prefix utils withg
as there's no risk of clashing with system built-ins. In my environment,stat
is the correct command that would need to be used.I can work around this by creating a link so that the condition is satisfied, but I am wondering if the preflight check needs to be more sophisticated. If it's ok, we can discuss here and I can provide a PR as a follow-up?
Thanks for the great work!
The text was updated successfully, but these errors were encountered: