Dominique Dumont

Looks like compiler id also depends from hostname. From my Debian packager point of view, this makes compiler id mostly unpredictable when building rakudo on Debian infrastructure. I can see...

@niner do you also consider this behavior as a bug ? If yes, could you fix it ? All the best

All I can say is that building rakudo on 2 different systems with the same setup (same directory layout, Debian/sid, moarvm and nqp installed with debian packages) lead to different...

@niner , how did you get the values below ? > ``` > $config := '/home/nine/rakudo/install'; > $config := '/home/nine/rakudo/install/share/perl6'; > > $config := '60c54e6a80e87dcfc0efac8a2514c215dbd2ae06'; > > $config := '/home/nine/rakudo/install/share/nqp';...

Looks good: ``` ### Location $config := '/usr'; $config := '/usr/lib/perl6'; $config := '38f6cb1287d5f25ed402f19bca6e86874b0dd010'; $config := '/usr/share/nqp'; ``` I've only found the build directory in comments in generated code. So...

Another weird thing. With the same rakudo on different arches (arm 32 bits vs amd64), I get: * the same source-digest * different compiler ids E.g on arm: ``` $...

For the record, `source-digest` is compiled in function `_m_source_digest` (file `tools/lib/NQP/Config/Rakudo.pm`) from all `npq` or `pm6` files found in `src` and from `gen/nqp-version`.

Looks like compiler-id is computed in `src/core.c/Compiler.pm6` with: ```perl6 my constant $compilation-id = nqp::box_s( nqp::sha1($*W.handle.Str ~ nqp::atkey($config,'source-digest')),Str ); ``` What's the purpose of salting the id with `$*W.handle.Str` ?

Since Debian freeze is coming soon. I'm going to patch rakudo on Debian to remove `$*W.handle.Str` from the computation of `compiler-id`.

Debian is in deep freeze, so I don't currently work on packaging Rakudo. That said I want to try a tweak on function `_m_source_digest` (file `tools/lib/NQP/Config/Rakudo.pm`). This function compiles a...