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.
