<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
I put the patch on the project website.<BR>
<BR>
<BR>
<BR>
On Mon, 2006-02-06 at 12:43 -0500, Ian Eslick wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">The .dylib extension change failed due to the missing or statement in</FONT>
<FONT COLOR="#000000">sleepycat.lisp. The Makefile should be fine as it is. This was perhaps</FONT>
<FONT COLOR="#000000">a superfluous change - but I wanted to be clear about what kind of files</FONT>
<FONT COLOR="#000000">were what.</FONT>
<FONT COLOR="#000000">Ian</FONT>
<FONT COLOR="#000000">Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">> Excellent! I bet Ian can figure out a more robust way to write the</FONT>
<FONT COLOR="#000000">> makefile....</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> On Mon, 2006-02-06 at 10:11 -0500, Waldo Rubinstein wrote:</FONT>
<FONT COLOR="#000000">>> Yeah. I would assume it would have to be something like that. I know</FONT>
<FONT COLOR="#000000">>> I can change the build to produce .so files, but I thought this</FONT>
<FONT COLOR="#000000">>> change was made intentionally to produce .dylibs and that's the</FONT>
<FONT COLOR="#000000">>> reason I didn't want to touch it.</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> Anyway, when I run uname -a I get:</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> waldo:~ waldo$ uname -a</FONT>
<FONT COLOR="#000000">>> Darwin waldo.local 8.4.0 Darwin Kernel Version 8.4.0: Tue Jan 3</FONT>
<FONT COLOR="#000000">>> 18:22:10 PST 2006; root:xnu-792.6.56.obj~1/RELEASE_PPC Power</FONT>
<FONT COLOR="#000000">>> Macintosh powerpc</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> Simply changing the EXT variable to so makes it work just fine.</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> BTW, once that change is in place, I ran the BDB tests and they all</FONT>
<FONT COLOR="#000000">>> ran fine on OpenMCL:</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> ELE-TESTS> (do-all-tests-spec *testdb-path*)</FONT>
<FONT COLOR="#000000">>> Doing 106 pending tests of 106 tests total.</FONT>
<FONT COLOR="#000000">>> FIXNUMS FIXNUM-TYPE-1 BIGNUMS FLOATS RATIONALS BASE-STRINGS STRINGS</FONT>
<FONT COLOR="#000000">>> SYMBOLS CHARS PATHNAMES CONSES HASH-TABLES-1 HASH-TABLES-2 ARRAYS-1</FONT>
<FONT COLOR="#000000">>> ARRAYS-2 TEST-DEEP-EQUALP OBJECTS CIRCULAR PERSISTENT</FONT>
<FONT COLOR="#000000">>> NON-TRANSIENT-CLASS-SLOT-1 NON-TRANSIENT-CLASS-SLOT-2</FONT>
<FONT COLOR="#000000">>> TRANSIENT-CLASS-SLOT</FONT>
<FONT COLOR="#000000">>> CLASS-DEFINERS BAD-INHERITENCE MIXES MIXES-RIGHT-SLOTS INHERIT</FONT>
<FONT COLOR="#000000">>> INHERIT-RIGHT-SLOTS INITFORM-CLASSES INITFORM-TEST INITARG-TEST</FONT>
<FONT COLOR="#000000">>> NO-EVAL-INITFORM REDEFCLASS MAKUNBOUND UPDATE-CLASS CHANGE-CLASS</FONT>
<FONT COLOR="#000000">>> CHANGE-CLASS2 CHANGE-CLASS3 BASICPERSISTENCE TESTOID BTREE-MAKE BTREE-PUT</FONT>
<FONT COLOR="#000000">>> BTREE-GET REMOVE-KV REMOVED MAP-BTREE INDEXED-BTREE-MAKE ADD-INDICES</FONT>
<FONT COLOR="#000000">>> TEST-INDICES INDEXED-PUT INDEXED-GET SIMPLE-SLOT-GET</FONT>
<FONT COLOR="#000000">>> INDEXED-GET-FROM-SLOT1 INDEXED-GET-FROM-SLOT2 REMOVE-KV-INDEXED</FONT>
<FONT COLOR="#000000">>> NO-KEY-NOR-INDICES REMOVE-KV-FROM-SLOT1 NO-KEY-NOR-INDICES-SLOT1</FONT>
<FONT COLOR="#000000">>> REMOVE-KV-FROM-SLOT2 NO-KEY-NOR-INDICES-SLOT2 MAP-INDEXED GET-FIRST</FONT>
<FONT COLOR="#000000">>> GET-FIRST2 GET-LAST GET-LAST2 SET SET2 SET-RANGE SET-RANGE2 REM-KV</FONT>
<FONT COLOR="#000000">>> REM-IDEXKV MAKE-INDEXED2 ADD-INDICES2 PUT-INDEXED2 GET-INDEXED2</FONT>
<FONT COLOR="#000000">>> GET-FROM-INDEX3 DUP-TEST NODUP-TEST PREV-NODUP-TEST PNODUP-TEST</FONT>
<FONT COLOR="#000000">>> PPREV-NODUP-TEST CUR-DEL1 INDEXED-DELETE TEST-DELETED INDEXED-DELETE2</FONT>
<FONT COLOR="#000000">>> TEST-DELETED2 CUR-DEL2 GET-BOTH PGET-BOTH PGET-BOTH-RANGE PCURSOR</FONT>
<FONT COLOR="#000000">>> NEWINDEX</FONT>
<FONT COLOR="#000000">>> PCURSOR2 ADD-GET-REMOVE ADD-GET-REMOVE-SYMBOL EXISTSP PREPARES-SLEEPYCAT</FONT>
<FONT COLOR="#000000">>> TEST-SEQ1 TEST-SEQ2 CLEANSUP-SLEEPYCAT REMOVE-ELEMENT MIGRATE1 MIGRATE2</FONT>
<FONT COLOR="#000000">>> MIGRATE3 MIGRATE4 MIGRATE5</FONT>
<FONT COLOR="#000000">>> No tests failed.</FONT>
<FONT COLOR="#000000">>> T</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> - Waldo</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>> On Feb 6, 2006, at 9:43 AM, Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>>> The makefile makes a switch based on what "uname -s" returns from</FONT>
<FONT COLOR="#000000">>>> the shell.</FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>> What does it return from your system?</FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>> It looks like Ian put this in, and perhaps his Mac version is</FONT>
<FONT COLOR="#000000">>>> different than yours.</FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>> I personally have zero knowledge of dylibs vs. .so's or anything</FONT>
<FONT COLOR="#000000">>>> else relating</FONT>
<FONT COLOR="#000000">>>> to Mac stuff.</FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>> You can change the Makefile easily enough to produce the .so, by</FONT>
<FONT COLOR="#000000">>>> assigning to</FONT>
<FONT COLOR="#000000">>>> the EXT variable, for example.</FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>></FONT>
<FONT COLOR="#000000">>>> On Mon, 2006-02-06 at 09:12 -0500, Waldo Rubinstein wrote:</FONT>
<FONT COLOR="#000000">>>>> In the previous versions of elephant, "make" built the</FONT>
<FONT COLOR="#000000">>>>> corresponding .so files. In this latest version, it builds .dylib</FONT>
<FONT COLOR="#000000">>>>> files (at least on my Mac).</FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>> I did correct the controller.lisp and bdb-enable.lisp to point to</FONT>
<FONT COLOR="#000000">>>>> the new elephant library path instead of the elephant-0.3 path.</FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>> However, it still complaints about not finding libmemutil.so. It's</FONT>
<FONT COLOR="#000000">>>>> like it doesn't even bother to look for libmemutil.dylib.</FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>> - Waldo</FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>> On Feb 6, 2006, at 8:55 AM, Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>>> I'm a little confused by this; other than the default path, I</FONT>
<FONT COLOR="#000000">>>>>> don't think we changed</FONT>
<FONT COLOR="#000000">>>>>> changed anything related to this from the most recent version that</FONT>
<FONT COLOR="#000000">>>>>> you tested.</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> Here are two additional questions:</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> 1) Does libmemutil.so exist on your system? If so, does the</FONT>
<FONT COLOR="#000000">>>>>> *elephant-lib-path*</FONT>
<FONT COLOR="#000000">>>>>> correctly point to it?</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> 2) If you run "make", does it not build libmemutil.so?</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> I suspect this is more an installation/path issue than a problem. </FONT>
<FONT COLOR="#000000">>>>>> The released version</FONT>
<FONT COLOR="#000000">>>>>> is only slightly different than the version you tested a few days ago.</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> Waldo wrote:</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> Just downloaded this version and already ran into a little problem.</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> The new sleepycat libraries are built with .dylib extension for</FONT>
<FONT COLOR="#000000">>>>>> Mac OSX. However, when I launch OpenMCL, it complaints that it</FONT>
<FONT COLOR="#000000">>>>>> cannot find libmemutil.so and does not even look for libmemutil.dylib.</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> It looks like the actual elephant library is not synchronized with</FONT>
<FONT COLOR="#000000">>>>>> the Makefile, or something like that.</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> Thanks,</FONT>
<FONT COLOR="#000000">>>>>> Waldo</FONT>
<FONT COLOR="#000000">>>>>></FONT>
<FONT COLOR="#000000">>>>>> On Mon, 2006-02-06 at 01:19 -0500, Waldo Rubinstein wrote:</FONT>
<FONT COLOR="#000000">>>>>>> I had noticed that I changed it to point to the .dylib path, but</FONT>
<FONT COLOR="#000000">>>>>>> it still failed.</FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>> BTW, OpenMCL's *features*:</FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>> ? *features*</FONT>
<FONT COLOR="#000000">>>>>>> (:ASDF :PRIMARY-CLASSES :CCL :CCL-2 :CCL-3 :CCL-4 :CORAL</FONT>
<FONT COLOR="#000000">>>>>>> :COMMON-LISP :MCL :OPENMCL :ANSI-CL :PROCESSES :UNIX</FONT>
<FONT COLOR="#000000">>>>>>> :OPENMCL-NATIVE-THREADS :OPENMCL-PARTIAL-MOP</FONT>
<FONT COLOR="#000000">>>>>>> :MCL-COMMON-MOP-SUBSET :OPENMCL-MOP-2 :POWERPC :PPC-TARGET</FONT>
<FONT COLOR="#000000">>>>>>> :PPC-CLOS :PPC32-TARGET :PPC32-HOST :DARWINPPC-TARGET</FONT>
<FONT COLOR="#000000">>>>>>> :DARWINPPC-HOST :DARWIN :POWEROPEN-TARGET :32-BIT-TARGET</FONT>
<FONT COLOR="#000000">>>>>>> :32-BIT-HOST :BIG-ENDIAN-TARGET :BIG-ENDIAN-HOST</FONT>
<FONT COLOR="#000000">>>>>>> :OPENMCL-PRIVATE-HASH-TABLES)</FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>> - Waldo</FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>> On Feb 5, 2006, at 11:13 PM, Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>> Also I changed the default directory from "elephant-0-3" to just</FONT>
<FONT COLOR="#000000">>>>>>>> "elephant" at the</FONT>
<FONT COLOR="#000000">>>>>>>> end of the path, that might create a problem for someone. I</FONT>
<FONT COLOR="#000000">>>>>>>> should have documented</FONT>
<FONT COLOR="#000000">>>>>>>> that more thoroughly.</FONT>
<FONT COLOR="#000000">>>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>> On Sun, 2006-02-05 at 23:03 -0500, Ian Eslick wrote:</FONT>
<FONT COLOR="#000000">>>>>>>>> Does OpenMCL use darwin or macosx in the *features* variable? In</FONT>
<FONT COLOR="#000000">>>>>>>>> sleepycat.lisp there's a #+macosx and #-macosx around the form assigned</FONT>
<FONT COLOR="#000000">>>>>>>>> to *c-library-extension* which is used to figure out which library type</FONT>
<FONT COLOR="#000000">>>>>>>>> to load (dylib or so). If you modify this to #+(or macosx darwin) that</FONT>
<FONT COLOR="#000000">>>>>>>>> should fix it. I'll look around for other macosx only reader</FONT>
<FONT COLOR="#000000">>>>>>>>> conditionals I stuck in there. Under Allegro they use macosx and not</FONT>
<FONT COLOR="#000000">>>>>>>>> darwin.</FONT>
<FONT COLOR="#000000">>>>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>>> Does OpenMCL require dylibs or so's?</FONT>
<FONT COLOR="#000000">>>>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>>> Ian</FONT>
<FONT COLOR="#000000">>>>>>>>></FONT>
<FONT COLOR="#000000">>>>>>>>> Waldo Rubinstein wrote:</FONT>
<FONT COLOR="#000000">>>>>>>>> > Just downloaded this version and already ran into a little problem.</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > The new sleepycat libraries are built with .dylib extension for Mac</FONT>
<FONT COLOR="#000000">>>>>>>>> > OSX. However, when I launch OpenMCL, it complaints that it cannot find</FONT>
<FONT COLOR="#000000">>>>>>>>> > libmemutil.so and does not even look for libmemutil.dylib.</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > It looks like the actual elephant library is not synchronized with the</FONT>
<FONT COLOR="#000000">>>>>>>>> > Makefile, or something like that.</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > Thanks,</FONT>
<FONT COLOR="#000000">>>>>>>>> > Waldo</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > On Feb 5, 2006, at 9:39 PM, Robert L. Read wrote:</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> >> Elephant 0.5.0 is now available under the LLGPL. </FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >> I put the following text on the project website:</FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >> The latest version is 0.5.0, release Feb. 5, 2006. It is released</FONT>
<FONT COLOR="#000000">>>>>>>>> >> under the LLGPL <<A HREF="http://opensource.franz.com/preamble.html">http://opensource.franz.com/preamble.html</A>>. This</FONT>
<FONT COLOR="#000000">>>>>>>>> >> version works with ACL, OpenMCL, and SBCL with or without Unicode</FONT>
<FONT COLOR="#000000">>>>>>>>> >> support. It has significant bug fixes over 0.4.0, especially with</FONT>
<FONT COLOR="#000000">>>>>>>>> >> respect to OpenMCL and ACL. Thanks to Andrew Blumberg, Ian Eslick,</FONT>
<FONT COLOR="#000000">>>>>>>>> >> and Waldo Rubinstein. The tutorial and documentation are improved,</FONT>
<FONT COLOR="#000000">>>>>>>>> >> but may still lag the source code in some ways.</FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >> ----</FONT>
<FONT COLOR="#000000">>>>>>>>> >> Robert L. Read, PhD read &T</FONT>
<FONT COLOR="#000000">>>>>>>>> >> robertlread.net</FONT>
<FONT COLOR="#000000">>>>>>>>> >> Consider visiting Progressive Engineering: <A HREF="http://robertlread.net/pe">http://robertlread.net/pe</A></FONT>
<FONT COLOR="#000000">>>>>>>>> >> In Austin: 912-8593 "Think</FONT>
<FONT COLOR="#000000">>>>>>>>> >> globally, Act locally." -- RBF</FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >></FONT>
<FONT COLOR="#000000">>>>>>>>> >> _______________________________________________</FONT>
<FONT COLOR="#000000">>>>>>>>> >> elephant-devel site list</FONT>
<FONT COLOR="#000000">>>>>>>>> >> <A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A> <mailto:<A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A>> <mailto:<A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A> <mailto:<A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A>>></FONT>
<FONT COLOR="#000000">>>>>>>>> >> <A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > ------------------------------------------------------------------------</FONT>
<FONT COLOR="#000000">>>>>>>>> ></FONT>
<FONT COLOR="#000000">>>>>>>>> > _______________________________________________</FONT>
<FONT COLOR="#000000">>>>>>>>> > elephant-devel site list</FONT>
<FONT COLOR="#000000">>>>>>>>> > <A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A> <mailto:<A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A>></FONT>
<FONT COLOR="#000000">>>>>>>>> > <A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
<FONT COLOR="#000000">>>>>>>>> </FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>>>></FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>>>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">>></FONT>
<FONT COLOR="#000000">> ------------------------------------------------------------------------</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> _______________________________________________</FONT>
<FONT COLOR="#000000">> elephant-devel site list</FONT>
<FONT COLOR="#000000">> <A HREF="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</A></FONT>
<FONT COLOR="#000000">> <A HREF="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</A></FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>