On Sat, Nov 19, 2011 at 9:32 AM, tsteven4 <tstev...@gmail.com> wrote:
The build fails because autoconf is not installed: > [ ... ] This seems like a general issue with subversion any time a target and a > dependency of that target are both in the repository. > This isn't new to SVN. We had this problem with CVS, too. As your research shows, it's not a solved problem. The practical choices a > Does any body know of a good way to resolve this? Clearly I can touch > configure before I make, but I am looking for a more general and > automated solution. > If you're going to live in the SVN tree, it's less painful to just install autoconf and let it do its thing. (And byte your lip an annoyance when you generate a patch and see that you have a slightly different autoconf than I do and that it'll generate a zillion lines of spew in the patches if you don't revert it...) I did just tweak Makefile.in to ensure that configure is always newer in the tarball so that more casual developers are less likely to be forced to endure that. We were already doing that for another of our checked-in, generated files. As I mentioned in a related post early today, I don't have deep love of autoconf. The only thing I've found worse so far is everything else. :-/ RJL
