<stikonas>will be easier to rebuild some autotools stuff, i.e. that will renanable autoreconf or shipped ./bootstrap scripts ***puckipedia is now known as puck
***qyliss- is now known as qyliss
<fossy>stikonas[m]: unfortunatley github is fking me over and i cannot currently login. however #60 and #59 are good, you can merge. <fossy>kexec-tools is progressing, binary that runs and produces help text. however it is unable to load a kernel <fossy>also, btw, this will mean our builds require an i686 seed kernel (compat x86_64 support is non-existant) ***janneke_ is now known as janneke
<stikonas>cause I'm also thinking about whether it's worth rebuilding coreutils <stikonas>well, env is needed by libtool, so we definitely need it sooner <stikonas>but if we have new autoconf, maybe it's worth just building full coreutils 6? <pder>is there anything in coreutils 6 that is not in 5? <stikonas>well, I only said 6 cause it's already in sources dir... <stikonas>it's just more of rebuilding coreutils with autotools / good musl <pder>my only thought is maybe we wait to upgrade coreutils until after we have gcc? <pder>do you think the next step is getting newer autoconf and automake working? <stikonas>well, automake probably can be built immediately too <stikonas>I think it has lower dependency requirements <stikonas>probably can just quicker to new versions <stikonas>autoconf I guess will be jumping either each version or occasionally skipping one or two <stikonas>pder: after that I think we need to rebuild sed and gawk <stikonas>and maybe build newer tar, this one is really old and still runs on mes <stikonas>if possible, we can just bootstrap all the way to newest autoconf/automake ***qyliss_ is now known as qyliss
***puckipedia is now known as puck
***pgreco_ is now known as pgreco
<stikonas>pder: so I briefly checked automake/autoconf, we might need to manually rebootstrap at least some newer versions of automake... <stikonas>older versions of automake often don't work on newer automake... <stikonas>pder: so I have most of the libtool working, but there is a slight problem <stikonas>I think our old bash is insufficient for it <stikonas>but I think we can move bash earlier, maybe with some workarounds "size=true and ar=tcc -ar"... <stikonas>actually, for ar I migth need a wrapper file anyway <pder>at what point did you need libtool? <stikonas>I tried building newer bash, that itslelf works <pder>you need something newer than 3.2.57? <stikonas>I get errors like /after/bin/autoheader-2.13: eval: line 140: unexpected EOF while looking for matching `"' <pder>can you run that for sym.. line in the shell? <stikonas> /bin/busybox sh /after/bin/autoheader-2.13 completed successfully <pder>maybe try tracing with /after/bin/bash -x /after/bin/autoheader-2.13 <stikonas>since we can't use new enough autotools... <stikonas>or maybe I can use providded bootstrap.sh... <stikonas>otherwise I need to deal with converting it to config.h <stikonas>fossy: would you be fine with not using bash build harness for sed? <stikonas>it's much simpler to just run a script that we already wrote for kaem <stikonas>(alternative would be to go for older sed) <stikonas>but I don't think downgrading is a good idea <stikonas>well, maybe I can convert kaem script to Makefile...