On Thu, Jan 22, 2004 at 04:51:43PM +0200, Jani Taskinen wrote: > > There's nothing wrong in this. If your autoconf/aclocal/etc. > tools are installed correctly, buildconf works fine. > > Please use the snapshots if you don't know what you're doing.
:-) I have to smile otherwise I would be offended. > >Why does build/buildcheck.sh do the dance of copying the contents of > >libtool.m4 (whose location it guesses - wrongly in my case) into > >aclocal.m4, instead of letting libtoolize copy libtool.m4 over and > >automake pop it into aclocal.m4? This presumably would happen during > >make -f build/build2.mk if buildcheck gave it a chance.. The above still stands. I would call your use of the autotools unorthodox. libtoolize would pop libtool.m4 either into . or the directory specified in AC_CONFIG_AUX_DIR. OK, you may wish to carry on using a really outdated autoconf which doesn't understand that, but at least letting libtoolize, which knows where to find the libtool.m4, copy it, and then look for it in . is not a bad thing. However, as you then just copy libtool.m4 into aclocal.m4, I don't see why you don't let the autotools just do if for you. It isn't as if you are altering libtool.m4's contents. Your complexity doesn't seem to buy anything other than your comment about libtool 1.5 not being backward compatible. Regards, Patrick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
