[Mageia-dev] problem with %_smp_mflags in Cauldron
Pierre-Malo Deniélou
pierre-malo.denielou at rhul.ac.uk
Sun Jan 6 14:51:34 CET 2013
Le 06/01/13 13:19,philippe makowski nous adresse ces quelques mots :
> 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)
I believe the answer is in how the autobuild is done:
http://fasmz.org/~pterjan/blog/?date=20130103#p01
The parameters are not exactly the same as the ones on the build system.
Cheers,
--
Malo
More information about the Mageia-dev
mailing list