From fahree at gmail.com  Thu Nov 29 19:03:05 2012
From: fahree at gmail.com (=?ISO-8859-1?Q?Far=E9?=)
Date: Thu, 29 Nov 2012 14:03:05 -0500
Subject: [xcvb-devel] [asdf-devel] ASDF-bundle and cross-compiling with
	ECL
In-Reply-To: <6CFD6EE3-967E-4165-94EF-A1192BCB3BF4@gmail.com>
References: <7F5F65CA-2B56-4083-AC87-EAA8D739CE67@gmail.com>
	<CAN7nBXcWCyeq=L3mn94GJY7EaoQ0KPaefLi5auX2QG-P3M1O0w@mail.gmail.com>
	<6CFD6EE3-967E-4165-94EF-A1192BCB3BF4@gmail.com>
Message-ID: <CAN7nBXd8VLNVunH0+CTPgNsOEzCHuy4i4av-JiL=YgpZVmH3gQ@mail.gmail.com>

On Thu, Nov 29, 2012 at 12:03 PM, Sylvain Ageneau <ageneau at gmail.com> wrote:
> Thanks for your answer.
>
> Yes I'm definitely interested. I started playing around with the latest (0.596) xcvb release and it looks like it can already almost do what I need.
>
If you pull from xcvb,
I have a trivial patch to remove grain-sets from the build.
It's quite possible I packaged the xcvb tarball
before I pushed fare-quasiquote to the public git ? my mistake,
and pulling should fix it indeed.

> After that I tried bootstrapping xcvb using the latest ECL trunk and ran into issues apparently related to closer-mop (I'm guessing this has to do with the latest mop changes in ECL). For what I'm trying to achieve I don't necessarily need to compile xcvb itself using ECL anyway right?
>
xcvb was not ported to compile with ECL as a host;
please use SBCL or CCL, or else CLISP if neither is available on your platform.

> --> Updated asdf to the latest revision (2.26.3), also removed the form (:when (:featurep :ecl) "asdf-ecl") in build.xcvb
>
Thanks. This is fixed in asdf 2.26.4.

> At this point xcvb manages to compile alexandria. There's a bunch of warnings "xcvb-driver::get-optimization-settings does not support your implementation. Please help me fix that.".
>
Fixed in xcvb HEAD.

> Next I tried with cffi. It fails apparently when trying to compile babel's "package.lisp" file:
>
>
> The value SB-IMPL::BACKQ-LIST is not of type CHARACTER.
Ooops, there was a spurious backquote in dependencies-interpreter.lisp.
Fixed in xcvb HEAD.

Still, when I get past it, I find that XCVB ends up
trying to load a .so the wrong way.
The CFFI and/or dynamic library support has bitrotten
(if it ever worked on ECL).
I see that compiling CFFI now fails on SBCL, too,
and at least requires re-merging a newer CFFI for xcvb.

I will investigate.

> Also If I understand correctly if I want to do cross-compilation, I need to provide a setup.lisp file that configures ecl as a cross compiler.
> I tried with a simple "setup.lisp" containing:
>
> #+xcvb (module (:depends-on ("package")))
> (setf common-lisp:*features* (cons :android common-lisp:*features*))
>
>
> But I get:
> xcvb simple-build -l ecl --setup /alexandria/setup --build /alexandria
> BORK:
> Simple Dispatcher[linkable-dependency]: Error: No associated dispatch function for the keyword in car position of expression (:LISP "/alexandria/setup")
>
> (same works fine if using sbcl)
>
That's weird. I will investigate.

I'm sorry XCVB is not ready for you yet :-(
I will get back to you...

??? ? Fran?ois-Ren? ?VB Rideau ?Reflection&Cybernethics? http://fare.tunes.org
What we Are is God's gift to us.
What we Become is our gift to God.