[Openmcl-devel] preparing 1.5 release

[Gary Byers]

This -has- come up before (though it may have been a while); it may
depend on what system is used to build the kernel binaries in the
distribution.

It probably has to do with the version of libc that was installed on
the machine that the kernel was built on (relative to the version
that's installed on the machine that you have there.)  If there's a
way to tell the C compiler/linker on Linux that "any reasonably recent
version of any of these libraries is OK, our use of the stuff in them
is pretty vanilla", I don't know what it is; we wind up with version
dependencies that we don't really want (and probably don't really need
to have.)

The workaround in cases like this is to just build the lisp kernel on
the machine(s) you want to run it on:

$ cd ccl/lisp-kernel/linuxx8664
$ make clean; make

If anyone knows of compiler/linker options that can be used to avoid
this nonsense (to say "any reasonably recent version of these libraries
is fine ...), please let us know.



On Thu, 15 Apr 2010, David L. Rager wrote:

> When running the 1.5 RC on linux x86-64, I get the following error message:
>
> uvanimor-0.cs.utexas.edu:/projects/hvg/ragerdl/hvg2/lisps/ccl-1.5-rc$
> scripts/ccl64
> /projects/hvg/ragerdl/hvg2/lisps/ccl-1.5-rc/lx86cl64: /lib/libc.so.6:
> version `GLIBC_2.4' not found (required by
> /projects/hvg/ragerdl/hvg2/lisps/ccl-1.5-rc/lx86cl64)
> uvanimor-0.cs.utexas.edu:/projects/hvg/ragerdl/hvg2/lisps/ccl-1.5-rc$
>
> Any idea why this is just now a problem in 1.5 and has never been an
> issue before?  Thanks!
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>