When I try to build in a different directory the configure script gives me an error saying that the Makefile in the main directory is not valid. mo:~/project/mozilla/mozilla/linux> ../configure --prefix=$pre \ ? --with-gtk-prefix=$pre \ ? --with-glib-prefix=$pre \ ? --with-libIDL-prefix=$pre \ ? --with-nspr=$pre \ ? --with-pthreads \ ? --disable-md creating cache ./config.cache checking host system type... i586-pc-linux-gnu checking target system type... i586-pc-linux-gnu checking build system type... i586-pc-linux-gnu *** * Your source tree contains these files: * /home/mo/project/mozilla/mozilla/Makefile * This indicates that you previously built in the source tree. * A source tree build can confuse the separate objdir build. * * To clean up the source tree: * 1. cd /home/mo/project/mozilla/mozilla * 2. gmake -f client.mk cleansrcdir *** If I remove this makefile then configure will work. Either configure needs to be fixed or the Makefile should be removed from the CVS.

Why is this a bug? This is what is supposed to happen if you previously built (or at least ran configure) in the source tree, and then switched to building in an "objdir". Configure is trying to help you avoid potential problems due to confusion as which set of generated files is the correct one. At least that's what I think was intended (Steve, does this still cause problems? What if we just warn about it, as with make 3.77, rather than abort?).

The Makefile is only part of on obsolete checkout module, MozillaSourceUnixOnly (which is in another obsolete module, MozillaSource) At any rate, I removed it from CVS. I will reopen the bug and mark it fixed. The test done by configure is a valid one. Having the Makefile in the source tree and the object tree can cause problems if Makefile.in changes and the Makefile needs to regenerate.

I just did a CVS update and it did not add the Makefile. I then ran configure and I did not get the error so I would say this bug has been fixed. Marking as verified.