IRC channel logs

2021-05-05.log

back to list of logs

<OriansJ>good news is I got ungz.c into shape for M2-Planet+M2libc builds: https://paste.debian.net/1196321/ bad news is it isn't functional yet but I should get the bugs out before the weekend with luck.
***attila_lendvai_ is now known as attila_lendvai
<melg8>Now i'm really sad panda. I've managed to build touch from coreutils 8.1, but only to see it saying "touch: setting times of `/after/gmp-6.2.1/build/gmp-6.2.1/mpn/zero_p.c': Function not implemented" - when calling with --no-dereference flag on links.
***stikonas_ is now known as stikonas
<stikonas>well, you can use gdb to find out what is causing that message
<gforce_d11977>stikonas: can you say, from which step is this commandline I see in logoutput?: /after/bin/mes --no-auto-compile -e main /after/bin/mescc.scm -- -o mes-tcc -L /after/lib tcc.s -l c+tcc
<stikonas>that's tcc-0.9.26
<gforce_d11977>stikonas: thank you....it eats much RAM, around ~450mb, i was just wondering
<stikonas>well, it's possible to reduce RAM usage there but with some disadvantages
<stikonas>so probably not worth it
<stikonas>tcc is built as "unified" source
<stikonas>all in one .c file instead of individual c files
<melg8>@stikonas - is it worth trying to fix coreutils 8.1 (2009) - or just try to build something like busybox and use it as a replacements for old/not fully correctly working coreutils-5/6 versions?
<stikonas>hmm, not sure now
<stikonas>by the way, why 8.1 ?
<stikonas>busybox was tricky when we looked earlier in bootstrap, might be easier now that we have GCC
<stikonas>but I think coreutils should work too
<stikonas>but I would go with something newer than from 2009...
<melg8>8.1 because it is first release with --no-dereference flag - using it i can fix dates on links with touch
<stikonas>I would go with newest possible version
<stikonas>which at this stage in bootstrap often means the latest version
<melg8>okay
<melg8>and.. all tools? not just touch?
<stikonas>older versions make sense when we need some something simple (e.g. compiler or libc are limited)
<stikonas>melg8: yeah, building all new coreutils would be a good idea
<melg8>okay, i'll try it then) thanks for guidance
<gforce_d11977>melg8: I understand your need for a working touch. but I would better go an path the filesystem/VFS layer for constant (or monotonic raising) timestamps. this should knock out possible differences in our builds, at least it gives a better feeling where we dont needed to search for needles anymore.
<gforce_d11977>"patch the filesystem"
<gforce_d11977>melg8: maybe you can go a shorter way by doing your own touch.c with a hardcoded timestamp
<gforce_d11977>melg8: than you can just do: find /after -type f -exec mytouch {} \n;
<gef>live from the field: I finally decided to abandon my vain attempt to build over a centos distro (don't ask why, I just tried that), switched over to debian:10.9 and now the bootstrap appears to build fine: https://gitlab.com/bootstrappable/live-bootstrap-ci/-/pipelines ; famous last words... we'll soon know what that really means, it's building tcc/0.9.26 via mescc, right now. You've been Warned: builds are in progress...
<xentrac>congrats!
<gef>lol... now, I hit a buffer limit, like this I may never find out why it will fail :-p
<gef>24782 Job's log exceeded limit of 4194304 bytes.
<gef>24783 Job execution will continue but no more output will be collected.
<melg8>Okay, for coreutils 8.32 we need "Perl v5.8.0 required--this is only v5.6.2, stopped at ./man/help2man line 23."
<xentrac>melg8: sounds easy to fix
<melg8>suggestions are welcome) i'm new to this stuff)
***luke-jr- is now known as luke-jr
<xentrac>well, I don't actually know what features were added between 5.6 and 5.8 (or 5.008 as we would've said in the old days)
<xentrac>but I don't think they were very profound, so hacking help2man to not use them would probably be pretty easy
<xentrac>line 23 probably says "use 5.8.0;" and you could just comment that out and see what else breaks
<stikonas>or laternatively wait until newer perl is available
<stikonas>which should be soon
<melg8>about perl, who is doing that? and which version?
<stikonas>melg8: fossy, latest version
<stikonas>but he is a bit busy with exams, so it will take some time
<melg8>okay, thanks! because i've started load of perl 5.10 - for test
<stikonas>not worth duplicating the effort I think
<stikonas>since fossy mostly got it working
<stikonas>and perl is somewhat complicated
<stikonas>with quite a few pregenerated files
<stikonas>and very unusual build system
<stikonas>it uses metaconfig to create ./Configure script and metaconfig is itself written in perl
<melg8>i've tried busybox today - it's complaining about linux headers in one setup, and about invalid detected size
<melg8>At least i now more familiar with build system and steps to add packets
<Hagfish>it sounds like you're really getting to grips with things, that's great!
<fossy>It works I just need to do checksums but I wont be very responsive to review so better to wait until after exams
<fossy>melg8: ive already done Perl 5.10 ill push the branch this arvo so you can look if you like
<fossy>afternoon
<xentrac>arvo?
<xentrac>melg8 fell off