Re: [Axiom-developer] Re: Debian axiom build failures

2009-03-08 Thread root
Camm, Did you ever get a chance to try make clean make NOISE= and store the log somewhere? The NOISE= option keeps the build process from throwing away standard output so we can see what might be failing. Tim ___ Axiom-developer mailing list A

[Axiom-developer] Re: Debian axiom build failures

2009-03-01 Thread root
Camm, I never implemented this change because I never understood compiler::link Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer

[Axiom-developer] Re: Debian axiom build failures

2009-03-01 Thread root
Camm, It appears that the change to read-char-no-hang no longer returns EOF in: (read-char-no-hang str nil 'eof) It returns NIL instead. Thus I cannot distinguish between the lack of a character and the end of the input data, causing an infinite loop. Tim _

[Axiom-developer] Re: Debian axiom build failures

2009-03-01 Thread root
Camm, #\Newline is a character in the input stream. If (read-char-no-hang) returns nil when there is no character and it retuns nil on a newline how can I distinguish the cases? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://l

[Axiom-developer] Re: Debian axiom build failures

2009-02-28 Thread Camm Maguire
Greetings! This is a broken alternate linking build procedure we introduced for axiom 2005 on systems where native object relocation is not yet implemented in GCL. For 2.6.8pre, this is ia64, hppa, mips, mipsel, and alpha. For 2.7.0 just ia64 and hppa remain. :native-reloc is the relevant featur

Re: [Axiom-developer] Re: Debian axiom build failures

2009-02-28 Thread Camm Maguire
Greetings! We made it ansi compliant -- specifically it ignores trailing newlines, so that (read-char-no-hang) at the prompt does not return #\Newline, but rather (read-char-no-hang) NIL >(read-char-no-hang)a #\a > Please let me know if this causes you problems. Take care, root writes: >

Re: [Axiom-developer] Re: Debian axiom build failures

2009-02-28 Thread root
Camm, In the latest version of GCL-2.6.8pre there is a change to the function READ-CHAR-NO-HANG that seems to break Axiom's new browse function. Can you tell me what changed? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://list

[Axiom-developer] Re: Debian axiom build failures

2009-02-26 Thread root
Camm, I don't understand why you are getting that error. Can you do: make clean make NOISE= and put the complete console log someplace? Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom

Re: [Axiom-developer] Re: Debian axiom build failures

2009-02-25 Thread Camm Maguire
Greetings! I'm using the latest gcl 2.6.8pre on all platforms. Aka gcl-system via the debian/rules mechanism of long ago. I've verified that the missing macro file is not relevant, and that the machine I'm working on (Debian sid ia64) is not in the list of different gcl versions. I can als check

[Axiom-developer] Re: Debian axiom build failures

2009-02-24 Thread root
Thoses gold sources certainly compile on other platforms so I'm not sure the failure lives in the Axiom source code. What version of GCL are you using? (See the top level Makefile and search for GCLVERSION Some platforms are sensitive to the version used. There are 4 version, the gcl 2.6.7, gcl2

[Axiom-developer] Re: Debian axiom build failures

2009-02-24 Thread root
Camm, > Loading /home/camm/axiom-20081101/mnt/linux/autoload/htcheck. >Warning: macro table not found What sources are you using? This bug was fixed a while ago. Tim ___ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.o