Hello, I was wondering if it's possible to build mutt outside the source tree. Starting doing it I created a directory called `build-mutt' somewhere on my system and ran `/path/to/mutt-1.1.9/configure' with it's options, which semmed to work properly. But make stopped with the following output: -----begin make output----- make all-recursive make[1]: Entering directory `/home/bendus/muttsrc/build-mutt' Making all in m4 make[2]: Entering directory `/home/bendus/muttsrc/build-mutt/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/bendus/muttsrc/build-mutt/m4' Making all in po make[2]: Entering directory `/home/bendus/muttsrc/build-mutt/po' make[2]: *** No rule to make target `../../mutt-1.1.9/keymap_alldefs.h', needed by `../../mutt-1.1.9/po/mutt.pot'. Stop. make[2]: Leaving directory `/home/bendus/muttsrc/build-mutt/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/bendus/muttsrc/build-mutt' make: *** [all-recursive-am] Error 2 ------end make output------ It seems to me that make tries to build something in the source tree but there is no makefile for it there. However building `keymap_alldefs.h' by hand in the build tree requires to copy the OPS* files from the source to the build directory. This isn't done by configure or anything. After making `keymap_alldefs.h' this way it has to be copied to the source tree in order to make mutt properly, which works then fine. As I figured out, make looks in POTFILES for the sources and what to build or something like that. Could the entry for keymap_alldefs.h point to `top_builddir/keymap_alldefs.h' rather than to `keymap_alldefs.h'? I guess this would solve the problem. Or am I missing something here and it works without all this? Regards, Stefan. -- Test-tube babies shouldn't throw stones.
