On Fri, 10 Sep 2010, Dean Groe wrote:
I am puzzled as to why I would bother to make after configure already told me that it was old, that my src was not updating?
Yea. Once configure tells you the version number and it's wrong there's no need to go further.
FWIW, it appears that the problem was due to CVS not updating source. I downloaded source and built in a different directory and it worked OK.
Of course, that is not how this is supposed to work ideally, but that is what was needed this time.
Probably becase you tried the STABLE or RELEASE tags and those options are sticky, as Jerry mentioned. Jerry wrote:
> Use 'cvs update -r HEAD' instead of STABLE or RELEASE. The use of > any tags in an update is sticky. You get what you asked for in > this case.
So if you had issued that command against your original directory you probably would have been able to then issue the "cvs update" command and gotten the latest CVS HEAD sources. Perhaps you still have that directory around and can try it. -- Curt, WE7U. <http://www.eskimo.com/~archer> APRS: Where it's at! <http://www.xastir.org> Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
