Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-19 Thread Camm Maguire
Greetings! Just wondering if there were any ideas or progress on this front. Take care, Camm Maguire <[EMAIL PROTECTED]> writes: > Greetings! > > With current cvs 2.6.8pre, I just took your patch, and changed the > GCLVERSION to gcl-system in both Makefile and Makefile.pamphlet. Then > I poin

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-16 Thread Camm Maguire
Greetings! With current cvs 2.6.8pre, I just took your patch, and changed the GCLVERSION to gcl-system in both Makefile and Makefile.pamphlet. Then I pointed the PATH to ~/gcl-2.6.8pre/bin:$PATH, set the AXIOM env variable as you instructed, and make AWK=awk. I get down to the following: tangli

[Axiom-developer] Re: noweb "bug"

2005-12-16 Thread root
> Hmmm, I don't know whether it is worth spending many hours on the spad > language. You know, I am a bit against spad. Although quite similar, > SPAD is not the same as Aldor. And I would rather like to see SPAD > replaced by Aldor. Eliminate the SPAD language in favour of Aldor. not to worry,

[Axiom-developer] Re: noweb "bug"

2005-12-16 Thread Ralf Hemmecke
i've started in on volume 2, the programmers guide which will require a complete rewrite. i've outlined it and am writing a programming example that will be carried throughout the book (a cohen algebra which i mentioned in a previous posting) Hmmm, I don't know whether it is worth spending many

[Axiom-developer] Re: noweb "bug"

2005-12-16 Thread Ralf Hemmecke
most of the steps would be: (1) PUSH THE CHANGE check out a fresh system build a pre-change copy of the system (call it old) build a second copy of the system (call it new) in new: add the awk script to etc/scripts update CHANGELOG update the etc/scripts/Makefile.pamphl

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread root
i took your suggestion and rewrote plttest.c to add the line: long findstring(char *a, char *b); but it had no effect. when you built axiom did you modify the makefiles to use GCLVERSION=gcl-2.6.8pre or did you build the lisp by hand and copy it over? or did you use your debian mod and compil

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread Camm Maguire
Greetings! Odd, I see: Loading /Users/camm/axiom/obj/MACOSX/interp/cformat.o start address -T 0xccf500 Finished loading /Users/camm/axiom/obj/MACOSX/interp/cformat.o Loading /Users/camm/axiom/obj/MACOSX/interp/cfuns.o start address -T 0xc41880 Finished loading /Users/camm/axiom/obj/MACOSX/inter

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread root
different error message. there is progress. now it is loading the lisp code that was compiled but it fails loading cfuns.o which is C code that gets compiled and linked into the image. the source is in src/lib/cfuns.c.pamphlet. the message is Loading /home/daly/macosx46/obj/MACOSX/interp/cfuns.o E

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread Camm Maguire
Greetings! OK, think I got it now, will know for sure in a bit. Might want to try a fresh update of 2.6.8pre at this point. Please keep me posted. Take care, root <[EMAIL PROTECTED]> writes: > still fails at the same spot in the same way. > > > OK, please try again with > > > > export CVSRO

[Axiom-developer] Re: noweb "bug"

2005-12-15 Thread root
> OK. Could you tell me how recent the sources are in book--main--1. > I have unfortunately never worked with tla except for 'tla get' and I am > learning very slowly. re: learning. no problem. you could even document it :-) > > If you don't mind, I'll put bookvol4 into src/doc and change every

[Axiom-developer] Re: noweb "bug"

2005-12-15 Thread Ralf Hemmecke
if you're interested in volume 4 go for it. send email and i'll help you with the details and the writing. the book--main--1 branch is probably better than the axiom--main--1 branch because we can update more frequently and the changes can be broken for a long time. we can also mirror them in src/

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread root
> But what matters is that there is just a link on the website telling > about book--main--1. I cannot remember that I have read much about the > different volumes that should be written. So why should I check out > book--main--1 if I am new to Axiom and just want to learn how I could > contrib

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread root
> it is just that any bug or fix I find in noweb will be sent to Norman > Ramsey. I will never modify the version that comes with Axiom. > I guess many people would think that way. If Tim has enough time to > maintain that version, fine with me. if you sent your fix to norman and he accepted it

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-15 Thread Ralf Hemmecke
re: advocacy ok. you're advocating a change. No, I am just complaining that you did something wrong 3 years ago. It was Ralf who was advocating a change. I just agreed with him. ;) Hmm, was I advocating? Well, my point of view is to minimise the effort of developing/maintaining axiom. As

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
still fails at the same spot in the same way. > OK, please try again with > > export CVSROOT=:pserver:[EMAIL PROTECTED]:/sources/gcl > cd gcl-2.6.8pre/o && cvs update plttest.c && make plt.o \ > && cd ../unixport && make saved_gcl > > Or try a fresh checkout if you wish. > > Please kee

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Camm Maguire
OK, please try again with export CVSROOT=:pserver:[EMAIL PROTECTED]:/sources/gcl cd gcl-2.6.8pre/o && cvs update plttest.c && make plt.o \ && cd ../unixport && make saved_gcl Or try a fresh checkout if you wish. Please keep me posted. I'll explain what is going on if you are interested

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Camm Maguire
Greetings! First let me say I'm totally fine with shipping gcl sources with axiom as is. The below is just an attempt to explore the other possibility in more detail. root <[EMAIL PROTECTED]> writes: > you ARE aware that gcl includes things like bfd, binutils, gmp, etc. > axiom isn't the only

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
Camm, further investingation shows that _feof is defined in /usr/lib/libc.dylib(feof.So) simplly definiing a file foo.lisp containing (defun foo (x y) (+ x y)) and then doing: (compile-file "foo.lisp") (load "foo.lisp") (foo 2 3) works so the breakage is more subtle. i'm continuing to inv

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
Camm, on the mac: loading /home/daly/macosx46/obj/MACOSX/interp/util.o Error: Undefined symbol "_feof" Fast links are on: do (si::use-fast-links nil) for debugging Error signalled by LOAD. Broken at LOAD. Type :H for Help. >>make[3]: *** [/home/daly/macosx46/obj/MACOSX/bin/interpsys] Error 255

[Axiom-developer] RE: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Page, Bill
Camm, On Wednesday, December 14, 2005 1:13 PM you wrote: >... > Bill Page wrote: > > Or does the Debian build actually rebuild noweb? > > I haven't touched axiom's use of noweb, apart from not shipping > special noweb binaries. You can look at a sample build log here: > > http://buildd.debian

[Axiom-developer] RE: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Page, Bill
Ralf, On Wednesday, December 14, 2005 7:56 AM you wrote: > > By the way, try the following in AXIOMROOT. > > find . -name '*.pamphlet' -exec grep "<<.*>>" {} \; > xxx.1 > grep -v ">>= *$" xxx.1 > xxx.2 > grep -v ">> *$" xxx.2 > xxx.3 > grep -v "@<<"xxx.3 > xxx.4 > wc xxx.4 >86 472 483

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
oh, and as an aside, even if you build axiom on a "native gcl" you don't need the native gcl afterward. you can erase it and axiom still works (since axiom IS a gcl image). so why force the user to install software that isn't used? t ___ Axiom-deve

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
(7) and readline isn't installed in gcl axiom has its own readline (clef) which can do "algebra command completion" and knows about axiom. clef is automatically started when axiom starts. readline interferes with clef. so if "native gcl" has readline we can't use it either. t __

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread root
you ARE aware that gcl includes things like bfd, binutils, gmp, etc. axiom isn't the only package that includes upstream sources. the only way i know to ensure that your product works as advertised is to make sure that it works when you build it. and that requires certain versions. in a perfect wo

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Ralf Hemmecke
Hi, Yes, we should simply "tell people that axiom needs at least version x.y of noweb" and version 2.6.x of gcl. These are prerequisites. Download and install them first - then install Axiom. If you are using apt-get on Debian or yum on Fedora, etc. then these prerequisites are automatically ins

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Ralf Hemmecke
Hello, root wrote: re: noweb bug i don't agree with Norman. *I* consider it a bug. especially so since Ralf fixed the same "feature" independently. noweb does the wrong thing with certain non-chunks. if the chunk isn't in the hashtable complain and continue. i diagnosed the bug,

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-14 Thread Ralf Hemmecke
By the way, try the following in AXIOMROOT. find . -name '*.pamphlet' -exec grep "<<.*>>" {} \; > xxx.1 grep -v ">>= *$" xxx.1 > xxx.2 grep -v ">> *$" xxx.2 > xxx.3 grep -v "@<<"xxx.3 > xxx.4 wc xxx.4 86 472 4836 xxx.4 Look at these 86 lines. I've only found Label: '<<' Name '>

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-13 Thread C Y
--- root <[EMAIL PROTECTED]> wrote: > sbcl just got itself working on windows. > i'm trying to build it to see if they got mcclim working. > if so, we have a cross-platform gui. Unfortunately, McCLIM currently requires clx to work (there is no Windows backend even in the works yet). > an alte

[Axiom-developer] RE: noweb "bug" (was: article "standard" header/footer)

2005-12-13 Thread Page, Bill
On Tuesday, December 13, 2005 8:17 PM Tim Daly (root) wrote: > > re: noweb bug > >i don't agree with Norman. *I* consider it a bug. >especially so since Ralf fixed the same "feature" independently. >noweb does the wrong thing with certain non-chunks. >if the chunk isn't in the has

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-13 Thread root
sbcl just got itself working on windows. i'm trying to build it to see if they got mcclim working. if so, we have a cross-platform gui. an alternative i'm also investigating is gtk+ and libglade it seems that gaim uses it and works everywhere. if they can, we can. t

Re: [Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-13 Thread C Y
--- root <[EMAIL PROTECTED]> wrote: > an alternative is to modify GCL to support UFFI (Universal > Foreign Function Interface) and modify Axiom to use it. I > looked at this path and it is a lot of work. When Axiom goes > ANSI it'll have to be done but that's still a long way in the > future and

[Axiom-developer] Re: noweb "bug" (was: article "standard" header/footer)

2005-12-13 Thread root
re: noweb bug i don't agree with Norman. *I* consider it a bug. especially so since Ralf fixed the same "feature" independently. noweb does the wrong thing with certain non-chunks. if the chunk isn't in the hashtable complain and continue. i diagnosed the bug, fixed it, and sent of