Dominique Dumont

Hi For what it's worth, here's a diff comparing the old and new list of symbols: ``` --- /tmp/libt.old 2023-01-03 18:53:12.541434141 +0100 +++ /tmp/libt.new 2023-01-03 18:52:51.730263028 +0100 @@ -1,15 +1,9...

Yes, I've seen this problem. After a while, the used memory can go over 100% :  In this case, the warning about critical memory is no longer shown... Anyway,...

Weirdly enough, there's no such problem with JSON::Marshal 0.0.23 ([build log](https://buildd.debian.org/status/fetch.php?pkg=raku-json-marshal&arch=amd64&ver=0.0.23-1%2Bb2&stamp=1664290866&raw=0)) but only META6 content was changed between version 0.0.23 and 0.0.24 (https://github.com/jonathanstowe/JSON-Marshal/commit/b916c8c3b7fd4dc4a19a2f22d798382c7594590e)

My bad. What changed is the patch applied to [rakudo](https://salsa.debian.org/perl6-team/rakudo/-/blob/master/debian/patches/fix-precompilation.patch) to fix pre-compilation issues as suggested in this https://github.com/rakudo/rakudo/issues/4907#issuecomment-1264446094

Sorry about the confusion. Let me try to clarify. The patch was applied to rakudo 2022.07 to fix a similar issue (#4907), it did work for some modules (i.e. `JSON::Fast`),...

@niner , do you have any idea on how to fix this issue ? All the best

No. I get the same result. On the other hand, I get different result depending on where are the dependencies built. I've tried building JSON::Marshal with packaged dependencies: * If...

ok, but it looks like another factor comes in creating the SHA for the compiler id. Debian effort to create reproducible builds show that the same source leads to different...

@niner, to manage Debian package, I need to know exactly what can trigger a change of compiler id. Besides the source code of nqp and rakudo, what is factored in...

I've run some tests. I've got different compiler ids when compiling the same source in different directories. Is that expected ?