On Tue, May 21, 2002 at 05:49:33PM +0300, Tommi Hassinen wrote: > A version from last friday works the same way; gives a blank top_builddir > like the current version. hmm. > Ooops, this is interesting. There seems to be two separate versions of > autoconf here: > > # locate autoconf |grep bin > /usr/bin/autoconf > /usr/bin/autoconf-wrapper > /usr/bin/autoconf2.13 > /usr/bin/autoconf2.50 > # It's the same here. There was a long discussion in Debian on how to handle the autoconf2.13/2.50 transition, apparently the maintainer wrote a wrapper script which should do the right thing[tm]. Dunno, perhaps it doesn't in your case. > I even can start either of them, but I don't know the logic how the > version is chosen: > > $ autoconf --version > Autoconf version 2.13 > > $ autoconf --version > autoconf (GNU Autoconf) 2.53 > Written by David J. MacKenzie and Akim Demaille. > > Copyright 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. This happens when you're running plain autoconf subsequently? Did you try running autoconf2.50 in the ghemical dir and see if top_builddir gets set correctly? > Ok, let's just leave this problem unresolved; probably the scripts are > just fine. :) OK. bye, Michael