On 05/30/2011 07:42 AM, Alexander Hansen wrote: > In any case, I found that fink's libtool2 along with fink's automake1.11 > appear to be needed for the build to proceed. I've just committed an > update (no revision change). Hopefully no other changes are needed.
Yes, even though you specify /usr/bin/autoreconf, autoreconf will just look along PATH for most of the other tools it runs (libtoolize, aclocal, autoconf, m4 etc). I say "most of", because I have not actually checked which ones use full path and which don't. You can force specific tools to run by setting env vars, e.g. ACLOCAL=/usr/bin/aclocal M4=/usr/bin/m4 AUTOCONF=/usr/bin/autoconf LIBTOOLIZE=/usr/bin/glibtoolize AUTOHEADER=/usr/bin/autoheader AUTOPOINT=/usr/bin/true AUTOMAKE=/usr/bin/automake autoreconf -fi though you may find it shorter to write: PATH=/usr/bin:$PATH autoreconf -fi Peter ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
