Hi, Mo Zhou a écrit le 20/08/2019 à 18:21 : > On 2019-08-20 16:15, Sébastien Villemot wrote: >> Le mardi 20 août 2019 à 18:11 +0200, Sébastien Villemot a écrit : >>> Le mardi 20 août 2019 à 09:00 -0700, Mo Zhou a écrit : >>>> Got it. But keep in mind that we haven't adapted the rules/control >>>> for 32-bit architectures -- they don't support BLAS64/LAPACK64. >>>> I'll add some guards in rules later and test it in an i386 env. >>> >>> Oh, I had overlooked that. >> >> I realize that I don’t know what we should put in the Architecture >> field in debian/control for the BLAS64/LAPACK64 packages. AFAIK there >> is no 64-bit wildcard. >> >> One option is to painfully list all the existing 64-bit architectures >> (including ports), but this is not very maintainable over the long-run. >> Is there a better option? I guess we’re not the first ones to face this >> problem. > > dpkg-architecture has a flag: > > DEB_HOST_ARCH_BITS=64 (on amd64) > > that can be used in d/rules. > > For d/control I cannot think of anything other than manually listing. You can keep 'Architecture: any' in d/control, and set DH_OPTIONS in d/rules to filter out the binary package with '-N<pkgname>'. See for example d/rules from the navit source package[1]. [1] https://sources.debian.org/src/navit/0.5.3+dfsg.1-2/debian/rules/#L89 _g.
Attachment:
signature.asc
Description: OpenPGP digital signature