<ldhacker[m]>
The dreaded program crash for the eclipse updater lol
alexanderwillner has quit [Quit: Idle for 30+ days]
Jamie[m] has quit [Quit: Idle for 30+ days]
ts170[m] has quit [Quit: Idle for 30+ days]
roxfan2 is now known as roxfan
vimal has quit [Remote host closed the connection]
vimal has joined #asahi-dev
zopieux has quit [Ping timeout: 272 seconds]
zopieux has joined #asahi-dev
sickdelan has joined #asahi-dev
sickdelan has quit [Quit: Leaving]
frode_0xa has quit [Ping timeout: 240 seconds]
thestr4ng3r_ has joined #asahi-dev
thestr4ng3r has quit [Ping timeout: 276 seconds]
VinDuv has joined #asahi-dev
hthh_ has quit [Ping timeout: 272 seconds]
hthh_ has joined #asahi-dev
rotbot9k has joined #asahi-dev
acelogic has joined #asahi-dev
<bastilian>
If I want to build m1n1, I should be able to do that in a virtual machine on an M1, or? Or should it also build normally on macOS as well?
<svenpeter>
If you install a aarch64 tool chain you can do it from macOS
<roxfan>
you probably need toolchain to build the kernel anyway
<bastilian>
oh, right to configure all the kernel modules.
<roxfan>
maybe homebrew has one
<bastilian>
Would it make sense to add a virtual machine (maybe with a Vagrantfile) or a container definition for developers to bootstrap a build environment? Would that even work... I'm not a big compiling expert. :D
<j`ey>
bastilian: The build env for the kernel is pretty minimal, make, flex/bison, libelf and a aarch64 toolchain