Re: [elephant-devel] 0.6.1 / OpenMCL / BDB

2007-01-24 Thread lists
I did (push :macosx *features*) as well as (push :darwin *features*) and in both instances, it failed to load the .so library. I guess somehow, UFFI still doesn't recognize it to use .dylib (and .dylib was not generated either). Very strange. Is there another way of "pushing" stuff into *feature

Re: [elephant-devel] 0.6.1 / OpenMCL / BDB

2007-01-24 Thread Ian Eslick
This is a problem with assumptions about *features* On Darwin we should be loading .dylib which is generated by the - bundle option to gcc/ld UFFI looks for tags in *features* as follows to determine the lib type to load: (defun foreign-library-types () "Returns list of string naming pos

[elephant-devel] 0.6.1 / OpenMCL / BDB

2007-01-24 Thread lists
I have been trying to make 0.6.1 work under OpenMCL Version 1.1-pre-061231 (DarwinX8664). However, as I mentioned before, I have been having compilation problems. They seem to be mainly related to libmemutil. Out of the box attempt, I got the following error: ; $ /usr/bin/gcc -shared -Wall -fP

Re: [elephant-devel] sbcl-64 tests

2007-01-24 Thread Henrik Hjelte
On Tue, 2007-01-23 at 20:09 -0500, Ian Eslick wrote: > I was in the middle of doing some similar changes in memutil to > support 64-bit (the files are still local on my machine). Marco > Baringer also did some work on 64-bit compliance. Are you willing/ > ready to forward your changes to me

Re: [elephant-devel] osx 32bit testing

2007-01-24 Thread Kilian Sprotte
Am 24.01.2007 um 11:24 schrieb Kilian Sprotte: I am attaching the complete test dribble for openmcl as well. Sorry, I am in a hurry right now - I might find a better way to describe those type errors that appear in the the test results, or possibly send diffs Actually, the first type