zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<DigitalKiwi>
mine already has that anyway :(
<DigitalKiwi>
why are computers so hard
FRidh2 has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
<Thra11>
Looks like llvm 3.9 has been removed from nixpkgs, but it's required for ghc-8.2.2-binary on aarch64 to work. ghc-8.2.2 is the start of the ghc bootstrap chain.
<Thra11>
Should we resurrect llvm39, or try to find a new ghc binary version to start our chain?
jamii has joined #nixos-aarch64
<Thra11>
(x86 uses ghc without llvm, so it isn't affected by having the wrong llvm version)
<jamii>
Hi, I'm trying to crosscompile a gtk app for aarch64 and running into some compile errors in gdk-pixbuf. I might just be doing this completely wrong.
<samueldr>
I don't know about ghc, so allow me dumb questions, Thra11
<samueldr>
how is it different on x86_64 and aarch64, and why can't we do the same on both?
<samueldr>
jamii: cross-compilation using nix/nixpkgs is a work-in-progress, the further away from the root base system packages, the more likely it is to break...
<samueldr>
... but don't necessarily let this discourage you from trying
* samueldr
looks at your log
<samueldr>
>> FileNotFoundError: [Errno 2] No such file or directory: 'ldd': 'ldd'
<jamii>
If using nix entire doesn't work, I would be content to just figure out how to get a crossplatform toolchain for gcc. I managed to build aarch64->aarrch64 gcc which means that there is presumably a x86->aarch64 somewhere on my laptop now :D
<samueldr>
that's the root cause of the failure, though, it looks like it comes from g-ir-scanner
<jamii>
I'm also happy to dig into the compiler error myself if there's a problem with crossbuilding gtk. I just wanted to make sure I wasn't cross-compiling wrong first.
<jamii>
I'm not even sure why it's trying to build all of gtk. I think I only need the header files on this system.
<samueldr>
from experience, sorry I don't have the knowledge to fix, all things gobject have been having issues with the nixpkgs cross-compilation harnesses
<DigitalKiwi>
isn't ghc likely moving to use llvm toolchain anyway?
<jamii>
samueldr: ok, fair enough, I'll avoid it
<DigitalKiwi>
due to windows shenanigans
<Thra11>
samueldr: GHC compiles Haskell code either directly to native code or using LLVM as a back-end. On x86, there is a choice of backends (native/llvm). On arm there's only one backend (llvm). However, most distros prefer the native backend where it exists (or at least they have in the past). So in theory you could go llvm-backend for all platforms, but I don't know if you might upset some x86
<Thra11>
users...
<jamii>
Do you happen to know how to refer to the x86->aarch64 gcc? If I can get the linker from that I can try the rust crosscompilation tools directly.
<samueldr>
my gut feeling with the current issue is that gobject-introspection needs to be patched to know about the cross-compiler-ldd when used in cross-compilation environment
<DigitalKiwi>
i don't even know if that's related; don't listen to me
<jamii>
I wonder if it would be easier to just build an aarch64 qemu image and compile in there.
<DigitalKiwi>
iiuc the llvm backend can often produce more optimized binaries at the cost of longer compile times
<Thra11>
DigitalKiwi: Interesting. Presumably the native backend has its advantages, otherwise they'd switch to llvm everywhere and save some complexity/maintenance
<Thra11>
While being homogenous across platforms might be nice, I suspect following upstream's lead (native on x86, llvm elsewhere) is probably less controversial.
<samueldr>
right, I see
orivej has joined #nixos-aarch64
<Thra11>
Also, I'm more interested in a relatively minor aarch64 fix that can go into 20.03 at this stage :)
<DigitalKiwi>
i think maybe thefloweringash opened an issue about it a few days ago
<simpson>
Thra11: "However, there is also one major disadvantage: @Phyx, our primary Windows contributor, is unable to contribute to LLD due to legal reasons. This is a very hard trade-off."
<samueldr>
though I haven't checked with the team there
<samueldr>
maybe for some odd reason they wouldn't whant that (though unlikely)
<ryantrinkle>
it looks like they already have a raspberry pi 2
<samueldr>
yeah
<samueldr>
if for some reason it's not desired, I was strongly thinking about having such a repo earmarked for sbcs
<ryantrinkle>
cool :)
<ryantrinkle>
well in any case the code will be somewhere
<ryantrinkle>
we can always shuffle it around
zupo has joined #nixos-aarch64
stiell has joined #nixos-aarch64
<stiell>
Hello. I'm trying to install NixOS on Raspberry Pi 4. Downloaded nixos-sd-image-19.09.2144.85548f2a131-aarch64-linux.img from Hydra, dd'd to a 16GB SD card, inserted into R-Pi and powered up. Not getting any output on serial, HDMI1 only shows the GPU firmware coloured splash screen. Tried boot_delay=1 in config.txt, same results. The same R-Pi boots Raspbian fine, and I can get serial output from it
<stiell>
through its /dev/ttyS0 once this has been enabled in raspi-config. Anything I'm missing?
<samueldr>
the raspberry pi 4 is not supported by the generic mainline-using aarch64 image yet