Hi,
automake generated compilation rules involving object files in subdirectories
lead to a build failure. With 'no-dependencies', the build failure disappears.
$ automake --version
automake (GNU automake) 1.10
$ autoconf --version
autoconf (GNU Autoconf) 2.60
$ gcc -v
Reading specs from /usr/lib
Hello Bruno,
* Bruno Haible wrote on Wed, Nov 08, 2006 at 02:20:44PM CET:
>
> automake generated compilation rules involving object files in subdirectories
> lead to a build failure. With 'no-dependencies', the build failure disappears.
Thanks for the report. A better title would have been: Dep
Hello Gary,
* Gary V. Vaughan wrote on Wed, Nov 08, 2006 at 06:34:45AM CET:
> Bad news, I appear to have hit a bug in aclocal. From a fresh checkout
> of m4 CVS HEAD:
[...]
> $ bootstrap
> ...
> bootstrap: running: autopoint --force
> bootstrap: running: gnulib-tool --update
> ...
> bootstrap: ru
Hello Karl,
* Karl Berry wrote on Wed, Nov 08, 2006 at 06:02:55PM CET:
> gnupload --help has this example:
>
> gnupload ...
>--to alpha.gnu.org:automake \\
>...
>
> I suggest changing it to:
>--to alpha.gnu.org:gnu/automake \\
Thanks. I took liberty to app
I suggested changing the example to:
--to alpha.gnu.org:gnu/automake \\
But actually I had it exactly wrong, and you had it right in the first
place. The gnu/ must *not* be there in the filename: directive, because
the ftp-upload script on the server side puts it in. So it should come
On 8 Nov 2006, at 13:17, Ralf Wildenhues wrote:
Hello Gary,
Hallo Ralf!
* Gary V. Vaughan wrote on Wed, Nov 08, 2006 at 06:34:45AM CET:
Bad news, I appear to have hit a bug in aclocal. From a fresh
checkout
of m4 CVS HEAD:
[...]
$ bootstrap
...
bootstrap: running: autopoint --force
boot