Re: Problems with Automake 1.13 and 1.13.1

2013-01-17 Thread Pavel Raiskup
>> Kevin Fenzi wrote: > Paolo Bonzini wrote: > >> Of course (BTW the Automake maintainer now confirmed to me privately >> that he'd accept such a patch), though it would probably would make >> sense to put it in Fedora even before 1.13.2. >> >> I'll try to put together the patch tomorrow, unless a

Re: Problems with Automake 1.13 and 1.13.1

2013-01-17 Thread Richard W.M. Jones
On Thu, Jan 17, 2013 at 12:27:35PM +, Richard W.M. Jones wrote: > On Thu, Jan 17, 2013 at 12:05:03PM +, Richard W.M. Jones wrote: > > Automake 1.13.1 also miscompiles the following: > > > > TESTS = run-bindtests \ > > $(sort \ > > $(patsubst %,%.bc,$(test_progs)) \ > >

Re: Problems with Automake 1.13 and 1.13.1

2013-01-17 Thread Richard W.M. Jones
On Thu, Jan 17, 2013 at 12:05:03PM +, Richard W.M. Jones wrote: > Automake 1.13.1 also miscompiles the following: > > TESTS = run-bindtests \ > $(sort \ > $(patsubst %,%.bc,$(test_progs)) \ > $(patsubst %,%.opt,$(test_progs))) Apparently even jamming them int

Re: Problems with Automake 1.13 and 1.13.1

2013-01-17 Thread Richard W.M. Jones
Automake 1.13.1 also miscompiles the following: TESTS = run-bindtests \ $(sort \ $(patsubst %,%.bc,$(test_progs)) \ $(patsubst %,%.opt,$(test_progs))) which worked in previous versions. It turns it into the following which breaks make because of the unclos

Re: Problems with Automake 1.13 and 1.13.1

2013-01-16 Thread Kevin Fenzi
On Mon, 14 Jan 2013 16:57:02 +0100 Paolo Bonzini wrote: > Of course (BTW the Automake maintainer now confirmed to me privately > that he'd accept such a patch), though it would probably would make > sense to put it in Fedora even before 1.13.2. > > I'll try to put together the patch tomorrow, un

Re: Problems with Automake 1.13 and 1.13.1

2013-01-14 Thread Kevin Kofler
Paolo Bonzini wrote: > Of course (BTW the Automake maintainer now confirmed to me privately > that he'd accept such a patch), though it would probably would make > sense to put it in Fedora even before 1.13.2. +1 It's time to stop breaking backwards compatibility willy nilly! Kevin Kofle

Re: Problems with Automake 1.13 and 1.13.1

2013-01-14 Thread Paolo Bonzini
Il 14/01/2013 16:10, Stephen Gallagher ha scritto: >> Choices are: >> >> 1) introducing automake-1.12: I believe distros should agree on _not_ >> introducing an automake-1.12 or similar package and get the Automake >> maintainer to fix his mess. >> >> 2) fixing all packages individually: sounds lik

Re: Problems with Automake 1.13 and 1.13.1

2013-01-14 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon 14 Jan 2013 09:52:39 AM EST, Paolo Bonzini wrote: > As of the original 1.13 release two macros where removed from Automake: > AM_PROG_CC_STDC (replaced by AC_PROG_CC as provided by autoconf) and > AM_CONFIG_HEADER (replaced by AC_CONFIG_HEADERS)

Problems with Automake 1.13 and 1.13.1

2013-01-14 Thread Paolo Bonzini
As of the original 1.13 release two macros where removed from Automake: AM_PROG_CC_STDC (replaced by AC_PROG_CC as provided by autoconf) and AM_CONFIG_HEADER (replaced by AC_CONFIG_HEADERS). These were later reintroduced in 1.13.1, but not with the original behavior---they just give an error messag