-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Guillaume Rousse wrote:
> Ainsi parlait AAW :
>
>>The line:
>>
>>      %{__cputoolize: %{__cputoolize}}
>>
>>should be
>>
>>      %if %buildfor9_2
>>      %{__cputoolize: %{__cputoolize}}
>>      %endif
>>

A more generic fix may be:
        %{?__cputoolize: %{__cputoolize}}

(ie I think it was a typo)

>>Otherwise the build fails on 9.1 and -- I assume but have no way of
>>testing -- prior versions. So far this has cropped in in
>>arts-1.1.3-2mdk.src.rpm and kdelibs-3.1.3-3mdk.src.rpm
>
> Backward compatibility has never been an issue for mdk package.

Depends on the packages. Samba still builds all the way down to 8.0
(tested), and I took a patch from someone who still built on 7.2. Luca
keeps cyrus-imapd building down to at least 8.2.

> The advantage
> is that it helps keeping spec files clears. And I doubt just changing
this
> macro call would be enough anyway.

KDE packages all built on 9.1 before this, and possibly earlier versions
too.

Anyway, I think with latest rpm, these additions can be removed, since
%configure now calls __cputoolize:

* Sat Jul 26 2003 Gwenole Beauchesne <[EMAIL PROTECTED]>
4.2-14mdk

- - Requires: libtool >= 1.4.3-5mdk
- - Always call cputoolize in %configure{,2_5x}

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/L/F9rJK6UGDSBKcRAnAkAKCOgXnskIJkF7j+AGu4fgrGVUoqMQCguNNS
8VDE7EccGuBvxO88Qdf/c0c=
=f2Mx
-----END PGP SIGNATURE-----

******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
******************************************************************

Reply via email to