| 9 Jul 2023 |
 Alex | Oh dear, no ethernet in mainline either | 11:23:29 |
 Pratham Patel | :') | 11:23:47 |
| 10 Jul 2023 |
 trofi | artemis: RE your past problems with libtool cross-compiling on Gentoo. I think I found the issue: if you run nix itself in a containerized environment nix silently falls back into the mode without a sandbox enabled (due to a sandbox-fallback = true) and happily runs unsandboxed builds in /tmp. ALl the bianries in /usr/bin and whatnot are available to the builds and this impurity contaminates the environemtn with /usr/lib library search paths breaks the builds.
The easy way to check it is to set sandbox-fallback = false in /etc/nix/nix.conf, restart nix-daemon and try to build something. If it fails that means you have been using unsandboxed builds.
| 08:32:39 |
| trofi | I disabled sandbox fallback in the overlay with https://github.com/trofi/nix-guix-gentoo/commit/88050fcf0f3a11a7a6763494eda580b707be1267 and added a README entry to diagnose it: https://github.com/trofi/nix-guix-gentoo/commit/8109131192dc340e314d9e41159b176bfb5b82c8 | 08:33:40 |
| trofi | What environment did you use to run nix? Real machine, a VM or some container? | 08:34:20 |
 artemis | In reply to @trofi:matrix.org
What environment did you use to run nix? Real machine, a VM or some container? real machine, no VMs, no containers | 08:56:22 |
| artemis | also my /etc/nix/nix.conf already has `sandbox-fallback = false` | 08:58:48 |
| artemis | * also my /etc/nix/nix.conf already has `sandbox-fallback = false` without issue | 08:59:01 |
| artemis | * also my /etc/nix/nix.conf already has `sandbox-fallback = false` without issue. i dont know when i added that but it's been there | 08:59:53 |
|  @achnazoor:matrix.org joined the room. | 09:05:21 |
|  avnik joined the room. | 09:39:14 |
| trofi | Must be something else then (or a poisoned local cache when was built without a sandbox, before nix.conf tweaks) | 09:46:47 |
| artemis | how coud i clean local cache to ttest that theory | 10:41:41 |
| trofi | Good question. I would "uninstall" everything by cleaning all gc roots in /nix/var/nix/gcroots and run nix-xollect-garbage -d. | 10:56:09 |
| trofi | * Good question. I would "uninstall" everything by cleaning all gc roots in /nix/var/nix/gcroots and run nix-collect-garbage -d. | 10:56:33 |
| trofi | Alternatively you can `nix-build --check` all paths in the problematic closure. But it will require checking for false positives manually. | 11:00:46 |
| artemis | i will do the first option | 11:25:01 |
| 11 Jul 2023 |
| Alex | In reply to @alex:tunstall.xyz
I'm currently compiling with a few patches applied to try to fix the compilation problems without disabling DRM, since I'd really like to get working HDMI on my VF2.
I'll share the configuration if I'm able to get it working. Given the similarities between the two SBCs (and their respective Linux fork), it might work for the Star64 too. I've gotten Linux 5.15 to compile but it doesn't boot, doesn't log to journalctl, and doesn't output to HDMI, so I've folded and ordered the necessary hardware to debug over serial. | 10:41:37 |
