[Ecls-list] Starting swank server

2010-12-30 Thread David Dreisigmeyer
I have the following for my .eclrc: (require 'asdf) (pushnew #P"/Users/daviddreisigmeyer/.emacs.d/site-lisp/slime/" asdf:*central-registry* :test #'equal) (push "/Users/daviddreisigmeyer/.emacs.d/site-lisp/slime/" asdf:*central-registry*) (asdf:oos 'asdf:load-op 'swank) (setf s

Re: [Ecls-list] Help needed, really

2010-12-30 Thread DS
Why not check what information is put in *features* by other implementations? If OpenAxiom runs on them, then that should be enough. Keywords like :X86 and :X86-64 seem common, and this should be easy to figure out when building ECL. :ILP32 or :LP64 might be even more informative than that

Re: [Ecls-list] Help needed, really

2010-12-30 Thread Matthew Mondor
On Thu, 30 Dec 2010 10:42:43 +0100 Juan Jose Garcia-Ripoll wrote: Sorry that I didn't read the previous discussions, which most probably happened on another list (and it's unclear to me why OpenAxiom requires that implementation-dependent low-level information; why it cannot use an FFI library or

Re: [Ecls-list] Help needed, really

2010-12-30 Thread Pascal J. Bourguignon
I have no preconceived idea about your problem, however, I will note that: Juan Jose Garcia-Ripoll writes: > Since ECL does not really care about the processor type, it is fine > with it, and just works: it only relies on information provided by the > compiler, such as type sizes, alignments, a

[Ecls-list] Help needed, really

2010-12-30 Thread Juan Jose Garcia-Ripoll
I am having a now too long discussion about things that ECL should or should not do and I really need help, someone that translates or helps me understand this because we are not getting anywhere. The original problem was that OpenAxiom was not building right in OS X because it expects ECL to expo