On Sun, Aug 19, 2018 at 05:29:04PM +0200, Barak A. Pearlmutter wrote: > Currently oaklisp can only be built for 32-bit systems. For that > reason, gcc-multilib is a build dependency on any 64-bit architecture, > where 32-bit binaries are built. In order to prevent fruitless build > attemps on 64-bit architectures without 32-bit variants and the > capability to build & run for them, I'm thinking it's easiest to just > leave this unsatisfiable-on-problematic-architectures build dependency > in. > > Unless that causes a problem for something else? > > Is there a better way to express this? Ideally a high-level > description "32-bit pointers or gcc -m32 generates something with > 32-bit points that runs" would be the thing. But I don't think there's > any nice way to say that.
Thanks, now I understand the purpose. The usual solution would be to have Architecture: armel armhf hppa any-i386 m68k mips mipsel powerpc powerpcspe sh4 x32 and then the user installs the 32bit package through multiarch, e.g. on amd64 the i386 package. Non-release architecture sparc64 is the only case currently in Debian where the corresponding 32bit architecture is no longer in Debian. Since the C library is the only dependency of oaklisp, your approach also works in this case and I don't see a strong need to have that changed. But any-riscv64 must then be added to the gcc-multilib architectures: https://buildd.debian.org/status/logs.php?pkg=oaklisp&ver=1.3.6-2&arch=riscv64&suite=sid cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
