Thomas Petazzoni cf647b69fb package/norm: fix build issue with waf >= 2.1.0 ... To fix build issues with modern Python versions, commit 8012a86f5c ("package/norm: use external waf") switched the norm package from using its internal waf copy to using our external waf package. Then, in fd5623150d ("package/waf: bump to v2.1.1"), we updated out external waf to a newer version, which breaks the API around ArgParse, see upstream commit: bd5c22d484: This causes breakage when building the norm package. Fabrice had already submitted patches upstream, to both the "protolib" project (which is used as a submodule in norm) and to the "norm" project. These pull requests are still pending, but let's backport the patches that seem reasonable and that fix the build issue. Fixes: http://autobuild.buildroot.net/results/f005d513434d42d26e601096b94b4070586118b2/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>		2024-08-26 11:31:49 +02:00
..
0001-protolib-drop-linux-version-check.patch
0002-Use-print-as-function-call-for-Python3-compatibility.patch
0003-Fix-mixed-tabs-spaces-in-protolib-wscript.patch
0004-protolib-wscript-fix-build-with-waf-2.1.0.patch
0005-wscript-fix-build-with-waf-2.1.0.patch
Config.in
norm.hash
norm.mk