Greetings, I can build the newest pet under Ubuntu dapper and edgy with autoconf 2.60 and automake 1.9. It sounds like your problems are being caused by how autoconf is being called. When I rebuild the configuration script, I usually call aclocal followed by autoconf. aclocal takes care of setting all of the version- related flags in the configuration file based on version information pulled from your system. You might want to try calling aclocal before calling autoconf. If it is Ubuntu packages you are after, I have already packaged the latest and greatest PET with selective unpacking. You can use the following repository: deb <a href="http://cl.naist.jp/~eric-n/ubuntu-nlp">http://cl.naist.jp/~eric-n/ubuntu-nlp</a> dapper delph-in deb-src <a href="http://cl.naist.jp/~eric-n/ubuntu-nlp">http://cl.naist.jp/~eric-n/ubuntu-nlp</a> dapper delph-in Eric <div>On 11/13/06, Timothy Baldwin <<a href="mailto:tim@csse.unimelb.edu.au">tim@csse.unimelb.edu.au</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi Stephan, > given a flurry of recent activity, i think you should get latest and > greatest versions of everything: the ERG, LKB, and [incr tsdb()] (in > the LinGO CVS repository); plus PET (from SVN).  the ERG that dan put > out yesterday includes a new MEM file `jhpstg.mem', which is active by > default.  it was trainined on an up-to-date treebank of 7000 sentences > of hiking text (the LOGON corpus) and uses three-level grandparenting; > thanks to zhang yi (of CoLi), the latest PET can take advantage of the > enriched feature set in this model, though only in selective unpacking > mode. We've been playing around with the latest and greatest version of PET and having various problems getting it to build. This may be a simple demonstration of our (my) ignorance of the subtleties of things like autoconf and automake, but when we run autoconf (v2.5.9) over the original <a href="http://configure.ac"> configure.ac</a> we get errors relating to automake (AM_*) commands:       If this token and others are legitimate, please use m4_pattern_allow.       See the Autoconf documentation. <a href="http://configure.ac:168"> configure.ac:168</a>: error: possibly undefined macro: AM_CONDITIONAL which we were able to remove by adding the following to <a href="http://configure.ac">configure.ac</a>: m4_pattern_allow([^AM_]) when we then run ./configure (parameterised variously), we get a bunch more errors relating to automake, which happily go away when all of the AM_* command lines are removed from configure, but configure then complains about not finding install.sh and the various <a href="http://Makefile.in"> Makefile.in</a> files in each directory. automake (v1.9.2) is independently grumpy about the contents of the various <a href="http://Makefile.am">Makefile.am</a> files: # automake <a href="http://configure.ac"> configure.ac</a>: no proper invocation of AM_INIT_AUTOMAKE was found. <a href="http://configure.ac">configure.ac</a>: You should verify that <a href="http://configure.ac">configure.ac</a> invokes AM_INIT_AUTOMAKE, <a href="http://configure.ac"> configure.ac</a>: that aclocal.m4 is present in the top-level directory, <a href="http://configure.ac">configure.ac</a>: and that aclocal.m4 was recently regenerated (using aclocal). <a href="http://configure.ac">configure.ac </a>: required file `./missing' not found cheap/Makefile.am:79: TOMABECHI_UNIFIER does not appear in AM_CONDITIONAL cheap/Makefile.am:83: SIMPLE_UNIFIER does not appear in AM_CONDITIONAL cheap/Makefile.am:96: ECL does not appear in AM_CONDITIONAL cheap/Makefile.am:98: ECLPREPROC does not appear in AM_CONDITIONAL cheap/Makefile.am:99: ICU does not appear in AM_CONDITIONAL cheap/Makefile.am:106: ECLMRS does not appear in AM_CONDITIONAL cheap/Makefile.am:130: XML does not appear in AM_CONDITIONAL cheap/Makefile.am:135: ICU does not appear in AM_CONDITIONAL cheap/Makefile.am:140: LEXDB does not appear in AM_CONDITIONAL cheap/Makefile.am:145: YY does not appear in AM_CONDITIONAL cheap/Makefile.am: required file `./depcomp' not found /usr/share/automake-1.9/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /usr/share/automake-1.9/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL cheap/Makefile.am:43: `CFLAGS' is a user variable, you should not override it; cheap/Makefile.am:43: use `AM_CFLAGS' instead. /usr/share/automake-1.9/am/depend2.am: am__fastdepCXX does not appear in AM_CONDITIONAL cheap/Makefile.am:42: `CXXFLAGS' is a user variable, you should not override it; cheap/Makefile.am:42: use `AM_CXXFLAGS' instead. /usr/share/automake-1.9/am/depend2.am: am__fastdepCXX does not appear in AM_CONDITIONAL /usr/share/automake-1.9/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/share/automake-1.9/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL /usr/share/automake-1.9/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL fspp/Makefile.am:31: `CFLAGS' is a user variable, you should not override it; fspp/Makefile.am:31: use `AM_CFLAGS' instead. /usr/share/automake-1.9/am/depend2.am: am__fastdepCXX does not appear in AM_CONDITIONAL fspp/Makefile.am:30: `CXXFLAGS' is a user variable, you should not override it; fspp/Makefile.am:30: use `AM_CXXFLAGS' instead. <a href="http://Makefile.am:2">Makefile.am:2</a>: ECL does not appear in AM_CONDITIONAL <a href="http://Makefile.am:3">Makefile.am:3</a>: ECLPREPROC does not appear in AM_CONDITIONAL <a href="http://Makefile.am:4">Makefile.am:4</a>: ICU does not appear in AM_CONDITIONAL <a href="http://Makefile.am">Makefile.am</a>: required file `./INSTALL' not found <a href="http://Makefile.am">Makefile.am</a> : required file `./NEWS' not found <a href="http://Makefile.am">Makefile.am</a>: required file `./AUTHORS' not found <a href="http://Makefile.am">Makefile.am</a>: required file `./ChangeLog' not found <a href="http://Makefile.am"> Makefile.am</a>: required file `./COPYING' not found I'm not sure if we are just using old versions of the various packages (although RedHat AS and Ubuntu dapper seemed equally grumpy), or just going about things the wrong way, but we'd appreciate it if anyone could offer any wisdom to help us out. Tim </blockquote></div> -- --Eric Nichols