On Aug 29 18:49, Corinna Vinschen wrote: > On Aug 29 12:09, Daniel Jacobowitz wrote: > > On Tue, Aug 29, 2006 at 06:04:06PM +0200, Corinna Vinschen wrote: > > > On Aug 29 11:47, Christopher Faylor wrote: > > > > Btw, I agree with Daniel's suggestion of using > > > > ../config/no-executables.m4 if that's possible. > > > > > > I did that first, but the argument against this is that the > > > mingw-runtime package, does not contain a top-level config directory. > > > The source tree is supposed to be built stand-alone. Therefore it's > > > required to have a stand-alone aclocal.m4 file. > > > > > > [time passes] > > > > > > Or do you mean I should just add an include(../config/no-executables.m4) > > > to winsup/acinclude.m4 and create the aclocal.m4 files from there? > > > > If you do that it'll just emit a sinclude into aclocal.m4 anyway, won't > > it? > > Hm, yes, I guess so. > > But the problem is clear I hope. If we refer to ../config/foo, the > mingw/aclocal.m4 file isn't self-sufficient anymore. That's actually > the only reason I didn't refer to ../config/no-executables.m4, but > copied it instead.
Oh well, it seems I suffered an autotools confusion. The patch to winsup/acinclude.m4 is completely unnecessary. Calling aclocal with the correct include paths creates apparently correct aclocal.m4 files. So, just scratch the winsup/acinclude.m4 patch. Regenerating the aclocal.m4 files is sufficient. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat
