!ayCRiZriCVtuCUpeLp:nixos.org

Nix Cross Compiling

579 Members
126 Servers

You have reached the beginning of time (for this room).

SenderMessageTime
3 Dec 2025
@hsngrmpf:matrix.orgDavHauI'm not sure, because maybe someone wants to use it in a non-cross scenario, and then they cannot, because it is null.03:42:34
@xin:xiny.lixin joined the room.19:29:39
4 Dec 2025
@i-am-logger:matrix.orgIdo Samuelson joined the room.01:45:01
@onur-ozkan:matrix.orgonur-ozkan joined the room.04:20:24
@hsngrmpf:matrix.orgDavHau How could we prevent contributers from including setuptools-rust as a native build input and force the usage of the setuptoolsRustBuildHook instead?
I've been seeing this multiple times already and it always breaks cross. 		06:07:26
@hsngrmpf:matrix.orgDavHau The checkBinaryArchHook unfortunately isn't gonna cut it because we don't cross build in CI the trigger the failure. 06:08:07
@hsngrmpf:matrix.orgDavHau Or would it make sense to improve setuptools-rust, so it pulls in the hook automatically? 06:11:35
@symphorien:xlumurb.eusymphorienadd the hook as propagated build input on setuptools-rust ?07:11:40
@hsngrmpf:matrix.orgDavHauI guess07:36:55
@hsngrmpf:matrix.orgDavHaufixed: https://github.com/NixOS/nixpkgs/pull/46779612:34:19
@hsngrmpf:matrix.orgDavHauOOps wrong link. Here: https://github.com/NixOS/nixpkgs/pull/46781712:34:45
@hsngrmpf:matrix.orgDavHauWhen will we add a cross package set to hydra BTW?13:06:37
@hsngrmpf:matrix.orgDavHauIt is kind of tiring to fix the same stuff over and over again. Broken cross builds should be a blocker in CI. Too much dev power is wasted on this.13:09:30
@k900:0upti.meK900We have some13:24:33
@k900:0upti.meK900It can't block all the builds13:24:41
@k900:0upti.meK900 That would break very badly 13:24:52
@nicolas-goudry:matrix.orgNicolas Goudry joined the room.14:10:37
@nicolas-goudry:matrix.orgNicolas Goudry

Hi there, I’m posting here (maybe wrong room, dunno) because I’m having an issue with compiling an aarch64-linux package from a darwin remote builder.

To further explain, I've set up the darwin.linux-builder on an M4 Macbook with the goal of being able to build aarch64-linux packages as I don't have any real aarch64-linux machine lying around.

After following the steps from the manual, I have an aarch64-linux builder VM running and have updated the Mac Nix conf with the following:

extra-experimental-features = nix-command flakes
build-users-group = nixbld
extra-trusted-users = nicolas
builders = ssh-ng://builder@linux-builder aarch64-linux /etc/nix/builder_ed25519 8 - - - c3NoLWVkMjU1MTkgQUFBQUMzTnphQzFsWkRJMU5URTVBQUFBSUpCV2N4Yi9CbGFxdDFhdU90RStGOFFVV3JVb3RpQzVxQkorVXVFV2RWQ2Igcm9vdEBuaXhvcwo=
builders-use-substitutes = true

When I try to build the package, after a few seconds I get the following error: error: creating pipe: Too many open files. I can see the remote builder is used from the brief log messages. Restarting the build does continue the build where it left (well, the built/retrieved dependencies are in the remote store so that's normal) so I guess that if I run the build enough times, it will end up producing the final build output, but it's quite annoying in the meantime.

I looked around a bit (surely not enough) but the only resources I found were referring to systemd. Since MacOS is using launchd, this is not of any help to my issue, or so I think. It's unclear if the error is from the local host or the remote builder.

Does anyone has an idea as to how to fix this?

14:27:15

Show newer messages

Back to Room ListRoom Version: 6