IRC channel logs

2023-03-26.log

back to list of logs

<civodul>sarg: goggles-bot is back! :-)
<civodul>thanks for the heads-up
<lilyp>To think that verdi even made the log servers strike :)
<ekaitz>civodul: I managed to bypass the socket problem, but some others appear like some stuff is "long long long" because there's some type combinations here and there
<ekaitz>it also explodes because it doesn't know what ‘sigjmp_buf’ is
<civodul>weird
<civodul>i'm not familiar with the Bash code base but i'd be surprised if it cannot be cross-compiled to MinGW
<ekaitz>I have to dig deeper in the configure.ac then
<jpoiret>it might be an error with the cross-toolchain in general? ie. that it doesn't detect stuff properly while configuring
<ekaitz>jpoiret: that might be too. It's like it's detecting some stuff wrong like uint_max
<ekaitz>but the fact that it doesn't find sys/resource.h and the rest of the problems... IDK
<ekaitz>the bash-5.1/support/config.sub file mentions mingw but it stills try to load sys/resource.h which is not present in windows
<ekaitz>something is setting the config.h to say you have HAVE_SYS_RESOURCE_H
<civodul>jpoiret: do you happen to have a link to the commit/discussion about -ffrestanding in MiG (for which you added a patch)?
<jpoiret>i think i just cherry-picked it from https://git.savannah.gnu.org/cgit/hurd/mig.git/commit/?id=73fbf2504ae606dda81372701a67dad6fee0865e
<civodul>awesome, thanks!
<civodul>ACTION makes progress
<torari_real>i love guix
<torari_real>:-D
<torari_real>ijiii
<torari_real>jhhh
<torari_real>j
<mirai>is glibc@2.23 still relevant or is it "long gone" ?