[Openmcl-devel] problems compiling OpenMCL from CVS

[Gary Byers]

On 14 Apr 2003, Marco Baringer wrote:

>
> using a fresh copy of the sources and OpenMCL 13.4 to build (this is
> all on 10.2.4.
>
> When trying (ccl::compile-ccl t) i get an error about
> #P"ccl:l1;level-1.lisp.newest" not being found. ccl::xcompile-ccl
> gives the same problem. The directory #P"ccl:l1;" does not exist, but

In the standard translations for the "CCL" host, "ccl:l1;" maps
to the level-1 directory.

> l1-dfsls, l1-pfsls, l1-sfsls and l1f do exist. Looking at
> lib/systems.lisp leads me to believe l1 and level-1 are getting mixed
> up.
>
> When trying (ccl::xload-level-0) it creates ccl:ccl;ppc-boot.image,
> not ccl:ppc-boot.image as the docs would have me believe.
>
> ----
>
> Here's a dribble of my attempt to compile ccl from CVS:
>
> 1) define CCL to be a logical host mapping to my cvs directory

I've actually never done this: my CCL directory and my CCL directory
are one and the same.

You'd presumably find this easiest if you ensured that the logical
host translations for your newly-defined CCL: host matched the builtin
one.  It might be a bit easier to simply clobber the builtin CCL:
hosts translations ...

Since the physical pathnames to which "CCL" and its subdirectories
map depend on where the "CCL_DEFAULT_DIRECTORY" environment variable
points (and "HOME"'s translations depend on the location of the
user's home directory), there's already a sleazy way to "re-root"
the translations in an existing logical host.  (See the function
CCL::INIT-LOGICAL-DIRECTORIES in "ccl:l1;l1-boot-1.lisp"; this function
is ordinarily called every time an image starts up.
CCL::INIT-LOGICAL-DIRECTORIES calls CCL::REPLACE-BASE-TRANSLATION to
do the dirty work.)

So,

(ccl::replace-base-translation "ccl:" "/path/to/your/cvs/tree/")

should make "ccl:" point to your CVS tree, and "ccl:l1;" point to its
level-1/ directory, etc.

>
> 2) from within openmcl run (ccl::xload-level-0)
>
> 3) symlink ccl:level-1 to ccl:l1
>
> 4) run (ccl::xcompile-ccl t)
>
> 5) move #P"ccl:ccl;ppc-boot.image" to #P"ccl:ppc-boot.image"
>
> 6) run ./dppccl ppc-boot.image (being unsure about what to do with the
>    files #P"ccl:ccl;level-1.dfsl" and #P"ccl:ccl;runtime.dfsl"
>
> Watch as step 6 leads to an error about
> ./l1-dfsls/ppc-callback-support.dfsl not existing (I didn't find it
> anywhere in the ccl tree).
>
> 7) go do what they pay me for :)
>
> --
> -Marco
> Ring the bells that still can ring.
> Forget your perfect offering.
> There is a crack in everything.
> That's how the light gets in.
>      -Leonard Cohen
>
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel
>
>


_______________________________________________
Openmcl-devel mailing list
Openmcl-devel at clozure.com
http://clozure.com/cgi-bin/mailman/listinfo/openmcl-devel