00:01 <samueldr> whew, turns out dropbear needed some LD_LIBRARY_PATH massaging + libnss libs

00:02 <gchristensen> nice...

00:02 <gchristensen> sphalerit / sphalerite ping

04:38 <sphalerit> gchristensen: pong

05:44 <sphalerit> andi-: nice, did you order a devkit?

05:48 <andi-> sphalerit: nah, only thought about it a few days ago. I'll try to get the software packaging done until then. I can imagine packaging the KDE/GNOME kind they are producing will already be a small challenge. After all we could probably fallback to a Gemini for initial testing of the stack. Not the same CPU (I think) but phone-like aarch64. In January my device is supposed to arrive..

05:49 <sphalerit> Yeah I haven't ordered mine yet

05:50 <sphalerit> I should have a fair bit of free time this summer, so if you want to work together on it let me know :)

05:50 <andi-> Sure :)

05:52 <andi-> I also have the need for proper cross compilation.. I just yesterday had to fix an older system (xilinx pynq board half FPGA/half arm core).. Will have to see how I can fit the custom u-boot and custom kernel into nixos.. :/ also just 512MB of RAM piratically forcing me to crosscompile

05:54 <elvishjerricco> andi-: Cross compiling perl stuff has been the main problem for me with cross compiling nixos

06:13 <andi-> Its by far my number one concern regarding embeddedish (RPI and those) devices: the memory footprint of running nix :/

10:27 <sphalerite> yeah… and memory aside, building stuff on them isn't fun either

12:26 <gchristensen> sphalerite: ping

15:00 <sphalerite> gchristensen: pong :x

17:04 <andi-> sphalerite: yep... must look into cross compiling again.. a few months ago (5?) I tried to do it but I just couldn't figure out how... :/

17:05 <sphalerite> basically pass crossSystem to nixpkgs

17:05 <sphalerite> let nativePkgs = import <nixpkgs> {}; crossPkgs = import <nixpkgs> {crossSystem = pkgs.lib.examples.foo;}

17:06 <sphalerite> not sure about cross-compiling nixos, but I do think shlevy got that working a while back when he was doing the risc-v stuff

17:06 <andi-> ok

17:06 <andi-> i'll try to at least try to emulate my future hardware (as close as I can get)

17:06 <andi-> should be feasible to boot it up on qemu... With out graphics probably

17:07 <samueldr> elvishjerricco got aarch64 nixos working, the sd-image for qemu can be cross-compiled

17:07 <samueldr> (not upstreamed yet)

17:07 <elvishjerricco> samueldr: Yea, I have that working too

17:07 <samueldr> I mean that YOU got it working :)

17:08 <elvishjerricco> Oh, thought you were saying you fixed the stuff on master :P My GitHub repo was on a pretty old nixpkgs

17:08 <samueldr> tried to cross-compile my device kernel, but it needs gcc6 which doesn't build using gcc7 and I'm a bit stumped at how to get cross gcc6 built using system's gcc5 or gcc6

17:09 <elvishjerricco> Seems like GCC 7 broke a lot of builds. Is that typical of major GCC version changes?

17:09 <samueldr> kind of

17:09 <samueldr> it's either undefined behaviour changing

17:09 <samueldr> or more warnings, with -Werror

17:09 <samueldr> in the case of gcc6. it seems to be (at least) a new warning

17:10 <andi-> IMO the problem is also not eased by us just disabling errors.. We should submit changes to upstream and ask them to fix it :/ I remember two motnsh trying to work on the gcc7 migration...

17:10 <samueldr> as for my kernel, I don't know, it builds, but doesn't work using gcc7, fine with gcc6

17:11 <samueldr> (but it's a crusty old 3.10 from asus)

17:11 <samueldr> (so it's kind of expected stuff's broken)

22:22 <elvishjerricco> linux-next worked flawlessly out of the box on my rpi 3 b plus... Wish I hadn't wasted time fixing things up for the linux-rpi kernel :P

22:50 <elvishjerricco> Oh wait, I used the old image. Never mind, it is not working out of the box :P