Package: capnproto Version: 0.6.1-1 Control: affects -1 + src:sonic-visualiser User: [email protected] Usertags: rebootstrap
cross building sonic-visualiser fails, because running capnp fails with an "Exec format error". That usually indicates that the relevant package (capnproto in this case) should be marked Multi-Arch: foreign to select the build architecture version rather than the host architecture one. But is such a marking actually correct? Unfortunately, answering that question is usually difficult as it requires both multiarch-specific knowledge and package-specific knowledge. Most people lack either or both. I for one lack the latter. Can you help me understand whether the marking is correct? The capnproto package contains a few programs. When thinking about Multi-Arch, one thinks about the interface of a package and these programs certainly are the main interface. The question to ask is: Do they behave any different when run on a different architecture? Sometimes one can quickly assert that both input and output formats are textual rather than binary. Is that the case for capnproto? If yes, it seems very likely that the marking can be correct. The invocation however says "compile". Does it actually run a C compiler? Since the output of a C compiler is architecture-dependent, running it voids and Multi-Arch: foreign marking. Please enter a discussion with me such that we can find out the correct Multi-Arch marking for capnproto. The actual marking is a rather simple step, once we know how it should be marked. The multiarch hinter says that the libcapnp-* packages should be Multi-Arch: same. Please consider adding that. If in doubt, please ask me. Thanks for your assistance Helmut
