>> Where did you get your iso image? > >Well, it is not a new and fresh install but a >up-to-date Debian sid. You can use any Debian >image [1,2], for example a "testing" [3] image >and the upgrade to "unstable/sid" with "apt". >(Make sure to load a minimal installer and not >the full software archive.)
Ok. I'll put a new debian iso and do a build. >> I'll build a virtual machine and see if I can make it fail. > >It might be some odd situation on my machine. >I started from git HEAD with git status showing >nothing new or modified. And I removed all mnt/* >before retrying. After the compilation, I have >some more files lying around: > >git status >On branch master >Your branch is up-to-date with 'origin/master'. > >Untracked files: > (use "git add <file>..." to include in what will be committed) > > Makefile.debian > Makefile.dvi > Makefile.pdf > .... Yes, I am moving the system away from noweb and some of these files are side-effects of the move that I forgot to add to the clean section. They do not matter and will be overwritten. >Oh, and my GCL is: > >GCL (GNU Common Lisp) 2.6.10 CLtL1 Jul 6 2014 00:07:47 Axiom does not use the installed GCL. It has its own copy in a tar-gzip file in the zips directory. >Hope this helps. Again, please do not waste time here. All my free time is spent working on Axiom. I don't consider it a waste of my time. I do hate it when the one of the failures gets off my desk and begins to affect other people. Poor form, that. >Obviously compiling Axiom must succeed somehow because >very new Axiom Debian packages appeared just a few days >ago [4,5]. I do not know from which version or git commit >of the Axiom source code they were build. News to me. I'll look once I build the debian virtual machine. Tim _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org https://lists.nongnu.org/mailman/listinfo/axiom-developer
