summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-January/021176.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-January/021176.html')
-rw-r--r--zarb-ml/mageia-dev/2013-January/021176.html175
1 files changed, 175 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-January/021176.html b/zarb-ml/mageia-dev/2013-January/021176.html
new file mode 100644
index 000000000..394837f01
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-January/021176.html
@@ -0,0 +1,175 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] problem with %_smp_mflags in Cauldron
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20problem%20with%20%25_smp_mflags%20in%20Cauldron&In-Reply-To=%3Ckcc2jm%24hcf%241%40ger.gmane.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="021174.html">
+ <LINK REL="Next" HREF="021178.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] problem with %_smp_mflags in Cauldron</H1>
+ <B>PhilippeDidier</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20problem%20with%20%25_smp_mflags%20in%20Cauldron&In-Reply-To=%3Ckcc2jm%24hcf%241%40ger.gmane.org%3E"
+ TITLE="[Mageia-dev] problem with %_smp_mflags in Cauldron">philippedidier at laposte.net
+ </A><BR>
+ <I>Sun Jan 6 15:44:08 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="021174.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
+</A></li>
+ <LI>Next message: <A HREF="021178.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#21176">[ date ]</a>
+ <a href="thread.html#21176">[ thread ]</a>
+ <a href="subject.html#21176">[ subject ]</a>
+ <a href="author.html#21176">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Pierre-Malo Deni&#233;lou a &#233;crit :
+&gt;<i> Le 06/01/13 13:19,philippe makowski nous adresse ces quelques mots :
+</I>&gt;&gt;<i> Hi,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I have a build fail in Cauldron
+</I>&gt;&gt;<i> (<A HREF="http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/log/python-cairo-1.10.0-3.mga3.src.rpm/build.0.20130104032637.log">http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/log/python-cairo-1.10.0-3.mga3.src.rpm/build.0.20130104032637.log</A>)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> because %python3_waf is resolved as /usr/bin/waf-3.3 build -l12 -j12
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> and I don't understand why
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> we have in /etc/rpm/macros.d/waf-python3.macros :
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> %python3_waf %__python3_waf build %_smp_mflags
+</I>&gt;&gt;<i> and
+</I>&gt;&gt;<i> %__python3_waf %{_bindir}/waf-%{python3_version}
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> so why getting /usr/bin/waf-3.3 build -l12 -j12
+</I>&gt;&gt;<i> instead of /usr/bin/waf-3.3 build -j12
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> from where come this -l that is not supported by waf (waf-3.3: error:
+</I>&gt;&gt;<i> no such option: -l)
+</I>&gt;<i>
+</I>&gt;<i> I believe the answer is in how the autobuild is done:
+</I>&gt;<i> <A HREF="http://fasmz.org/~pterjan/blog/?date=20130103#p01">http://fasmz.org/~pterjan/blog/?date=20130103#p01</A>
+</I>&gt;<i>
+</I>&gt;<i> The parameters are not exactly the same as the ones on the build system.
+</I>&gt;<i>
+</I>&gt;<i> Cheers,
+</I>&gt;<i>
+</I>There was the same problem for lv2 with the autobuild system...
+lv2 uses waf too !
+
+It could correctly build on the Build System but failed with autobuild,
+for the same reason
+
+A workaround consists to modify the spec file :
+replace &quot;./waf %{?_smp_mflags}&quot; with simply &quot;./waf build&quot;
+
+but it will take more time to build :(
+
+
+A contrario :
+Ardour3 that uses waf can be built without any problem with the
+autobuild system :
+the spec file contains symply ; ./waf build
+
+
+Nevertheless, the autobuild system is now different from the
+BuildSystem, and I don't know if it's useful to modify your spec file,
+to be compliant with the autobuild, not knowing for now if the same
+modification will be applied inside the BS.
+
+NB some programs ask to use their own bundled version of waf... which
+means that modifying Mageia waf-rpm and the waf-python3.macros will not
+solve the problem of the smp_flags for them.
+
+
+Regards
+Philippe
+
+
+
+
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="021174.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
+</A></li>
+ <LI>Next message: <A HREF="021178.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#21176">[ date ]</a>
+ <a href="thread.html#21176">[ thread ]</a>
+ <a href="subject.html#21176">[ subject ]</a>
+ <a href="author.html#21176">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>