1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
|
<!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=%3CCA%2BCX%2Bbh4w7buy54caYXLMmPnsBN5ysHF0dMairqSr8N_MxFQ2Q%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="021176.html">
<LINK REL="Next" HREF="021180.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] problem with %_smp_mflags in Cauldron</H1>
<B>Pascal Terjan</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=%3CCA%2BCX%2Bbh4w7buy54caYXLMmPnsBN5ysHF0dMairqSr8N_MxFQ2Q%40mail.gmail.com%3E"
TITLE="[Mageia-dev] problem with %_smp_mflags in Cauldron">pterjan at gmail.com
</A><BR>
<I>Sun Jan 6 15:59:17 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="021176.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
</A></li>
<LI>Next message: <A HREF="021180.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21178">[ date ]</a>
<a href="thread.html#21178">[ thread ]</a>
<a href="subject.html#21178">[ subject ]</a>
<a href="author.html#21178">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Sun, Jan 6, 2013 at 2:44 PM, PhilippeDidier
<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">philippedidier at laposte.net</A>> wrote:
><i> Pierre-Malo Deniélou a écrit :
</I>>><i> Le 06/01/13 13:19,philippe makowski nous adresse ces quelques mots :
</I>>>><i> Hi,
</I>>>><i>
</I>>>><i> I have a build fail in Cauldron
</I>>>><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>>>><i>
</I>>>><i> because %python3_waf is resolved as /usr/bin/waf-3.3 build -l12 -j12
</I>>>><i>
</I>>>><i> and I don't understand why
</I>>>><i>
</I>>>><i> we have in /etc/rpm/macros.d/waf-python3.macros :
</I>>>><i>
</I>>>><i> %python3_waf %__python3_waf build %_smp_mflags
</I>>>><i> and
</I>>>><i> %__python3_waf %{_bindir}/waf-%{python3_version}
</I>>>><i>
</I>>>><i>
</I>>>><i> so why getting /usr/bin/waf-3.3 build -l12 -j12
</I>>>><i> instead of /usr/bin/waf-3.3 build -j12
</I>>>><i>
</I>>>><i> from where come this -l that is not supported by waf (waf-3.3: error:
</I>>>><i> no such option: -l)
</I>>><i>
</I>>><i> I believe the answer is in how the autobuild is done:
</I>>><i> <A HREF="http://fasmz.org/~pterjan/blog/?date=20130103#p01">http://fasmz.org/~pterjan/blog/?date=20130103#p01</A>
</I>>><i>
</I>>><i> The parameters are not exactly the same as the ones on the build system.
</I>>><i>
</I>>><i> Cheers,
</I>>><i>
</I>><i> There was the same problem for lv2 with the autobuild system...
</I>><i> lv2 uses waf too !
</I>><i>
</I>><i> It could correctly build on the Build System but failed with autobuild,
</I>><i> for the same reason
</I>><i>
</I>><i> A workaround consists to modify the spec file :
</I>><i> replace "./waf %{?_smp_mflags}" with simply "./waf build"
</I>><i>
</I>><i> but it will take more time to build :(
</I>><i>
</I>><i>
</I>><i> A contrario :
</I>><i> Ardour3 that uses waf can be built without any problem with the
</I>><i> autobuild system :
</I>><i> the spec file contains symply ; ./waf build
</I>><i>
</I>><i>
</I>><i> Nevertheless, the autobuild system is now different from the
</I>><i> BuildSystem, and I don't know if it's useful to modify your spec file,
</I>><i> to be compliant with the autobuild, not knowing for now if the same
</I>><i> modification will be applied inside the BS.
</I>
I had suggested few months ago to use it on build system too to not
kill the machine when it gets to build several kernels each of them
using -jN, but it is being tested on autobuild first (using it allowed
to reduce total build time from 6 days to 30h).
So far only waf should be a problem. Maybe we could add a macro with
only the number of cpus and use -j%n_cpus with waf instead of using
the make flags given that it is not compatible with other make
options? (In smp_mflags the second m is for make)
I just searched for it and it seems rpm upstream will add such macro
<A HREF="https://bugzilla.redhat.com/show_bug.cgi?id=669638#c13">https://bugzilla.redhat.com/show_bug.cgi?id=669638#c13</A>
><i> NB some programs ask to use their own bundled version of waf...
</I>
This is very sad
><i> which means that modifying Mageia waf-rpm and the waf-python3.macros will not
</I>><i> solve the problem of the smp_flags for them.
</I></PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="021176.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
</A></li>
<LI>Next message: <A HREF="021180.html">[Mageia-dev] problem with %_smp_mflags in Cauldron
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#21178">[ date ]</a>
<a href="thread.html#21178">[ thread ]</a>
<a href="subject.html#21178">[ subject ]</a>
<a href="author.html#21178">[ 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>
|
