"import declaration not implemented for this Lisp"

[binghe]

Hi,

I'm trying to compile open-axiom by LispWorks. Basically I modified core.lisp.in and related Makefiles (c.f. [1] for details) to support LispWorks. But then I met the following error message that I couldn't locate the root cause:

/Applications/Xcode.app/Contents/Developer/usr/bin/make interpsys
../../src/driver/open-axiom --execpath=../../x86_64-apple-darwin15.6.0/bin/bootsys --syslib=../../x86_64-apple-darwin15.6.0/lib \
		--compile --output=sys-os.64xfasl --load-directory=. ../../../source/src/interp/sys-os.boot
LispWorks(R): The Common Lisp Programming Environment
Copyright (C) 1987-2017 LispWorks Ltd.  All rights reserved.
Version 7.1.1
Saved by binghe as bootsys, at 05 Jun 2019 16:44
User binghe on binghe-mac5.local
fatal error: import declaration not implemented for this Lisp
make[3]: *** [sys-os.64xfasl] Error 1
make[2]: *** [all-interpsys] Error 2
make[1]: *** [all-interpsys] Error 2
make: *** [all-local] Error 2

Could you please give me some hints?

--
Chun Tian

[1] https://github.com/binghe/open-axiom/tree/lispworks

[oldk1331]

Hi, to support a new lisp (LispWorks) for AXIOM or its forks, I think your best shot is to begin with https://github.com/nilqed/fricas0 (that's for FriCAS, of course). I'm interested in your findings and willing to help to add LispWorks support in FriCAS.

[binghe]

Hi @oldk1331 , thanks for pointing me to fricas0, that's very interesting! Actually I wanted to build an AXIOM variant in LispWorks and then generate a DLL, so that it can be called from my other C-based front-ends. I'll try to port fricas0 to LispWorks by myself first, and if I met any issue I'll ask your help by sending issues to your Git repository. --Chun

[GabrielDosReis]

@binghe I am not familiar with LispWorks internals; will look into it.

@oldk1331 OpenAxiom is still a good place to look into AXIOM variants; I wouldn't go to other panAxiom places and tell people to go elsewhere - each has its focus.

[ip1981]

Re:

open-axiom/src/boot/strap/ast.clisp

Lines 3855 to 3864 in 467b6fb

	(COND
	((|%hasFeature| :GCL) (|genGCLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :SBCL) (|genSBCLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :CLISP)
	(|genCLISPnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :ECL) (|genECLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :CLOZURE)
	(|genCLOZUREnativeTranslation| |op| |s| |t| |op'|))
	(T
	(|fatalError| "import declaration not implemented for this Lisp")))))))

and

open-axiom/src/boot/ast.boot

Lines 1951 to 1956 in 467b6fb

	%hasFeature KEYWORD::GCL => genGCLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::SBCL => genSBCLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::CLISP => genCLISPnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::ECL => genECLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::CLOZURE => genCLOZUREnativeTranslation(op,s,t,op')
	fatalError '"import declaration not implemented for this Lisp"

[binghe]

Re:

open-axiom/src/boot/strap/ast.clisp

Lines 3855 to 3864 in 467b6fb

	(COND
	((|%hasFeature| :GCL) (|genGCLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :SBCL) (|genSBCLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :CLISP)
	(|genCLISPnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :ECL) (|genECLnativeTranslation| |op| |s| |t| |op'|))
	((|%hasFeature| :CLOZURE)
	(|genCLOZUREnativeTranslation| |op| |s| |t| |op'|))
	(T
	(|fatalError| "import declaration not implemented for this Lisp")))))))

and

open-axiom/src/boot/ast.boot

Lines 1951 to 1956 in 467b6fb

	%hasFeature KEYWORD::GCL => genGCLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::SBCL => genSBCLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::CLISP => genCLISPnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::ECL => genECLnativeTranslation(op,s,t,op')
	%hasFeature KEYWORD::CLOZURE => genCLOZUREnativeTranslation(op,s,t,op')
	fatalError '"import declaration not implemented for this Lisp"

Hi,

thank you very much for your help. This is very helpful, perhaps just filling the gaps with LispWorks-specific functions the entire OpenAxiom will work. (I really should have done the same search (not that hard) 3 years ago before raising this issue ticket.)

P. S. I'm still learning how to use Axiom and these days I'm just using the original Axiom built by GCL. (Fortunately I'm good enough there to build it by myself in recent operating systems [1], and I tried to send some patches to the original Axiom maintainers.)

Regards,

Chun Tian

[1] https://github.com/binghe/axiom-cas/releases

[GabrielDosReis]

thank you very much for your help. This is very helpful, perhaps just filling the gaps with LispWorks-specific functions the entire OpenAxiom will work. (I really should have done the same search (not that hard) 3 years ago before raising this issue ticket.)

Were you able to make the modifications needed?

[binghe]

thank you very much for your help. This is very helpful, perhaps just filling the gaps with LispWorks-specific functions the entire OpenAxiom will work. (I really should have done the same search (not that hard) 3 years ago before raising this issue ticket.)

Were you able to make the modifications needed?

Yes, I will do it in next days.

[GabrielDosReis]

Yes, I will do it in next days.

Thanks! That would be helpful.

[binghe]

Greetings, the actual work here is to implement the function genLISPWORKSnativeTranslation w.r.t. LispWorks-specific code for handling foreign functions. I'm still investigating on the differences between FFI of SBCL, CCL and LispWorks, together with the special grammar of AXIOM programming language. Please allow for more days.