!pbdtvoHxUGLhcEvnlu:nixos.org

Exotic Nix Targets

319 Members
98 Servers

Load older messages


SenderMessageTime
19 Sep 2021
@sternenseemann:systemli.orgsterni Alyssa Ross: any testing I should do for netbsd wrt https://github.com/NixOS/nixpkgs/pull/138560? 19:16:48
@qyliss:fairydust.spaceAlyssa Rosssternenseemann: uh, check a netbsd package with a man page compiles?21:48:32
@sternenseemann:systemli.orgsternieverything still builds except tic, libutil, man, compat; now checking if those are new regressions (comparing to master)22:10:08
28 Sep 2021
@ryantm:matrix.orgryantm joined the room.21:03:48
29 Sep 2021
@anodium:matrix.orgAndrea Pascal joined the room.02:45:11
6 Oct 2021
@kamadorueda:matrix.orgkamadorueda joined the room.03:12:30
@rosariopulella:matrix.orgRosario Pulella changed their display name from rosariopulella to Rosuavio.10:38:36
@rosariopulella:matrix.orgRosario Pulella changed their display name from Rosuavio to Rosario Pulella.10:45:01
8 Oct 2021
@r-burns:matrix.orgRyan Burns joined the room.19:02:19
9 Oct 2021
@kity:kity.wtfash (it/its) 🏳️‍⚧️ hey aaronjanse did you ever get around to fixing the rust custom platform issue? 03:49:17
@aaronjanse:matrix.orgaaronjanseAh sadly I haven't, sorry :(17:22:10
11 Oct 2021
@kity:kity.wtfash (it/its) 🏳️‍⚧️can nixos run on kernel 2.6?20:19:17
@kity:kity.wtfash (it/its) 🏳️‍⚧️for a xeon phi20:19:29
@qyliss:fairydust.spaceAlyssa Rossunlikely, I'd have thought20:38:07
@kity:kity.wtfash (it/its) 🏳️‍⚧️ from discussion in #nix:nixos.org it seems like glibc won't work but musl might. nix requires 3.8 for sandboxing, but the real blocker is systemd which requires 3.13 20:39:18
@kity:kity.wtfash (it/its) 🏳️‍⚧️just nix might work though, without sandboxing20:41:14
13 Oct 2021
@piper:lutris.engineeringPiper McCorkle (they/them or she/her)for those of you interested in SPARC & PowerPC (specifically ppc64le for now), I've started working on getting stdenv working on them: https://github.com/NixOS/nixpkgs/pull/14144804:06:51
@piper:lutris.engineeringPiper McCorkle (they/them or she/her)I've got the bootstrap tools done, now my Hydra cluster's churning away at seeing what else I need to tweak to get stdenv building04:07:11
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) * I've got the bootstrap tools built, now my Hydra cluster's churning away at seeing what else I need to tweak to get stdenv building04:07:17
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) * I've got the bootstrap tools built, now my Hydra "cluster" (it has two machines, but one is a Raspberry Pi so it's not working on this) is churning away at seeing what else I need to tweak to get stdenv building04:07:52
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) * for those of you interested in SPARC & PowerPC (specifically sparc64 and ppc64le for now), I've started working on getting stdenv working on them: https://github.com/NixOS/nixpkgs/pull/14144804:09:17
@piper:lutris.engineeringPiper McCorkle (they/them or she/her)

I'd love to hear y'all's thoughts on this:

https://github.com/NixOS/nixpkgs/pull/141448#issuecomment-941916618

W.r.t. bootstrap tools, see also #115406. These always get held up because it's hard to verify that the bootstrap tools are reproducible - how do you do that for native bootstrap tools on a platform we don't support yet? But on the other hand, cross-compiled bootstrap tools won't build stdenv because of #113977, so I'm not really sure how to proceed here.

Very true... it seems like there are three stages to building bootstrap tools:

  1. Cross-compile
  2. Native using cross tools
  3. Native using native tools

Maybe there should be more automation around building these - like, on a system with qemu-binfmt, you have a derivation that runs through all three stages, though that requires having a way to inject the newly built bootstrap tools into nixpkgs.

The first approach that comes to mind would be adding an argument to nixpkgsFun for the seeds, which probably wouldn't be a bad idea in general. I'd love to hear other people's thoughts on that though.

04:47:28
@r-burns:matrix.orgRyan BurnsI think it would be a good idea to try to produce the tarballs entirely on our hydra builders. That way there would be no "leap of faith" where the people in charge of tarballs.nixos.org have to upload an untrusted blob - they would just persist a trusted artifact direct from hydra.04:51:48
@piper:lutris.engineeringPiper McCorkle (they/them or she/her)Do the Hydra builders have qemu-binfmt? If not, we'll need to have a sparc64 and ppc64le buildbox to run those builds on.04:54:06
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) * Do the Hydra builders have qemu-binfmt? If not, we'll need to have a sparc64 and ppc64le (etc) buildbox to run those builds on.04:54:18
@r-burns:matrix.orgRyan BurnsUnfortunately not. But what about running the build inside a full-fledged VM? We already use VMs for the NixOS tests, and cross-compile entire NixOS systems for embedded hardware. I don't think it would be too much of a leap to cross-compile a testing VM and use it to bootstrap our exotic platforms.04:56:12
@piper:lutris.engineeringPiper McCorkle (they/them or she/her)True, we could do that! Though that means we need to get a NixOS system working before being able to add that platform.04:58:02
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) I wonder what the hurdles would be to getting qemu-binfmt added to the build boxes, that seems like a more elegant solution than a VM and it would mean running it locally would be as easy as nix build (as long as you have qemu-binfmt or a remote builder for the arch) 05:20:57
@r-burns:matrix.orgRyan BurnsMaybe a question for https://github.com/NixOS/nixos-org-configurations/?05:34:04
@piper:lutris.engineeringPiper McCorkle (they/them or she/her) Looks like they have a Matrix room (#infrastructure:nixos.org ), asked there 05:37:59

Show newer messages


Back to Room ListRoom Version: 6