<OriansJ>siraben: I'll review your pull request later tonight after I finish moving knight-native to M2libc <OriansJ>and to delete a javascript file from talk_notes so github stops sending me crap updates about how it has vulnerable dependencies. <siraben>OriansJ: I think you can disable those updates <fossy>stikonas[m]: i am midly confused about flex-2.5.11 <stikonas[m]>fossy, I initially wrote it to rebuild itself but then added newer flex, I'm considering removing it in my flex 2.6.4 work <stikonas[m]>Main2 would be uses for 2nd pass if we want to build unpatched lex <stikonas[m]>I'm also looking at moving m4 after musl, the we can drop that patch but I got linking errors, so need to investigate more <fossy>please do remove one and clean that up in flex 2.6.4, tis rather confusing <stikonas[m]>Maybe because the binary overwrites itself... I'll replace it with install <gforce_d11977>stikonas[m]: it *is* a lowram-issue, i'am pretty sure, my QEMU used only 1G, will fix and repeat, sorry <stikonas[m]>Yeah, we need more ram, especially as we add more sources <gforce_d11977>(ok, qemu runs again, uploads to some URL... - i'am AWK, cu later) <gforce_d11977>(ok, qemu runs again, uploads to same URL... - i'am AWK, cu later) <marusich>dftxbs3e, dongcarl, the issue is fixed. However, I think coreutils-final doesn't build; I'll probably open a report about that one next.. <marusich>I'm sure something else won't build... If you find something that is broken, please open a bug report about it so we can track which commits fix which problems, etc. <stikonas>fossy: so I think musl is ready to merge? <gforce_d11977>i can fire a x86_64 QEMU to see if this changes something, shouldt i? <stikonas>it migth be some of the patching that we do... ***ChanServ sets mode: +o rekado_
***rekado_ is now known as rekado
<stikonas>gforce_d11977: still failed on x86_64... <stikonas>but I guess you'll have to investigate since only you can reproduce it <gforce_d11977>stikonas: this is just "./rootfs minikernel" - but i will look deeper and report. <gforce_d11977>stikonas: i have no idea what can be missing in the kernel...? let me dig a little bit <stikonas>I thought we wouldn't use floating exceptions... <stikonas>oh, it might be that musl has more requirements on kernel <stikonas>and your minikernel is now insufficient... <stikonas>at this stage in the bootstrap I think we'll not be running bootstrap kernel anymore once kernels are sorted out <gforce_d11977>now i have to find the CONFIG_SYMBOL which makes that happen <stikonas>ok, so musl requires more stuff from the kernel... <gforce_d11977>(i make progress finding to additional needed KERNEL_CONFIG_SYMBOLS, but the time needed for a compile-run-cycle is really, arrgggg!) <stikonas>oh, m4-1.4.4 also builds and unlike 1.4 it doesn't need patch... <stikonas>let's update it. It's also 10 years newer <stikonas>I couldn't get m4 working with musl though, something strange is going on with alloca. I was able to solve same problem in grep... <stikonas>but doesn't matter, we can build it with mes libc <stikonas>that's the final component in flex/bison bringup <stikonas>argh, bison is also struggling with that "alloca" symbol...