On Tuesday 29 May 2012, Guido Berhoerster wrote:
On 29.05.2012 15:33, Richard Guenther wrote:
The "fix" is of course to stop doing autoreconf in spec files. Upstream decided on the automake/autoconf version it uses (well, at least if they are shipping autogenerated files, which they should).
How else do you handle cases where you need to modify the build system (configure.ac, Makefile.am and friends)? Most of the time it works, but I find this is a fundamental flaw in autotools.
Either run autoreconf locally and include the autogenerated files in the patch too. Or at least don't use the full autoreconf but only the commands which are actually needed. BTW usually make would do this for you. For example instead of the current tar package does now: sed -i -e 's@need runtime check@yes@g' m4/*.m4 autoreconf -fiv %configure make which breaks the build on almost all repos... we could do this: %configure sed -i -e 's@need runtime check@yes@g' m4/*.m4 make Now make will invoke the needed aclocal, autoconf and automake and configure again. But in this example probably sed -i -e 's@need runtime check@yes@g' configure would be enough to avoid the automake dep completely. Generally I would say that we have too much packages where autoreconf is called for no good reason. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org