From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-January/021173.html | 131 ++++++++++++++++++++++++++++ 1 file changed, 131 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-January/021173.html (limited to 'zarb-ml/mageia-dev/2013-January/021173.html') diff --git a/zarb-ml/mageia-dev/2013-January/021173.html b/zarb-ml/mageia-dev/2013-January/021173.html new file mode 100644 index 000000000..a95c806d8 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-January/021173.html @@ -0,0 +1,131 @@ + + + + [Mageia-dev] problem with %_smp_mflags in Cauldron + + + + + + + + + +

[Mageia-dev] problem with %_smp_mflags in Cauldron

+ philippe makowski + makowski.mageia at gmail.com +
+ Sun Jan 6 14:19:55 CET 2013 +

+
+ +
Hi,
+
+I have a build fail in Cauldron
+(http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/log/python-cairo-1.10.0-3.mga3.src.rpm/build.0.20130104032637.log)
+
+because  %python3_waf is resolved as /usr/bin/waf-3.3 build -l12 -j12
+
+and I don't understand why
+
+we have  in /etc/rpm/macros.d/waf-python3.macros :
+
+%python3_waf		%__python3_waf build %_smp_mflags
+and
+%__python3_waf	%{_bindir}/waf-%{python3_version}
+
+
+so why getting  /usr/bin/waf-3.3 build -l12 -j12
+instead of   /usr/bin/waf-3.3 build -j12
+
+from where come this -l that is not supported by waf (waf-3.3: error:
+no such option: -l)
+
+thanks
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1