> I don't think this is how bootstrap is meant to be used. You should > distribute it together with your application, and do "./bootstrap > --skip-po --gnulib-srcdir=/devel/gnulib/git/gnulib".
Just as the other files pulled in from Gnulib were not part of the source tree, bootstrap was also being used directly from the cloned Gnulib snapshot. The vanilla bootstrap that is provided by Gnulib and a customised bootstrap.conf that _is_ part of the source tree was good enough till this broke. If one is supposed to distribute bootstrap together with the application, two questions come to my mind: + Would it not result in unnecessary commits to the SCM to keep it synchronized with Gnulib's version? + A user who wants to fiddle with the release tar balls can just use 'autoreconf --install' instead of 'bootstrap'. Since the required Gnulib sources are already in the release tar ball, there is no need to bootstrap it, isn't it? Cheers, Debarshi
