IRC channel logs

2021-04-01.log

back to list of logs

***lukedashjr is now known as luke-jr
<stikonas>so I think we can get to automake-1.15
<stikonas>which is probably enough for almost everything
<stikonas>automake-1.16 is a bit tricker...
<stikonas>seems to need perl 5.8 for something
<stikonas>which is doable of course but extra work
<OriansJ`>pder: mescc-tools are in state for a stage0-posix spin; M2-Planet just needs me to do a trivial replace of file_print with fputs and update the checksums accordingly. M2libc needs to add fputs to $arch/Linux/bootstrap.c as the goal for the next release is be more C standard.
<OriansJ`>After that the only work remaining is expanding M2libc to take meslibc's place and porting efforts.
<OriansJ`>bauen1: I think the chroot requirement for the kernel is unlikely to be needed until after guile 3.x is bootstrapped and at that point GCC should be able to bootstrap linux for us. Then we can just have a standard Guix system image be the final piece built.
<stikonas>OriansJ`: we don't need guile anymore for GCC
<stikonas>I found a way to build GCC without autogen
<stikonas>although, with guile we can do it a bit better
<stikonas>and it's also useful for guix
<OriansJ`>stikonas[m]: honestly I was only thinking of guile for allowing us ot punt the later work to Guix
<OriansJ`>but I do like GCC without autogen
<OriansJ`>hopefully 4.7.4 (I think that is the last version that can be built with a C compiler)
<stikonas[m]>Well, for 4.7.4 we should build autogen
<stikonas[m]>Since we need to build quite a bit more of GCC
<stikonas[m]>G++, libstd++, etc...
<stikonas[m]>Anyway, like you said, now it's not a question of whether we can do it, just have to do a few steps
<OriansJ`>and the big problem becomes what architectures do the versions we can bootstrap are able to run on.
<OriansJ`>as PowerPC64el, RISC-V and etc probably are not supported by most of them.
<stikonas[m]>Indeed...
<pder>stikonas, I was looking at building binutils 2.18 and it needs autogen as well
<gforce_de1977>stikonas: /dev/console is created by the automtic included initramfs.cpio which a normal kernel always has: https://github.com/bittorf/kritis-linux/blob/main/minilinux.sh#L2085
<fossy><stikonas> well, the alternative would be not to run qemu but run CI in chroot mode...
<fossy>dont like this cause of future kernel work
<fossy>I am amenable to upkg tho
<fossy>this looks interesting
<fossy> https://gitlab.com/bztsrc/posix-uefi
<stikonas>fossy: by the way, I'll also have to fix binutils, pder noticed autogen in newer binutils, but it's the same in older
<stikonas>fix is the same though (don't use top-level configure)
<stikonas>fossy: so posix-uefi then can act as bootstrap kernel?
<stikonas>it looks very minimal though
<stikonas>might be enough to run M2-Planet though
<stikonas>also I think creating binaries for it needs extra tools (ld at least)
<fossy><stikonas> fossy: so posix-uefi then can act as bootstrap kernel?
<fossy>maybe
<fossy>Not yet
<fossy>It would be some work
<stikonas>yeah, I was talking about potentially, not right now...
***nckx is now known as Thunderbi
<fossy>stikonas: before doing guile, i noticed that guile needs very recent automake, so i am doing "proper" perl now (i.e. using ./Configure)
<stikonas>very recent?
<stikonas>like which version?
<fossy>1.16.2
<stikonas>oh, really?
<fossy>yeah :\
<stikonas>I thought 1.12 is enough, we have 1.15
<fossy>i can probably hack it to use an older one
<fossy>but new perl would be nice anyways
<stikonas>so you'll try ot build perl's configure using their system?
<fossy>yeah
<stikonas>hmm, what was it called...
<fossy>metaconf
<fossy>ig
<fossy>metaconfig
<stikonas>in principle I can get 1.16.2 working too
<stikonas>the only complaint I got was perl 5.8 is needed
<fossy>i think we can probably do a big-ish jump
<stikonas>but if we can build metaconf, then ok...
<stikonas>yeah, if we can then alright
<stikonas>I'm still trying to get binutils building
<fossy>well metaconfig is itself in perl lol
<fossy>:s
<stikonas>well, yeah...
<stikonas>not sure which perl is needed...
<stikonas>whether 5.6 is enough...
<fossy>it says in the README 5.004
<stikonas>if not, 5.8 should be easily buildable
<stikonas>ok
<fossy>how true that is is a good question
<fossy>also new perls are very nice, they have one regen script
<fossy>perl regen.pl
<stikonas>yeah, I saw
<fossy>and it does everything
<stikonas>although, they are quite picky about bison version
<fossy>hm, true
<fossy>i will see how i go with that
<stikonas>so might need really new perl
<stikonas>I'm getting some strange problems when trying to build binutils witout top level configure :(
<stikonas>no idea why...
<fossy>e.g.?
<stikonas> /after/include/musl/bits/alltypes.h:148: error: identifier expected
<fossy>huh
<stikonas>yeah...
<stikonas>in musl...
<fossy>is that a gcc problem maybe?
<stikonas>that's tcc
<stikonas>it's way before gcc
<fossy>oh
<fossy>does it use autogent oo
<stikonas>back to binutils 2.14
<stikonas>yeah...
<fossy>oh
<stikonas>same stuff coppied from gcc
<stikonas>more or less
<fossy>gross
<stikonas>there are even references to xgcc there
<stikonas>it should be possible to build everything using subdirectory configures and makes
<fossy>put an issue up so i don't forget
<fossy>yeah it should
<fossy>which directory is that error in
<stikonas>oh, you already have an issue
<stikonas> https://github.com/fosslinux/live-bootstrap/issues/82
<fossy>oh i meant to say
<fossy>i put an issue up so i don't forget
<fossy>not for you to lol
<stikonas>oh ok
<fossy>sorry that was very vague
<stikonas>it's actually the very first file we build
<stikonas>that is very strange
<stikonas>exactly the same command here https://api.cirrus-ci.com/v1/task/5979828307361792/logs/run.log
<stikonas>succeeded
<stikonas>maybe some header file is created somewhere
<stikonas>or maybe configure order matters...