<spk121>If it hasn't been done already, someone needs to make a bad presentation joke about Guile and Star Wars and use the phrase "You repl scum.". <ecraven>dsmith-work: I just built the epub from the 2.2 release tarball, fine enough ;) thank you! ***_zxq9_ is now known as zxq9
<sneek>wingo, stis says: it looks like it is not possible to move segments when removing some of them due to references in the code in order to compact. <sneek>wingo, stis says: what to do due to this, just clear the bytes? - that would help at least in targets with vm else I think that we need to store the reloc table as a debug option <wingo>stis: in theory we can parse the code section completely to recover those references and relocate them; that's an option i guess <wingo>or we can write a reloc table, but that could be large <wingo>but the code doesn't reference debugging sections, right? <wingo>anyway, i have been afk for a week or so, will look at email tomorrow <stis>yes i think that we could just nuke the debug sections. The question though is if we would like to change for example page alignement <stis>then I think that we need a reloc table. But let's take one step at the time. I will just nuke them. <wingo>sneek: later tell daviid would you mind updating the guile.m4 in guile-lib to match what is in guile git? thanks! <wingo>sneek: later tell daviid i would do it myself but i think you have some non-standard modifications there <civodul`>wingo: it's a slow read-only mirror AIUI <wingo>i was building a presentation recently and had to commit to all of guile-present's deps to allow it to build with guile 3.0 ;) <paroneayea>is this because you're doing experiments towards guile 3.0? <civodul>wingo: like GUILE_PKG([3.0 2.2 2.0])? fun :-) <ym>Is guile-emacs in workable state now?