Le lun. 10 janv. 2022 à 21:27, Helmut Grohne <hel...@subdivi.de> a écrit : > > Source: talloc > Version: 2.3.3-2 > Tags: patch > User: debian-cr...@lists.debian.org > Usertags: cross-satisfiability ftcbfs > > talloc fails to cross build from source. I'm inclined to say it's > because waf. Really, stop using waf if you can. It's a nightmare. > > Ok ok. It's bad, but not impossible. I've attached this huge patch to > make it work. Of course you can apply it and it'll work, yes. But how > about stop using waf? > > Polemics aside. waf can be made to cross build if you export all the > build tools. Beyond the usual ones, you also need PYTHON3_CONFIG and > this magic _PYTHON_SYSCONFIGDATA_NAME variable. Of course, debian/rules > also needs to use it instead of calling python3-config directly. Beyond > that, a waf anser file is needed. And that's mostly it. Build-Depends > need to be multiarchified and the python3-talloc.lintian-overrides was > wrongly hard coding the amd64 triplet. > > It really can be made to work. But is all this pain really worth it? How > about using like setuptools or something sane? Think about it. And if > all else fails, apply my patch.
I would review any "setuptools or something sane" patch, but I won't have the time to write it myself. Alternatively, a patch to waf would help too... Regards -- Mathieu Parent