IRC channel logs

<fossy>stikonas: yeah, will get to making sure live-bootstrap works with git snapshots once i finish the full pregend files audit

<fossy>perl is quite annoying :\

<fossy>slowly making progress

<fossy>but analysing the use/require commands is unfortunately insufficient

<janneke>snuik: later tell stikonas: are you talking about 64bit? doing something like MES=mes-m2 ./pre-inst-env mescc -v -v -v -c scaffold/hello.c, I get "mescc: failed: M1 ..."; however somehow mescc still exits 0 for me now, but using something like https://paste.debian.net/1392498 you see something like ;;; ("status" 140733193388032)

<snuik>janneke, you have 1 message

<snuik>janneke, stikonas says: that mes seems to work with with M2-Planet 1.13.1. Have you somehow workarounded that miscompilation that you reported yesterday?

<snuik>Got it.

<janneke>snuik: later tell stikonas: i somehow cannot reproduce mescc exiting non-zero, even with the error message being displayed---but status should be 0 (and with mes-gcc or 1.12.0 _is_ 0) so something's fishy with 1.13.1+0.27.1

<snuik>Got it.

<janneke>snuik: botsnack

<snuik>ty!

<matrix_bridge><Andrius Štikonas> janneke: I also found that there is regression on x86_64 building tcc

<matrix_bridge><Andrius Štikonas> It used to be able to link tcc-mes

<matrix_bridge><Andrius Štikonas> Which was partially functional but not able to recompile itself

<matrix_bridge><Andrius Štikonas> Now mescc somehow crashes on linking

<matrix_bridge><Andrius Štikonas> Even though M1 seems to run fine

<matrix_bridge><Andrius Štikonas> Oh that might be the same problem you described

IRC channel logs

2025-08-20.log