Using the new native M1 support #334

purcell · 2021-05-28T06:57:36Z

Apple M1 (aarch64-darwin) support just landed in Nixpkgs master, so I thought I'd open an issue here to describe/discuss how best to migrate to a nix-darwin setup which uses that system type by default.

I've had some luck with this, so I'll recount what I've done. Starting with a regular x86_64-darwin installation, on the nixpkgs-unstable channel, I added

      extra-platforms = x86_64-darwin aarch64-darwin

to nix.extraOptions and defined a package set like

  pkgsM1 = import <nixpkgs> { localSystem = "aarch64-darwin"; };

At this point, it's possible to set nix.pkg = pkgsM1.nix, and then after darwin-rebuild switch, the nix tools and overall system are switched to aarch64, and pkgs will yield aarch64 packages.

However, of course many packages in a user's configuration won't build on aarch64, so to get to this stage, you have to comment out those packages. After switching the nix installation to aarch64, the packages can be added back in, with a similar pkgs_x86.

Notable packages (for me) which don't yet build on aarch64 are nix-direnv and anything written in Haskell, like shellcheck, niv.

It's also possible to skip switching nix.pkg, and keep the overall system as x86_64 for now: then, packages can be included from pkgsM1 for installation as desired. This might be the best choice for most users until some of the rough edges are smoothed off.

Hope this helps some people. I'd be keen to hear tips and tricks from others.

The text was updated successfully, but these errors were encountered:

hlolli · 2021-05-29T15:58:58Z

Thanks a lot for this tip. I've finally got the wheels running after mostly commenting out package overrides based on nixpkgs PR's. I went the other way around it. Instead of selecting the aarch64 packages, I overlay the x86_64's.

~/.nixpkgs/darwin-configuration.nix

I use with to thoroughly set the stdenv.

{ ... }:
# just a tarball of the latest master
with import (fetchTarball /. + "file:///Users/hlolli/nixpkgs-fork.tar.gz") { localSystem = "aarch64-darwin"; };

 {
  imports = [
    /Users/hlolli/nixos-configuration
  ];
}

/Users/hlolli/nixos-configuration/default.nix

I have the two versions

{ stdenv, config, pkgs, ... }:

let pkgsX86 = import <nixpkgs> { localSystem = "x86_64-darwin"; };
...

and overlay the unsupported packages

...
  nixpkgs.overlays = [
    (
    self: super: {
      inherit (pkgsX86) haskell haskellPackages openssl openssl_1_1;
    }
  )];
  ...

long rebuild ahead rn, praying for luck 🙏

LnL7 · 2021-05-29T16:06:31Z

I don't think that overlay will do what you want as it mixes x86 and arm libraries. To build a mixed system you most likely want to use the same overlays for both package sets and between the architecture at binary level.

{ config, lib, pkgs, ... }:
let pkgsX86 = import <nixpkgs> { localSystem = "x86_64-darwin"; overlays = config.nixpkgs.overlays; };
{
  environment.systemPackages =
    [ pkgs.curl
      pkgsX86.haskell
    ];
}

hlolli · 2021-05-29T16:17:18Z

Yes indeed, I should have known, but the rosetta2 magic has spelled my senses here.
Bad idea I was suggesting there above.

ld: warning: ignoring file /nix/store/96j2ai9h4f5kaqcnp9kvgbp2srr79xhx-openssl-1.1.1k/lib/libcrypto.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:

Besides the fact that openssl compiles fine on aarch (so far so good after I removed it from the overlay), then I hope this adverts pitfalls for others.

hlolli · 2021-05-30T15:05:23Z

Maybe not the right place for it, but I have a PR for emacs fix for aarch64, if someone wants to review and test the fix NixOS/nixpkgs#124888

antifuchs · 2021-06-10T15:37:43Z

I've gotten a flake.nix-based configuration working working, where I install the rosetta x86-64 packages by default and opt into arm64 packages on a case-by-case basis.

Here's the relevant flake.nix bits:

{
outputs = {self, nixpkgs, darwin, ...}: {
  darwinConfigs."my-machine" = darwin.lib.darwinSystem {
    modules = [
      { nix.extraOptions = ''extra-platforms = x86_64-darwin aarch64-darwin ''; }
      ./machine/my-machine.nix
    ];
    specialArgs = { 
      m1Ize = (pkgs: config: import nixpkgs {
        system = "aarch64-darwin";
        overlays = config.nixpkgs.overlays;
      });
    };
  };
};
}

note the specialArgs.m1Ize function; that will be passed down to the modules, e.g. to my development system config module:

{ pkgs, config, lib, m1Ize, ... }:
let
  m1Pkgs = m1Ize pkgs config;
in
{
  environment.systemPackages = with m1Pkgs; [
    cmake
    llvm
    openssl
    gnumake
    postgresql_13
  ];
}

You have to use that let binding in all the modules where you intend to use it, but it's about as short as it gets. Hope this helps fellow flake-ers (:

lloeki · 2021-06-18T14:55:55Z

For those that stumble on this and, like me, use a pure nixpkgs install (i.e don't use nix-darwin, flakes, or whatever), I'm popping up a nix-shell with arm64 derivations quite easily:

$ sh <(curl -L https://nixos.org/nix/install) --daemon  # install as usual
$ cat /etc/nix/nix.conf                                 # add extra-platforms

build-users-group = nixbld
extra-platforms = x86_64-darwin aarch64-darwin
$ cat shell.nix
{
  pkgs ? import <nixpkgs> { localSystem = "aarch64-darwin"; },
}:
let
  ruby = pkgs.ruby_3_0;
in pkgs.mkShell {
  buildInputs = [
    pkgs.openssl
    ruby
  ];
}
$ nix-shell
nix$ which ruby
/nix/store/sc54smx4gqa80nxwpfvpxfw8slh7fgyd-ruby-3.0.1/bin/ruby
nix$ file $(which ruby)
/nix/store/sc54smx4gqa80nxwpfvpxfw8slh7fgyd-ruby-3.0.1/bin/ruby: Mach-O 64-bit executable arm64

Now I'm a complete beginner, so if only I knew how to pivot the nixpkgs install into arm64 😅 I'd rather be arm64 first and fill in the blanks with x86_64 on a case by case basis with an additional pkgs_x86_64 ? import <nixpkgs> { localSystem = "x86_64-darwin"; }, in shell.nix:

{
  pkgs ? import <nixpkgs> { localSystem = "aarch64-darwin"; },
  pkgs_x86_64 ? import <nixpkgs> { localSystem = "x86_64-darwin"; },
}:
let
  ruby = pkgs.ruby_3_0;
in pkgs.mkShell {
  buildInputs = [
    pkgs.openssl
    ruby
    pkgs_x86_64.shellcheck
  ];
}

LnL7 · 2021-06-18T16:50:59Z

@lloeki By default the nix client evaluates using the system it was built with. So upgrading you nix installation to the arm build will also change the default.

lloeki · 2021-06-19T18:28:12Z

Thanks @LnL7, I think I managed to do it:

$ sudo su -l
# cat /etc/nix/nix.conf 
build-users-group = nixbld
system = aarch64-darwin
extra-platforms = x86_64-darwin aarch64-darwin
#  launchctl unload /Library/LaunchDaemons/org.nixos.nix-daemon.plist
#  launchctl load /Library/LaunchDaemons/org.nixos.nix-daemon.plist
# nix-env -iA nixpkgs.nix
replacing old 'nix-2.3.12'
installing 'nix-2.3.12'
-----8<------
# file $(which nix-shell)
/var/root/.nix-profile/bin/nix-shell: Mach-O 64-bit executable arm64
# file /nix/var/nix/profiles/default/bin/nix-daemon
/nix/var/nix/profiles/default/bin/nix-daemon: Mach-O 64-bit executable arm64
# launchctl unload /Library/LaunchDaemons/org.nixos.nix-daemon.plist
# launchctl load /Library/LaunchDaemons/org.nixos.nix-daemon.plist

From there I think I can remove system = aarch64-darwin from /etc/nix/nix.conf, but everything seems alright nonetheless.

shaunsingh · 2021-06-22T03:31:29Z

Hi, I'm having an error with installing nix-darwin using my configuration.nix. My configuration.nix can be found here: https://github.com/shaunsingh/vimrc-dotfiles/blob/main/.nixpkgs/darwin-configuration.nix

Please let me know if you need any other information that may help with solving the issue. Thank you for the amazing project and your time!

Edit: Sorry for cluttering up the thread. The error in question was due to a package not cooperating with aarch64 (Neovim-nightly), nix-darwin itself was/is working fine. I apologize for my noob behavior. Thanks for the great project once again!

BaoPham92 · 2021-07-05T17:02:43Z

Thanks @LnL7, I think I managed to do it:

$ sudo su -l
# cat /etc/nix/nix.conf 
build-users-group = nixbld
system = aarch64-darwin
extra-platforms = x86_64-darwin aarch64-darwin
#  launchctl unload /Library/LaunchDaemons/org.nixos.nix-daemon.plist
#  launchctl load /Library/LaunchDaemons/org.nixos.nix-daemon.plist
# nix-env -iA nixpkgs.nix
replacing old 'nix-2.3.12'
installing 'nix-2.3.12'
-----8<------
# file $(which nix-shell)
/var/root/.nix-profile/bin/nix-shell: Mach-O 64-bit executable arm64
# file /nix/var/nix/profiles/default/bin/nix-daemon
/nix/var/nix/profiles/default/bin/nix-daemon: Mach-O 64-bit executable arm64
# launchctl unload /Library/LaunchDaemons/org.nixos.nix-daemon.plist
# launchctl load /Library/LaunchDaemons/org.nixos.nix-daemon.plist

From there I think I can remove system = aarch64-darwin from /etc/nix/nix.conf, but everything seems alright nonetheless.

I followed both of your above approach while being on macOS Big Sur.

So far I was able to follow the steps, but activating "nix-shell" within the plutus project would give me the following:

error: cannot coerce null to a string, at /nix/store/sdjxjsd5phr225rs2qzklj2xci0c9gr0-source/pkgs/stdenv/generic/make-derivation.nix:192:19

I tried:

error: Package ‘ghc-8.10.4’ in /nix/store/9jyvfa211fxvwyd79vz5ydak07q52y5w-nixexprs.tar.xz/pkgs/development/compilers/ghc/8.10.4.nix:267 is not supported on ‘aarch64-darwin’, refusing to evaluate.

a) To temporarily allow packages that are unsupported for this system, you can use an environment variable
   for a single invocation of the nix tools.

     $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1

b) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Each options of a - c, so far the same error reappears.

I've also attempted your approach as clean installs.

yisraeldov · 2021-07-27T18:25:40Z

@purcell , Steve what is your current setup for getting things working on the M1 ?

domenkozar · 2021-08-28T17:47:36Z

Note that ghc builds as of today on master. More package fixes are pending in haskell-updates (including cachix).

domenkozar · 2021-08-28T17:48:53Z

Flake.nix needs to pass the correct system to

nix-darwin/eval-config.nix

Line 1 in a7492a8

{ lib, system ? builtins.currentSystem or "x86_64-darwin" }:

dhess · 2021-08-28T21:09:00Z

#317

shaunsingh · 2021-10-05T01:24:01Z

Anyone have a sample darwin-configuration.nix setup for m1 that they would like to share? Its hard to follow along with the thread, and I'm quite new to nix-darwin

lilyball · 2021-11-06T00:33:05Z

In order to get this working I had to darwin-rebuild switch with extra-platforms = x86_64-darwin aarch64-darwin set first, before I could then build any x86_64 packages (pkgs is aarch64-darwin). Is there any way to avoid this two-phase configuration? I've got this machine setup now, but I don't want to run into this again the next time I set up a new machine.

srid · 2021-11-23T15:07:54Z

Anyone have a sample darwin-configuration.nix setup for m1 that they would like to share? Its hard to follow along with the thread, and I'm quite new to nix-darwin

@shaunsingh Add this to your darwin-configuration.nix during install:

  nix.extraOptions = ''
    extra-platforms = aarch64-darwin x86_64-darwin
    experimental-features = nix-command flakes
  '';

masaeedu · 2022-01-19T17:03:46Z

@domenkozar in your comment here you mention that:

GHC has been fixed just last week, with now over 25000 packages building on aarch64-darwin.

Presumably this fix is for the "cannot coerce null to a string" bug. Would you happen to recall what PR/commit introduced this fix and what the problem was (I'm wondering if I can backport the fix to an older nixpkgs). Thanks in advance.

domenkozar · 2022-01-20T11:03:12Z

This was related to signing and process getting killed, so your error message is something different/new.

yacinehmito · 2022-11-11T10:17:04Z

Is there still an issue with native M1 support? I installed nix-darwin recently on an M1 and I seem to get everything on aarch64-darwin without having done anything special.

purcell · 2022-11-13T14:17:17Z

Agree, I'll go ahead and close this: I opened it mainly to share info, and there's indeed no current issue on these machines.

dotkrnl mentioned this issue Jun 15, 2021

Native support for Apple Silicon NixOS/nixpkgs#105026

Merged

21 tasks

lloeki mentioned this issue Jun 19, 2021

Support for Apple Silicon (aarch64-darwin) NixOS/nixpkgs#95903

Closed

antifuchs mentioned this issue Dec 3, 2021

Support M1 machines cmacrae/emacs#3

Closed

purcell closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Using the new native M1 support #334

Using the new native M1 support #334

purcell commented May 28, 2021 •

edited

Loading

hlolli commented May 29, 2021

LnL7 commented May 29, 2021

hlolli commented May 29, 2021

hlolli commented May 30, 2021

antifuchs commented Jun 10, 2021 •

edited

Loading

lloeki commented Jun 18, 2021 •

edited

Loading

LnL7 commented Jun 18, 2021

lloeki commented Jun 19, 2021 •

edited

Loading

shaunsingh commented Jun 22, 2021 •

edited

Loading

BaoPham92 commented Jul 5, 2021 •

edited

Loading

yisraeldov commented Jul 27, 2021

domenkozar commented Aug 28, 2021

domenkozar commented Aug 28, 2021 •

edited

Loading

dhess commented Aug 28, 2021

shaunsingh commented Oct 5, 2021

lilyball commented Nov 6, 2021

srid commented Nov 23, 2021 •

edited

Loading

masaeedu commented Jan 19, 2022

domenkozar commented Jan 20, 2022

yacinehmito commented Nov 11, 2022

purcell commented Nov 13, 2022

Using the new native M1 support #334

Using the new native M1 support #334

Comments

purcell commented May 28, 2021 • edited Loading

hlolli commented May 29, 2021

LnL7 commented May 29, 2021

hlolli commented May 29, 2021

hlolli commented May 30, 2021

antifuchs commented Jun 10, 2021 • edited Loading

lloeki commented Jun 18, 2021 • edited Loading

LnL7 commented Jun 18, 2021

lloeki commented Jun 19, 2021 • edited Loading

shaunsingh commented Jun 22, 2021 • edited Loading

BaoPham92 commented Jul 5, 2021 • edited Loading

yisraeldov commented Jul 27, 2021

domenkozar commented Aug 28, 2021

domenkozar commented Aug 28, 2021 • edited Loading

dhess commented Aug 28, 2021

shaunsingh commented Oct 5, 2021

lilyball commented Nov 6, 2021

srid commented Nov 23, 2021 • edited Loading

masaeedu commented Jan 19, 2022

domenkozar commented Jan 20, 2022

yacinehmito commented Nov 11, 2022

purcell commented Nov 13, 2022

purcell commented May 28, 2021 •

edited

Loading

antifuchs commented Jun 10, 2021 •

edited

Loading

lloeki commented Jun 18, 2021 •

edited

Loading

lloeki commented Jun 19, 2021 •

edited

Loading

shaunsingh commented Jun 22, 2021 •

edited

Loading

BaoPham92 commented Jul 5, 2021 •

edited

Loading

domenkozar commented Aug 28, 2021 •

edited

Loading

srid commented Nov 23, 2021 •

edited

Loading