Hi, On 14.12.2009, at 07:06, Steve wrote:
> Hi, > > Had a google, some indications say check autoconf, automke as upto date. > This is the case as is fuse. > > > cd . && /bin/sh /root/t2-trunk/src.fuse.mfs.20091214.052721.25527 > localhost/fuse-2.8.1/missing --run aclocal-1.10 -I m4 > > configure.in:73: warning: macro `AM_ICONV' not found in library > > cd . && /bin/sh /root/t2-trunk/src.fuse.mfs.20091214.052721.25527 > localhost/fuse-2.8.1/missing --run autoconf > > cd . && /bin/sh /root/t2-trunk/src.fuse.mfs.20091214.052721.25527 > localhost/fuse-2.8.1/missing --run automake-1.10 --gnu > > configure.in:73: error: possibly undefined macro: AM_ICONV > > If this token and others are legitimate, please use m4_pattern_allow. > > See the Autoconf documentation. > > make: *** [configure] Error 1 > > make: *** Waiting for unfinished jobs.... > With T2 it more likely is the other way round: namely the auto* junk is too new - they often cause regressions by breaking their API :-( The best usually is not to regenerate the package's auto* stuff, that is if fuse does so fix the T2 package not to. Greetings -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin http://exactcode.com | http://t2-project.org | http://rene.rebe.name
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
