IRC channel logs

<stikonas>GoogulatorMobile: is trap broken on old bash?

<GoogulatorMobile>ERR traps won't cascade into functions

<stikonas>I just get a scrolling wall of /external/distfiles # [TRAP - use Ctrl+D] /external/distfiles {repeated forever}

<GoogulatorMobile>that's odd

<GoogulatorMobile>What bootstrap mode are you in?

<stikonas>well, with preexisting kernel on real HW

<stikonas>so kind of baremetal but with Linux kernel

<stikonas>but I forgot to include external sources

<stikonas>and networking failed

<stikonas>and kernel is kind of same as in live-bootstrap (same config) but 64-bits and also with 32-bit ELF support enabled

<stikonas>since that's the only thing that can be booted on UEFI...

<stikonas>it's not possible to boot 32-bit efi binary there

<stikonas>(I think the only supported way of booting 32-bit OS would be 64-bit EFI stub that switches to 32-bit mode first)

<stikonas>fossy: I'm looking at #445. What happens if we compare just tars? are they different?

<Googulator>mid-kid: ran into some trouble with the step CTARGET=x86_64-bootstrap-linux-gnu EXTRA_ECONF='--with-sysroot=/usr/$CTARGET --enable-shared' EXTRA_EMAKE='MAKE=make MAKE+=libsuffix=../lib64' USE='-sanitize -openmp -fortran' emerge -O1 sys-devel/gcc

<Googulator>The directory that should contain system headers does not exist:

<Googulator> /usr/TARGET/usr/include

<Googulator>sounds like $CTARGET isn't correctly substituted

<Googulator>retrying with --with-sysroot=/usr/x86_64-bootstrap-linux-gnu instead

<Googulator>current progress on bootstrapping Gentoo on bare metal: https://gist.github.com/Googulator/86af97ed078eb9e6c18c6eb49e46c96d

<sam_>nice!

<Googulator>based on https://mid-kid.root.sx/git/mid-kid/bootstrap/src/branch/master/gentoo-2024/gentoo.txt

<sam_>I would probably link to that in there

<Googulator>added the missing config64 file (the 64-bit kernel config)

<Googulator>eventually it's gonna be a PR, but it's still in progress

<Googulator>the biggest change compared to mid-kid's qemu-based bootstrap (which relies on a 64-bit host kernel) is the pivot to a 64-bit kernel using the intermediate cross toolchain of LFS

<Googulator>also, all the LFS steps are expanded into code

<Guest991> https://greenhosting.am/db/get?id=320dfce8-f0b3-4f04-be70-be873b2c168d-f12a6f83-270d-4fd2-8c18-d679623b5f18#cf01ce20-0831-4a65-8ec3-1982bca79c21-adf6cc0d-db90-40df-aef9-0347df493a92

<Guest991>HI, I created ./rootfs.py -b -a x86 --cores 4 .img with this command to put it on bare-metal, then I ran it in bios and it gives this error, what solution would you suggest? error picture this link https://greenhosting.am/db/get?id=320dfce8-f0b3-4f04-be70-be873b2c168d-f12a6f83-270d-4fd2-8c18-d6796...

<fossy>the guyis back again

<fossy>Oh hes on another machine now

<fossy>I've seen that error before....

<fossy>is that the one we had after the m4 update??

<matrix_bridge><Andrius Štikonas> Hmm, could be

<Googulator>mid-kid: is 811M a reasonable size for /mnt/gentoo?

<Googulator>final compressed XZ size is 127M

<mid-kid>Yeah it compresses down to some 200MB

<mid-kid>Though the partition you run portage in should be bigger

<Googulator>200MB?

<Googulator>I ended up with 127 after compression

<Googulator>pre-compression, it was 811