[elephant-devel] Elephant 0.5.0 is released under the LLGPL

Mon Feb 6 15:30:15 UTC 2006

Sorry Ian,

I got your previous email but didn't realize you wanted me to make  
the change to sleepycat.lisp.

Just to confirm that after changing sleepycat.lisp, as per your  
instructions, it all works fine with .dylibs and all tests ran clean  
again. You may want to commit this change.

Thanks,
Waldo

On Feb 6, 2006, at 10:22 AM, Ian Eslick wrote:

> Did you not get my earlier e-mail about adding #+(or macosx darwin)  
> to sleepycat.lisp in place of #+macosx?  That will fix it for MCL.
>
> We also need to do something about user system-specific  
> dependencies.  Folks should not have to modify sources to get  
> things personalized to their system.  One option is to use asdf- 
> config as an option which was designed to allow user config of  
> params without requiring source modification...
>
> Ian
> ___
> Sent with SnapperMail
> www.snappermail.com
>
>  ..... Original Message .......
> On Mon, 6 Feb 2006 09:12:50 -0500 "Waldo Rubinstein"  
> <waldo at trianet.net> wrote:
>> In the previous versions of elephant, "make" built the  
>> corresponding .so files. In this latest version, it builds .dylib  
>> files (at least on my Mac).
>>
>> I did correct the controller.lisp and bdb-enable.lisp to point to  
>> the new elephant library path instead of the elephant-0.3 path.
>>
>> However, it still complaints about not finding libmemutil.so. It's  
>> like it doesn't even bother to look for libmemutil.dylib.
>>
>> - Waldo
>>
>> On Feb 6, 2006, at 8:55 AM, Robert L. Read wrote:
>>
>>
>> I'm a little confused by this; other than the default path, I  
>> don't think we changed
>> changed anything related to this from the most recent version that  
>> you tested.
>>
>> Here are two additional questions:
>>
>> 1)  Does libmemutil.so exist on your system?  If so, does the  
>> *elephant-lib-path*
>> correctly point to it?
>>
>> 2)  If you run "make", does it not build libmemutil.so?
>>
>> I suspect this is more an installation/path issue than a problem.   
>> The released version
>> is only slightly different than the version you tested a few days  
>> ago.
>>
>>
>>
>> Waldo wrote:
>>
>> Just downloaded this version and already ran into a little problem.
>>
>>
>> The new sleepycat libraries are built with .dylib extension for  
>> Mac OSX. However, when I launch OpenMCL, it complaints that it  
>> cannot find libmemutil.so and does not even look for  
>> libmemutil.dylib.
>>
>>
>> It looks like the actual elephant library is not synchronized with  
>> the Makefile, or something like that.
>>
>>
>> Thanks,
>> Waldo
>>
>> On Mon, 2006-02-06 at 01:19 -0500, Waldo Rubinstein wrote:
>> I had noticed that I changed it to point to the .dylib path, but  
>> it still failed.
>>
>>
>> BTW, OpenMCL's *features*:
>>
>>
>> ? *features*
>> (:ASDF :PRIMARY-CLASSES :CCL :CCL-2 :CCL-3 :CCL-4 :CORAL :COMMON- 
>> LISP :MCL :OPENMCL :ANSI-CL :PROCESSES :UNIX :OPENMCL-NATIVE- 
>> THREADS :OPENMCL-PARTIAL-MOP :MCL-COMMON-MOP-SUBSET :OPENMCL- 
>> MOP-2 :POWERPC :PPC-TARGET :PPC-CLOS :PPC32-TARGET :PPC32- 
>> HOST :DARWINPPC-TARGET :DARWINPPC-HOST :DARWIN :POWEROPEN-TARGET : 
>> 32-BIT-TARGET :32-BIT-HOST :BIG-ENDIAN-TARGET :BIG-ENDIAN- 
>> HOST :OPENMCL-PRIVATE-HASH-TABLES)
>>
>>
>> - Waldo
>>
>> On Feb 5, 2006, at 11:13 PM, Robert L. Read wrote:
>>
>> Also I changed the default directory from "elephant-0-3" to just  
>> "elephant" at the
>> end of the path, that might create a problem for someone.  I  
>> should have documented
>> that more thoroughly.
>>
>>
>> On Sun, 2006-02-05 at 23:03 -0500, Ian Eslick wrote:
>> Does OpenMCL use darwin or macosx in the *features* variable? In  
>> sleepycat.lisp there's a #+macosx and #-macosx around the form  
>> assigned to *c-library-extension* which is used to figure out  
>> which library type to load (dylib or so). If you modify this to #+ 
>> (or macosx darwin) that should fix it. I'll look around for other  
>> macosx only reader conditionals I stuck in there. Under Allegro  
>> they use macosx and not darwin. Does OpenMCL require dylibs or  
>> so's? Ian Waldo Rubinstein wrote: > Just downloaded this version  
>> and already ran into a little problem. > > The new sleepycat  
>> libraries are built with .dylib extension for Mac > OSX. However,  
>> when I launch OpenMCL, it complaints that it cannot find >  
>> libmemutil.so and does not even look for libmemutil.dylib. > > It  
>> looks like the actual elephant library is not synchronized with  
>> the > Makefile, or something like that. > > Thanks, > Waldo > > On  
>> Feb 5, 2006, at 9:39 PM, Robert L. Read wrote: > >> Elephant 0.5.0  
>> is now available under the LLGPL. >> >> I put the following text  
>> on the project website: >> >> >> The latest version is 0.5.0,  
>> release Feb. 5, 2006. It is released >> under the LLGPL <http:// 
>> opensource.franz.com/preamble.html>. This >> version works with  
>> ACL, OpenMCL, and SBCL with or without Unicode >> support. It has  
>> significant bug fixes over 0.4.0, especially with >> respect to  
>> OpenMCL and ACL. Thanks to Andrew Blumberg, Ian Eslick, >> and  
>> Waldo Rubinstein. The tutorial and documentation are improved, >>  
>> but may still lag the source code in some ways. >> >> >> >> ----  
>> >> Robert L. Read, PhD read &T >> robertlread.net >> Consider  
>> visiting Progressive Engineering: http://robertlread.net/pe >> In  
>> Austin: 912-8593 "Think >> globally, Act locally." -- RBF >> >> >>  
>> _______________________________________________ >> elephant-devel  
>> site list >> elephant-devel at common-lisp.net <mailto:elephant- 
>> devel at common-lisp.net> >> http://common-lisp.net/mailman/listinfo/ 
>> elephant-devel > >  
>> --------------------------------------------------------------------- 
>> --- > > _______________________________________________ > elephant- 
>> devel site list >