Hi Matt! Have not forgotten about this. I think odds are good that my last 2.6.9 commit was made yesterday. Things are a little ambiguous because Debian just made a release, and the autobuilders are building in a somewhat unstable environment, so my usual testing of the maxima/axiom/acl2/hol88 builds across all those architectures show some failures which might or might not be GCL's fault, and need chasing down. If interested, you can see the progress at
https://buildd.debian.org/status/package.php?p=gcl&suite=sid https://buildd.debian.org/status/package.php?p=maxima&suite=sid https://buildd.debian.org/status/package.php?p=acl2&suite=sid https://buildd.debian.org/status/package.php?p=hol88&suite=sid https://buildd.debian.org/status/package.php?p=axiom&suite=sid Once there are no gcl related failures, I will 1) tag Version_2_6_8 and Version_2_6_9 in cvs and git 2) push gcl_2.6.8.tar.gz and gcl_2.6.9.tar.gz to the download area at gnu.org 3) update the website with this announcement 4) proceed henceforward with the master and experimental branches in git, as this appears to be what the users want. To fetch anything from git, do git clone git://git.sv.gnu.org/gcl.git cd gcl git checkout Version_2_6_9pre (or experimental, or Version_2_6_8pre ....) ./configure && make As for the mac, I have one build environment available, that generously provided by Robert Krug. Both Version_2_6_8pre and Version_2_6_9pre work on his machine with ./configure && make (with or without the --enable-ansi flag to configure). There has been a report on a more recent mac version to which I have no access. There appears to be a minor configure issue where the test for the profil() function fails incorrectly. I believe, though have been unable to test, that ./configure echo "#undef NO_PROFILE" >h/config.h make will work around this. I've pointed out the gcc failure responsible to the reporting user in case a cleaner solution can be implemented, but so far no word back. I would prefer not to hold up the release on this issue. Take care, > Hi, Camm -- > >>From the point of view of GCL users (rather than developers who don't > understand these version control issues), what's the current way to > obtain 2.6.8pre or 2.6.9, etc.? And what would you expect to work on > a Mac? > > Is there a web page for me to get up-to-date answers to questions like > these? > > Thanks -- > -- Matt > From: Camm Maguire <c...@maguirefamily.org> > Date: Fri, 02 Aug 2013 17:57:56 -0400 > > Greetings! > > git clone git://git.sv.gnu.org/gcl.git > > should work now. Its identical to cvs at the moment save for some > pushed commits I've made to experimental. Comments most welcome. > > Will probably tag 2.6.8 and 2.6.9 separately in git and cvs, push > tarballs to gnu.org, then abandon cvs to work in git on experimental, to > be merged into master. > > There are a few bogus branches from cvs2git I've left in place for the > moment (unlabeled*). It might be best to remove these and git gc the > commits at some point in the future. > > (I'm using Egg, the emacs git interface btw, and it seems quite handy. > If anyone has a better tool, I'd be interested.) > > Take care, > -- > Camm Maguire > c...@maguirefamily.org > ========================================================================== > "The earth is but one country, and mankind its citizens." -- Baha'u'llah > > _______________________________________________ > Gcl-devel mailing list > Gcl-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/gcl-devel > > > > > -- Camm Maguire c...@maguirefamily.org ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org https://lists.gnu.org/mailman/listinfo/gcl-devel
