> For example, perhaps you have the same "frontend" directory listed > also in SUBDIRS for some other unrelated makefile? That is probably > the simplest way this situation could happen.
The problem is as follows. * In the `frontend` directory, the binary `ttfautohintGUI` is built. * In the `doc` directory, I need the `ttfautohintGUI` binary to create a snapshot image of its GUI. To do this, I have something like the following rule: ttfautohintGUI.png: $(top_srcdir)/frontend/maingui.cpp \ $(top_srcdir)/configure.ac \ $(srcdir)/ttfautohintGUI.stylesheet cd $(top_builddir)/frontend \ && $(MAKE) $(AM_MAKEFLAGS) ttfautohintGUI$(EXEEXT) $(SHELL) $(srcdir)/make-snapshot.sh \ $(top_builddir)/frontend/ttfautohintGUI$(EXEEXT) I must admit that I no longer remember why I did it this way. It works fine for non-parallel builds (and I have obviously never tested with make's `-j` option). Now I want to do better :-) However, the problem persists: `ttfautohintGUI` gets built in the `frontend` directory, and there is a dependency on the binary in the `doc` directory. Is there a clean solution for that? Werner