On Thursday 28 September 2006, Mike Frysinger wrote:
> i normally use automake-1.9.6 but i just tried out 1.9b and it appears to
> have the same problem
automake-1.10 exhibits the problem as well ... finally spent some time digging
at it for fun
> $ svn st INSTALL
> $ automake-1.9b -a -c
> $ svn
Hello Polarina,
* Polarina wrote on Wed, Jan 02, 2008 at 08:35:26PM CET:
> The automake and friends automatically licensed my code with GPLv2 (They
> added the COPYING file with that license) when I wanted GPLv3. What
> gives? I'm using version 1.10.
> $ automake --add-missing --copy
The next
Polarina wrote:
> The automake and friends automatically licensed my code with GPLv2 (They
> added the COPYING file with that license) when I wanted GPLv3. What
> gives? I'm using version 1.10.
> $ automake --add-missing --copy
At the time that automake-1.10 was released GPLv2 was the appropri
The automake and friends automatically licensed my code with GPLv2 (They
added the COPYING file with that license) when I wanted GPLv3. What
gives? I'm using version 1.10.
$ automake --add-missing --copy
- Polarina
Hello Bruno,
Thanks for the bug report, and a Happy New Year.
* Bruno Haible wrote on Wed, Dec 26, 2007 at 03:43:40PM CET:
>
> When automake is installing files, it does so in a non-deterministic order.
> For example, in the same situation, sometimes "automake -a" outputs
>
> configure.in:5: in
