> I think I figured out that precompile.pike takes a --base parameter,
> common_module_makefile.in uses it with $(MODNAME) as the value, and
> it's been this way for ages. In the source release tarballs, all files
> have the same timestamp, and what seems to have happened is that
  ^^^^^^^^^^^^^^^^^^^^^^^
???

| $ tar tvzf Pike-v9.0.11.tar.gz | grep mpq
| -rw-r--r-- grubba/grubba   29544 2025-12-11 10:57 
Pike-v9.0.11/src/modules/Gmp/mpq.cmod
| -rw-r--r-- grubba/grubba   73115 2025-12-11 11:02 
Pike-v9.0.11/src/modules/Gmp/mpq.c
                                              ^^^^^

Looks good to me...

I suspect that precompile.sh-stamp has been regenerated and that this
triggers the regeneration.

        /grubba
  • Gen... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
    • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum
      • ... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
      • ... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
        • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum

Reply via email to