-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 18 Sep 2026 07:18:19 +0100
Source: mit-scheme
Architecture: source
Version: 12.1-9
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter <bap@debian.org>
Changed-By: Barak A. Pearlmutter <bap@debian.org>
Changes:
mit-scheme (12.1-9) unstable; urgency=medium
.
* Backport from upstream development branch: 32MB default heap on 32-bit;
configure sizes the host compiler heap by the host word size, not the
target's; sf integrates the target's fixnum bounds when cross-compiling.
Together these make i386 build without help: drop the
MITSCHEME_HEAP_SIZE workaround from debian/rules.
* Patch src/Clean.sh so make distclean no longer deletes
src/Makefile.tools, which is a source file since -7.
* Patch the aarch64 microcode to strip the type code from the dynamic link
restored after an interrupt. A tagged stack pointer is invisible to
compiled code thanks to top-byte-ignore, but every stack check and the
GC's stack scan see a huge address, so a native arm64 Scheme could not
host a build: SIGSEGV at a point that depended on the memory layout,
reproducibly under sbuild and never in a login session. Reported
upstream. arm64 still bootstraps from mit-scheme-svm here, because the
buildd's host is the previous upload; it can switch to the native Scheme
once a fixed one is in the archive.
* Build mit-scheme-svm on riscv64 and loong64. Patch confshared.h to
recognise them -- neither has a native back end, so they need only a
machine type and HEAP_IN_LOW_MEMORY, which makes their object
representation match the other 64-bit little-endian ports -- and
uxtrap.h to use __executable_start rather than the legacy _init, which
the newer ports do not provide.
* Substitute the SVM back end name into the maintainer scripts at
build time instead of calling dpkg-architecture, which lives in
dpkg-dev: that is not Essential and is absent from a minimal chroot,
so mit-scheme-svm failed to configure there with status 127
(piuparts).
* Make compilation reproducible. The compiler gave every file a random
32-byte debugging key; sf stamped every .bin with the wall clock;
fasdump wrote the uninitialised padding after every string and
bytevector; and a saved band carried the garbage collector's timing
history, the save time, and everything the cold load had drawn from
the entropy pool, so the compiler itself differed from build to
build. Derive the key from the compilation's pathnames, honour
SOURCE_DATE_EPOCH, zero the padding, and keep the clock and the
entropy pool out of bands. Two causes are left, both in the bands
only; see debian/NOTES.md.
Checksums-Sha1:
1241700e651056bc659f22d3837a1523fda1504f 2073 mit-scheme_12.1-9.dsc
ab8b1454db8921db5ebd09eef5d9c60d37d47d5f 74004 mit-scheme_12.1-9.debian.tar.xz
5879721372f02b1e90e9c2971915b1fdf879d0c8 7567 mit-scheme_12.1-9_source.buildinfo
Checksums-Sha256:
82bfd230d74c67a82ed5c98d2f297daadd897069319c25d4d22baee8233b989a 2073 mit-scheme_12.1-9.dsc
f1732b6d3a585613f806d19a9c67d28674f96878ccf21fd88382bc7580ac7103 74004 mit-scheme_12.1-9.debian.tar.xz
05ea523b27182981170c456c6aba456ad539d7ceafdbb30a9c3f47dd0c1a9f58 7567 mit-scheme_12.1-9_source.buildinfo
Files:
0f444eabc0883df285b260e9e53bdcc0 2073 lisp optional mit-scheme_12.1-9.dsc
4d4839d24ce0a33255dce54152550015 74004 lisp optional mit-scheme_12.1-9.debian.tar.xz
fcd3dcc49c357e13d0a0c660e1220918 7567 lisp optional mit-scheme_12.1-9_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iIUEARYKAC0WIQQt5L8FQhB2xHrSA2fGrySQ08pyuQUCarQpxQ8cYmFwQGRlYmlh
bi5vcmcACgkQxq8kkNPKcrmxagEApDhy53j+CIIWv26lzmlH9Gu3T1Akm09sdc4z
525zSGwA/3quQHEjGlmDN/jc1Zlc9YQIJDK7Qm2KMJ5iIMvyVi4B
=OHhx
-----END PGP SIGNATURE-----
