On Thu, Sep 9, 2010 at 8:19 PM, Dean Groe <warpedspe...@yahoo.com> wrote: > And we are back. > > I finally had another chance to work on this tonight. Summary - Same result. > > With "cvs update" I decided to try forcing the STABLE and then the RELEASE > tags, > but each time, no difference. > > > Each time - > bootstrap works fine. > 7) Removing autom4te.cache directory... > 6) Running aclocal... > 5) Running autoheader... > 4) Running autoconf... > 3) Running automake... > 2) Checking for 'mkinstalldirs'... Found! > 1) Generating derived language files..... > Bootstrap complete. > > configure gives me this: > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > > Configuring xastir 1.9.8 > > ... etc.... > > And there we have it. I cannot get this thing past 1.9.8 . > > Any ideas? What have I missed?
Hmm, the above would all happen as shown in the event that entering 'cvs update' effectively did nothing. What happens if you do the following at the command line in a new blank directory? cvs -d:pserver:anonym...@xastir.cvs.sourceforge.net:/cvsroot/xastir login (just hit enter when prompted for a password after the above command) cvs -d:pserver:anonym...@xastir.cvs.sourceforge.net:/cvsroot/xastir co xastir cd xastir ./bootstrap.sh mkdir build cd build ../configure The above just downloads a fresh copy of 1.99 and runs with it. Regards, Lee - K5DAT Murphy, TX _______________________________________________ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir