Hi, Camm --
Thanks very much for the work and the information. I took a quick
look at https://buildd.debian.org/status/package.php?p=acl2&suite=sid,
specifically at the logs in the failure cases (ia64, kfreebsd-i386,
mips, mipsel), and in each case I found the following (or something
close to it, at least):
ACL2 Error in ACL2-INTERFACE: Unable to obtain the truename of file
"/sbuild-nonexistent/".
Error: ACL2 Halted
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by LET.
Raw Lisp Break.
Backtrace: lp > let > error > lisp:lambda-closure > APPLY
I'm pretty sure that the message is coming from ACL2 function
our-truename. One way this could happen is that ACL2 function our-pwd
is attempting to get the current directory namestring using
our-truename (which for cltl1 GCL, calls si::stat if it's fboundp),
but that directory somehow doesn't exist (odd). A more likely
possibility is that our-truename is being called on
(user-homedir-pathname), which in turn is returning nil or perhaps a
non-existent directory name.
For the future, I think I'll fix our-truename to print a message that
gives more information about why it's failing. For now, a more
complete backtrace might help.
By the way, I tried to follow your instructions on my Mac (running Mac
OS 10.6.8) after installing git, but I needed another "cd gcl". Hope
I did it right (below, "lt" is an alias for "ls -lrt"; sorry about
that).
~/lisps/gcl/2013-08-04$ git clone git://git.sv.gnu.org/gcl.git
Cloning into 'gcl'...
remote: Counting objects: 57616, done.
remote: Compressing objects: 100% (12893/12893), done.
remote: Total 57616 (delta 38402), reused 57616 (delta 38402)
Receiving objects: 100% (57616/57616), 56.82 MiB | 334.00 KiB/s, done.
Resolving deltas: 100% (38402/38402), done.
Checking connectivity... done
Checking out files: 100% (11213/11213), done.
~/lisps/gcl/2013-08-04$ lt
total 0
drwxr-xr-x 4 kaufmann staff 136 Aug 4 10:47 gcl
~/lisps/gcl/2013-08-04$ cd gcl
~/lisps/gcl/2013-08-04/gcl$ git checkout Version_2_6_9pre
Branch Version_2_6_9pre set up to track remote branch Version_2_6_9pre from
origin.
Switched to a new branch 'Version_2_6_9pre'
~/lisps/gcl/2013-08-04/gcl$ ./configure && make
bash: ./configure: No such file or directory
~/lisps/gcl/2013-08-04/gcl$ ls -l
total 0
drwxr-xr-x 70 kaufmann staff 2380 Aug 4 11:02 gcl
~/lisps/gcl/2013-08-04/gcl$
The build on my Mac seemed to succeed (hooray!). But the debugger
seems to have a problem ("illegal ihs index") when entered with
control-c (where you'll see two control-c keys echoed by emacs below),
though not when entered through an error:
~/lisps/gcl/2013-08-04/gcl/gcl$ bin/gcl
GCL (GNU Common Lisp) 2.6.9 CLtL1 Aug 4 2013 11:05:45
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License: GPL due to GPL'ed components: (READLINE UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter
Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files set to
/var/folders/kt/ktfN4HB6GeqP--4uIFkD+E+++TI/-Tmp-/
>(car 3)
Error: 3 is not of type LIST.
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by CAR.
Broken at EVAL. Type :H for Help.
>>:q
Top level.
> C-c C-c
Correctable error: Console interrupt.
Signalled by SYSTEM:TOP-LEVEL.
If continued: Type :r to resume execution, or :q to quit to top level.
Error: 4 is an illegal ihs index.
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by SYSTEM::GCL-TOP-LEVEL.
Broken at SYSTEM::GCL-TOP-LEVEL.
>>>
By the way, I forgot to include --enable-ansi with my configure
command. Maybe at this point it would be reasonable for that to be
the default?
Finaly, regarding your comment:
3) update the website with this announcement
Are you referring to http://www.gnu.org/software/gcl/? If so, then
are you referring to the "Get Latest Release" link near the top on the
left side of the page, or perhaps to the "Debian package page" below
it (which is currently a broken link)?
Thanks --
-- Matt
From: Camm Maguire <c...@maguirefamily.org>
Date: Sat, 03 Aug 2013 09:20:50 -0400
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
