Re: automake-1.9.6: wrong handling of self-defined directories

[Ralf Wildenhues]

Hi Adrian,

* Adrian Bunk wrote on Tue, Aug 02, 2005 at 08:42:13PM CEST:
> I have the following Makefile.am:
> <--  snip  -->
> 
> secondbindir = $(prefix)/bin2
> 
> bin_PROGRAMS = test1
> secondbin_PROGRAMS = test2
> 
> install-exec-hook:
>       cd $(DESTDIR)$(bindir) && ln -fs test1 test11
>       cd $(DESTDIR)$(secondbindir) && ln -fs test2 test22
> 
> <--  snip  -->
*snip*
> "make install" fails with the following error:

[ secondbin_PROGRAMS gets installed through install-data, not install-exec ]
*snip*
> automake knows that secondbin_PROGRAMS contains programs, and it should 
> therefore call the install target from install-exec-am.

I'm not really sure how Automake /should/ behave (and I would have
expected the same thing you have), but it does behave according to
its documentation.  Quoting 'info Automake Install':

|    Variables using the standard directory prefixes `data', `info',
| `man', `include', `oldinclude', `pkgdata', or `pkginclude' (e.g.
| `data_DATA') are installed by `install-data'.
| 
|    Variables using the standard directory prefixes `bin', `sbin',
| `libexec', `sysconf', `localstate', `lib', or `pkglib' (e.g.
| `bin_PROGRAMS') are installed by `install-exec'.
| 
|    Any variable using a user-defined directory prefix with `exec' in
| the name (e.g. `myexecbin_PROGRAMS') is installed by `install-exec'.
| All other user-defined prefixes are installed by `install-data'.

So, try `secondexecbindir' as variable name instead.  :)

Cheers,
Ralf