<thefloweringash>
FWIW I’ve been using latest mainline (+ patches from arch) on my rock64 since 19.03.
<lopsided98>
I'm just switched to mainline U-Boot, but I was previously using the one in nixpkgs. I will submit a PR that replaces the downstream U-Boot with mainline in nixpkgs once I finish testing my RockPro64
orivej has quit [Ping timeout: 276 seconds]
h0m1 has quit [Ping timeout: 250 seconds]
h0m1 has joined #nixos-aarch64
<lopsided98>
I have blob free mainline U-Boot working on my RockPro64
<samueldr>
I have some exciting and annoying news
<samueldr>
got a new phone to replace my old one, like personal bought for me phone
<samueldr>
(so I can actually make the addison the hybrid target)
<samueldr>
(but that's not the news)
<samueldr>
the new phone supports eDP out on type-c
<samueldr>
and it looks like that, in android, it's done through the kernel DRM
<samueldr>
so it's likely not something spooktastic made-for-android
<clever>
betaboon: what does nix-build print out when failing? what are the contents of /etc/nix/machines ?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<gchristensen>
oh no my new fancy rust code doesn't compileon aarch64
<gchristensen>
spooky it is building the second try
zupo has joined #nixos-aarch64
<betaboon>
I'm trying to build `android-device` of the mobile-nixos demo. it just runs into `Building with crossSystem?... -> we are` and then fails with the regular aarch64-cross-build failures. as if it doesnt even try
<clever>
betaboon: what are the contents of /etc/nix/machines ?
<clever>
error: attribute 'targetPlatform' missing, at /home/betaboon/src/nix/nixpkgs/pkgs/development/tools/build-managers/meson/default.nix:98:17
<clever>
betaboon: the error has nothing to do with build machines
<betaboon>
clever: but that is the error it fails on due to trying to crossbuild
<betaboon>
clever: exactly
<clever>
98 system = '${targetPackages.stdenv.targetPlatform.parsed.kernel.name}'
<clever>
betaboon: i think your nixpkgs rev isnt compatible
t184256 has left #nixos-aarch64 ["Error from remote client"]
<betaboon>
clever: that's just due toe crosscompiling
<clever>
betaboon: it hasnt even reached the phase where it tries to connect to the community box
t184256 has joined #nixos-aarch64
<betaboon>
clever: thats current master
<betaboon>
on nixpkgs-unstable it fails in the same way
<clever>
betaboon: are you on a branch of mobile-nixos?
<betaboon>
same for nixos-unstable. and as far as i understood the documentation of mobile-nixos it is supposed to be build against nixos-unstable for now
<betaboon>
clever: I'm on mobile-nixos master
<clever>
- The option definition `services.xserver.displayManager.slim' in `<unknown-file>' no longer has any effect; please remove it.
<clever>
for me, it fails even harder
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<clever>
2019-11-29 18:35:56 < betaboon> clever: I'm on mobile-nixos master
<betaboon>
clever: ehm. yeah sorry that was unclear. master + that commit . sorry
<clever>
betaboon: looks like youll need samueldr to help, it seems to fail in 3 different ways, on every nixpkgs rev i test
<betaboon>
yeah. seems like it. i was under the impression that the meson error was due to the evaluation being run without the remote-builder. guess that was wrong
<clever>
it would clearly say i am x86, but need aarch64