On Wed, Oct 25, 2006 at 09:33:34PM +0200, Ralf Wildenhues wrote: > * Patrick Welche wrote on Wed, Oct 25, 2006 at 07:44:21PM CEST: > > Building automake, after > > > > gmake distclean > > cvs update > > sh bootstrap > > configure > > Bzzt. At this point, you are not building Automake. You are building > whatever package this configure comes from: somewhere in $PATH. > Looks to me like you shouldn't do such thing, if it hurts. ;-)
OK, the security weenies may get me, but . is in the path, and no other "configure" is in a directory in the path. Phew. > > gmake > > > gmake[1]: Entering directory `/usr/src/local/automake/doc' > > ... > > config.status: creating Makefile > > config.status: creating src/Makefile > > The Automake package does not contain a "src" directory. Yes: doc/amhello/src ^^^ > > config.status: creating config.h > > Neither a config header (no C sources near or far here). Just take a look in doc/amhello > > config.status: executing depfiles commands > > make: don't know how to make w. Stop > > > Yet then > > > > cd doc > > gmake > > cd .. > > gmake > > > > succeeds?! > > Hmm, dunno. Whatever package you're building may have a benign doc > directory... automake/doc ? > > I can then repeat at the top and get stuck making "w" again > > or run gmake check and pass all 585 tests.. > > No released version of Automake has 585 tests (thanks Alexandre for the > stats table!), neither does CVS HEAD. Or did you mean without SKIPped > or XFAILed tests? that's right, with the skipped/xfailed tests... amhello seems to be the mystery.. Cheers, Patrick