layne@unf5.UUCP (Layne Wallace) (10/15/87)
Has anyone brought Kyoto Common Lisp up on a 3B machine? I keep getting an
error along the lines of:
bad bigsize: 012
Is there a parameter I haven't set correctly? And, if so, what and how do I
correct this?
Please send responses by email and I'll be glad to pass solutions on to others
in the same boat as myself.
Thanks,
Layne Wallace uucp: decvax!ucf-cs!unf5!lwallace
Division of Computer and Information Sciences Univ. of North Florida
(904) 646-2987eer@ritcv.UUCP (Ed Reed) (10/17/87)
In article <3@unf5.UUCP> layne@unf5.UUCP (Layne Wallace) writes: >Has anyone brought Kyoto Common Lisp up on a 3B machine? I keep getting an >error along the lines of: > > bad bigsize: 012 > Let's be more specific - when you say 3B machine, do you mean... Unix PC (7300) 3B1 (both those are 68010 machines from Convergent Technologies, with CT's Sys V) 3B2 (family of WE32000 chip computers from ATT) There's a difference. The distribution tape we got was for the 3B2, and except for some .h file errors in the ATT supplied include libraries, was almost ok. Took a day or so to track down all the little discrepancies. One noteable prblem was that the linker has an upper limit to the string table size in the bound unit, which was exceeded under some linking circumstances - I've forgotten now just how we got around that...maybe someone else can fill you in. I'm presently finishing porting Kyoto to the 3B1 family machines and have the interpretor running just fine - big issue there was that the Convergent linker padds segment to nice even starting offset addresses in the a.out file, and correctly documents that fact in the section headers, but the unixsave.c routine in the 3B2 sources didnot allow for that - had to rewrite unixsave to work. The only problem I'm having now is getting compiled code to fasl correctly - looks like I've got some more pointer/offset problems that I havent tracked yet - I can load init files okay (lisp code compiled and distributed as c source that I only have to load the lisp data vector from) but when I write my own lisp function "foo" (well, "fib", actually) and compile it with my own running compiler and then load the resulting object file - it blows up trying to execute the init code generated by the compiler for my function. The other advise for you if you're working with 3B1 machines - 20MB is too little. Need at least the 40 MB drive to have enough room to develop/debug Kyoto. Good luck. I'd also be interested in hearing from anyone else working on the 3B1 port. Ed Reed -- ------------------------------------------------- Ed Reed - Rochester Institute of Technology phone: (716) 334-3006 Delphi: EERTEST GEnie: SQA.INC Usenet: ...rochester!ritcv!eer -------------------------------------------------
eric@ms.uky.edu (Eric Herrin) (10/18/87)
>From: eer@ritcv.UUCP (Ed Reed) >Good luck. I'd also be interested in hearing from anyone else >working on the 3B1 port. I have the KCL port finished to the point where you are stuck also... I have been stuck at this point for some time (admittedly, I have been devoting much time to it since the interpreter works fine...) on my 3B1. If you (or anyone) track it down before I do, I would appreciate the result. eric -- | Eric Herrin II cbosgd!ukma!eric | | "'tis better to be silent eric@UKMA.BITNET | | and be THOUGHT a fool, than to open eric@ms.uky.csnet | | one's mouth and remove all doubt." eric@ms.uky.edu |