I recall there being problems taking base class injection out of
shared-initialize - can initialize-instance manipulate the class precedence
list and direct superclasses at that point in the instance initialization?
It occurs to me that, the easiest way to fix this is by policy; remove the
func
The problem was exposed by loading elephant again without also loading the
backend libraries. I made a few changes so that doesn't happen so easily.
Sounds like you had a better fix. I haven't dug into this code base, nor done
much CL hacking, in almost two years so feeling rusty. :)
I also
Anyone remember why we put this into the elephant.asd file? I think the goal
was to force some action to take place so that all the dynamic libraries were
loaded each time. It was causing the CCL MOP problem discussed earlier. I may
have fixes for the CCL MOP - a few tests still fail which I
I was creating the set-valued slot API as a placeholder for something more
native, but ran out of time to work on the project before really getting it
done right. As you say, the API is awkward.
I think it would be more convenient to use lists as the slot-level API and have
a separate API for
I worked on this project with Clojure, so they may be willing to help diagnose.
I'll be looking into this later this month when I upgrade the running server
and add some features to that old project I mentioned. -Ian
On Sep 9, 2011, at 12:06 PM, Alex Mizrahi wrote:
>> I use CCL for some produ
I use CCL for some production CL applications that use Elephant. Which version
of CCL are you having problems with? I haven't upgraded in awhile - 1.2-1.4
were all good for me.
On Sep 9, 2011, at 3:23 AM, Alex Mizrahi wrote:
> It looks like something weird happens with CCL's CLOS when we loa
For the past 5 years or so I've been the lead developer on Elephant and the BDB
backend. I have been and will be inactive for some time yet. I may make some
updates when I do a bug / upgrade pass on the two legacy commercial websites I
have that are running on weblocks + Elephant.
The BDB bac
I missed the earlier patch from Red somehow. I do follow the Elephant list and
am more than happy to grow the crew of people who can do patching. Alex, I'll
ask to get you perms for Elephant on cl.net. Anyone else interested in pushing
to Elephant directly? The more the merrier.
Thanks,
Ian
Alex,
This may be overkill, but the metaclass system and related support code would
probably benefit from a clean, rethought architecture and possible rewrite of
the indexing + schemas + database evolution code. Features were added
incrementally over the years in response to specific needs and
How can you guarantee that the postgres cache is coherent across machines?
Also, BDB does caching in shared memory regions across multiple processes, so
I'm not sure how much extra benefit you'll get from the Postgres cache.
Sent from my iPhone
On May 7, 2011, at 9:20 AM, Alex Mizrahi wrote:
I definitely recommend the Postgres backend for your application. It will be a
significant amount of tricky work to get BDB replication + distributed
transactions to work cleanly with Elephant. Not worth the time / bug risks I
think. It should be trivial to migrate.
Henrik, with the caching
or two ago about
doing a distributed locking solution for Elephant, but I don't know the status
of it.
Thanks,
Ian
On May 4, 2011, at 11:51 AM, Ian Eslick wrote:
> BDB does not work across multiple machines, its transaction support relies on
> a shared memory region to handle locking
BDB does not work across multiple machines, its transaction support relies on a
shared memory region to handle locking so any shared memory architecture (with
multiple CPUs) works fine but separate machines and a NAS device don't work.
You'll have to use the Postgres store (5x slower, but reaso
FYI - I still run three production sites on Elephant BDB, although I haven't
been tracking Oracle's latest releases... I'll upgrade at least one of them to
the next version you release and do some testing.
Elephant has been in pre-release status for a 1.0 release for almost three
years now, it
Clearly a bug if the instances aren't getting indexed when you add an index!
Should be a simple one to fix.
The older you get, sadly, the easier it is to do long-term forecasting. :)
Ian
On Apr 28, 2011, at 1:51 PM, Vassilis Radis wrote:
> As Ian correctly assumed, I just added the :index t
I agree the semantics of inherited indexing is off. I implemented what worked
for me at the time and was an easy extension to what was already there.
However, the issues around class redefinition, database connection state,
schema synchronization, data loss protection, etc make code changes ar
Hi everyone,
I'm not going to be in a position to do regular development or support for
Elephant for at least the next year. I may be able to make small, critical bug
fixes or apply patches if no one else steps up.
Leslie and Alex are both capable of making changes and improvements and I'm
I assume you added :index and didn't change the slot name? I think the
function you want is recreate-index-using-class
On Apr 28, 2011, at 5:48 AM, Vassilis Radis wrote:
> After creating a lot of objects of a specific class I decided to change a
> slot to be indexed. It did change, no old it
That library primarily contains our clib-based serializer and a few utilities
from the BDB backend. It's possible it's a false dependency or there is still
some code in CLP that depends on the library. The key suspect is the
serializer. It's been a few years since I've looked at CLP so I can'
I've done this successfully in testing and I know people who have done this in
production. Also many modern lisps use OS threads and multi-threaded apps work
fine.
Cheers,
Ian
On Mar 18, 2011, at 10:31 AM, Kevin Raison wrote:
> I am curious about this use case for Berkeley DB; can someone co
Hi Petter,
Any progress since you wrote this? Tracking down these kinds of errors is
nasty - I had to do a bunch of it a few years ago when I was changing the
serialization code and messing around with the serializer's bits and bytes.
I'm afraid I don't have a good idea here. Was your proble
Did you have this problem in 1.4? We use Elephant extensively on Clozure on
Mac/Linux under 1.4 but I haven't upgraded to the latest 1.5 on any system that
I'm aware of. There are some occasional bugs found in the schema management
code too that may be lurking.
Ian
On Sep 23, 2010, at 10:51
Finally getting switched over to cffi would be fantastic; thanks Gustavo! And
thanks Leslie for doing the testing & integration. Yes, we should delete
elephant-unstable now.
Ian
On Aug 11, 2010, at 10:29 PM, Leslie P. Polzer wrote:
>
> Gustavo wrote:
>
>> I've realized that elephant-1.0 is
Probably a global parameter with a more expected default is appropriate.
Multi-store operation is not a commonly supported operating mode, although
we've made provisions for it over time. The current behavior was intended to
solve the following problem.
1) System one opens a store and starts u
Ok, it is missing a function that elephant depends on. I've sent a mail to the
ccl developer list.
Ian
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
(1).
>
> And the tests never run to completion.
>
> -Kevin
>
>
> On 04/12/2010 09:12 PM, Ian Eslick wrote:
>> I can't speak to the specific errors, although I'm just setting up my own
>> x86-32bit Linux installation with ccl and Elephant so will let you k
I'm using the development head of CCL on a 32-bit linux and am running into the
same memory fault. I'll reach out to the devs.
Ian
On Apr 12, 2010, at 11:57 PM, Leslie P. Polzer wrote:
>
> Hey Kevin,
>
> you wrote:
>
>> But using CCL 1.4 or 1.5 on Linux x86 with BDB 4.7 fails tests in
>> st
I can't speak to the specific errors, although I'm just setting up my own
x86-32bit Linux installation with ccl and Elephant so will let you know if I
have problems.
The errors in the tests look like you didn't clear out the test databases
(there's a script in the test folder to do this).
Ia
I can't say I've thought deeply about this, but instance creation is wrapped in
a transaction - so long as the side effects you are concerned about, including
reads the store, they should be atomic due to BDB locking.
On Mar 18, 2010, at 6:37 AM, Alex Mizrahi wrote:
> IE> Should be easy to add
I tend to agree with Alex on this one. Moreover, I'm not going to have time to
make changes for awhile, but I'd be willing to review a patch.
Should be easy to add an index lookup to shared-initialize and a check in
indexed slot access as to whether you are changing the unique value. Can a
I'm not sure if Elephant will play nicely with Berkeley DB 4.8 yet - we should
probably fix this. For now, however, you can ignore the db_deadlock setting in
my-config as it is not strictly required as of 4.7.
Ian
On Mar 5, 2010, at 12:49 AM, Nicolas Neuss wrote:
> Hello,
>
> I would like to
Hi Lukas,
How are you defining 'memory not released'? Is this a measure of the Lisp heap
or the OS footprint?
As I recall, when allocating space in the heap for new objects, SBCL will
periodically ask the OS for more heap memory. Even if the objects are garbage
collected later, the allocated
I don't believe elephant is compatible with CFFI yet, or did I miss an update?
The latest UFFI is probably more appropriate?
On Feb 13, 2010, at 8:02 AM, Leslie P. Polzer wrote:
>
> Andrew Kirkpatrick wrote:
>> Hi, I'm trying to use elephant but with limited success. Running on
>> Ubuntu 9.04,
Sounds like an idempotence problem. Sometimes prior runs of the test leave
data in the test DB that fouls up other tests. Are you running on a clean DB?
You can run tests/delscript.sh to ensure databases are fresh)? Also, which
lisp are you running?
Thanks,
Ian
On Feb 10, 2010, at 3:45 PM,
The Elephant MOP overloads class objects to store a variety of data. The MOP
only guarantees to call finalize-inheritance at the latest when an instance is
created, so if you call get-instances-by-class, the Elephant MOP has to make
sure to call finalize-inheritance.
Sounds like we need to do
> I have an idea: we could have a second elephant database used only for
> reference tracking. It does not have to have the same backend,
> bdb will probably be the best choice at all time. This should be easy
> to implement and avoid the problem completely?
> Make we can make its use an option, af
But not, I believe, in the actual 0.9 release. 0.9.1 may have had it.
On Jan 20, 2010, at 6:35 PM, Alex Mizrahi wrote:
> IE> We introduced recreate-instance in 1.0 which does not call your
> IE> initialize-instance when existing instances are pulled from the DB.
> IE> You are not the first to
le-bdb.asd (previously in
> c:\lisp\libraries\elephant-1.0\elephant.asd).
> NIL
>
>
> (setf *db-spec* '(:BDB #p"c:/temp/testdb/"))
> (ele:open-store *db-spec*)
>
> throws this error:
>
> Error: Berkeley DB error #22: Invalid argument
>
>
I know we have pre-build Elephant DLLs for 4.5 which should work with 1.0. Is
that configuration working for everyone?
What's the current status of LW and BDB 4.7? I only have access to LW 5.1 at
the moment (Personal Edition for 6 is not out yet) so will not be able to help
debug 6.0. It wil
We introduced recreate-instance in 1.0 which does not call your
initialize-instance when existing instances are pulled from the DB. You are
not the first to have this problem. ;) Under the new system, you'll use
initialize-instance which should have the expected behavior now of only acting
a
x27;s a pretty nasty one and my solution does not scale
> well--requires a lot of time when reopening a database to construct
> the indexes.
>
> -Red
>
> On Tue, Dec 29, 2009 at 9:51 PM, Ian Eslick wrote:
>> I'll give it a try with that configuration...
>>
&g
Hi Frank,
Have you tested with BDB? I'm curious if it's a backend issue (the serialized
byte-stream seems to be at fault; it's what's causing the condition to be
asserted which itself fails).
The other sanity check is to confirming no stale fasls and appropriate settings
in my-config.sexp
e t argument to the open-controller
> method. This seems to indicate that the 'BY-NAME secondary indices
> that map a class indices to OIDs, and class names to class indices, do
> not persist. Is this expected behavior? I'm not familiar enough with
> the internals to tell.
get-instances-by-value is a low level primitive, so it operates only on a
single index.
I have a triple-store / ontology hack in my contrib directory. I haven't
looked at it in a couple of years but you may find it useful.
elephant-1.0/src/contrib/eslick/triples.lisp
There is also a qu
I checked in some patches I missed from the list earlier as well as some
changes to cached slot / instance behavior.
Ian
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
Hi Edward,
I'm unable to reproduce with my local version of the latest Elephant (latest,
ccl64, DB 4.7, Mac). Can you give me a transcript like:
(setf btree (make-btree))
(setf (get-value 'foo btree) 10)
(setf (get-value 'bar btree) 20)
(dump-btree btree)
(remove-kv 'foo btree)
(dump-btree btre
Done.
On Dec 16, 2009, at 5:33 AM, Lukas Gießmann wrote:
>
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
Is this what you are looking for?
http://roeim.net/vetle/docs/cl-webapp-intro/part-2/
Sent from my iPhone
On Dec 15, 2009, at 5:40 AM, Arjun Mullick
wrote:
> I am a new user to elephant , and it has been very hard to learn the
> language just by the documentation on your site , can u pleas
Hi Lukas,
I haven't seen that particular darcs problem before, although I have seen the
gcc build via asdf fail but work when done manually. This may be fixed in the
latest head, actually. You might try pulling elephant-1.0 without the --tag
option and see if that fixes it.
Best,
Ian
On Dec
I don't think BDB 4.7 has been tested on windows until now. I'm surprised 4.5
works with the latest head - but it's probably because you aren't exercising
some of the 4.7 features Leslie added.
On Dec 8, 2009, at 1:14 PM, Elliott Slaughter wrote:
> On Tue, Dec 8, 2009
1.0\src\db-bdb\libberkeley-db.c: In function
> `lisp_compare_key2':
> c:\Bin\asdf\elephant-1.0\src\db-bdb\libberkeley-db.c:1155: warning: unused
> variable `i'
> c:\Bin\asdf\elephant-1.0\src\db-bdb\libberkeley-db.c: In function `case_cmp':
> c:\Bin\asdf\elephant-1.0\src\
> receved today)
>
> If there is a chance for help - I would be very happy.
>
> On Mon, Dec 7, 2009 at 7:34 PM, Elliott Slaughter
> wrote:
>> Here are the dlls I built for the newest version of Elephant with BDB
>> 4.7.25. If they work for you, then Ian can put
Elliott said he was going to give this a shot. You might correspond with him
directly. -Ian
On Dec 7, 2009, at 12:09 AM, Plamen . wrote:
> Hello Ian,
>
> thank you for the quick response!
>
> On Sun, Dec 6, 2009 at 5:44 PM, Ian Eslick wrote:
>> Hey, quick answers:
>&g
When without-interrupts was put in Allegro (7.x) didn't have SMP support and it
was a fast way of handling locking for high frequency synchronization
(primarily the serializer). I haven't used Allegro in awhile so didn't revisit
this. I guess that 9.0 is finally going to support SMP! Feel fre
What's your my-config.sexp?
On Dec 6, 2009, at 1:12 PM, Elliott Slaughter wrote:
> Hi,
>
> I'm testing the newest Elephant 1.0 SBCL 1.0.29 on Windows 7 with BDB 4.7. I
> get the following error when attempting to open a controller. (I've used SBCL
> with Elephant 1.0 and BDB 4.5 in the past, s
Hey, quick answers:
1) In the online FAQ you'll notice that you have to ensure that you are using
uffi and not the uffi compatibility package from cffi.
2) The prebuilt DLLs are not up to date (sorry!), they need to be made current
against BDB 4.7 which Elephant 1.0 depends on.
3) We have one or
Shaneal Manek wrote:
> Hi,
>
> I just wanted to quickly let everyone know that I'm using elephant in
> production on my start up (http://postabon.com).
>
> Thanks to everyone here for creating such a great piece of open source
> software. In particular, Ian Eslick and L
I've posted this FAQ documentation online. -Ian
On Nov 19, 2009, at 11:10 AM, Sebastian Tennant wrote:
> Hi Ian,
>
> Sorry for the late reply. I have a rather annoying cold at the
> moment.
>
> Quoth Ian Eslick :
>> I'm ostensibly the primary deve
What were the problems you encountered and solutions you found?
Anything we should add to the FAQ?
Sent from my iPhone
On Nov 21, 2009, at 1:54 PM, Sebastian Tennant
wrote:
> Quoth "Leslie P. Polzer" :
>> Can you send us the backtrace? Also try compiling libmemutil.so
>> manually.
>> Th
No problem! I'll add the FAQ to the site shortly. -Ian
On Nov 19, 2009, at 3:09 PM, Sebastian Tennant wrote:
> Quoth Ian Eslick :
>> The reason I asked for the my-config.sexp is that the my-config you
>> forwarded some time ago below will fail in the way you are talking
Seb,
The reason I asked for the my-config.sexp is that the my-config you
forwarded some time ago below will fail in the way you are talking
about (undefined symbols as well as unrecognized arguments) because
this file is telling it to use BDB 4.5 headers to talk to 4.7
libraries. BDB chan
What's your my-config look like again?
Sent from my iPhone
On Nov 19, 2009, at 11:10 AM, Sebastian Tennant
wrote:
> Hi Ian,
>
> Sorry for the late reply. I have a rather annoying cold at the
> moment.
>
> Quoth Ian Eslick :
>> I'm ostensibly the primar
>> No I think this particular compilation has already been completed
>> at this point.
>> [...]
>> Not sure about that. We need a backtrace, and please show us your
>> bdb-constants.lisp.
>
> I have a third machine (an x86 32-bit Debian VPS) and I've finally got
> elephant-1.0 to work with a patc
Hi All,
To address recent discussions.
I'm ostensibly the primary developer on Elephant; the three prior
primary developers have been inactive for years now. Leslie has
recently been kind enough to step up and help with user support and
bug fixes and will certainly be recognized in the 1.
Did you do a migration/upgrade or just run the old DB under the new
code base? -Ian
On Nov 4, 2009, at 10:58 PM, Aslak Gronflaten wrote:
> Hi,
>
> I'm (still) having problems upgrading an existing berkeley 4.6
> database from
> elephant 0.9 to 1.0 trunk, running sbcl under 32 bit linux.
>
>
Elephant should automatically create and populate a schema when a
class definition is evaluated while the DB is open. I'm surprised it
doesn't do this when a schema is not available. I'll look into this.
Ian
On Nov 5, 2009, at 7:40 PM, Aslak Gronflaten wrote:
> Hi,
>
> I've looked into thi
ssociation slot types may be buggy and/
or cause data loss. Be careful!
On Oct 19, 2009, at 4:20 PM, Alain Picard wrote:
> Ian Eslick writes:
>
>> Association slots were added recently and have not been fully tested.
>> They should be considered in beta.
>>
&g
Derived index slots have been around for quite some time (before 0.5
and 0.6 at least). I'm surprised coverage of them isn't in the
manual. The interface changed a few years ago (they are now defined
in the slot defs and not subject to dynamic addition/removal).
However they were broken
> One last question, while I have your attention: I think I intend
> to have more than 1 process on the machine access the store
> concurrently; but I assume that's no more dangerous than having
> multiple threads doing so; and Berkeley DB should be able to
> take care of itself and protect the int
There was a bug with the get-con function that returns nil after the
restart. I just checked in a fix for that and went ahead and
implemented your suggestion for a saner error + restart model. An
interactive error is asserted which provides a 'reopen-controller
restart. Keep in mind that
My only concern about the variable is adding addition checks to
performance. We have significant overhead going on during slot access
already. One thought would be to make this a compilation option for
high safety settings. I've recorded a Trac ticket for this issue.
Ian
On Oct 2, 2009,
I can say more later, but given controller opening costs, we should
deprecate with-open-store. The usage model I use with multiple stores
is (with-transaction (:store-controller *my-store*)
I open the controller just once. If there is only one store you can
rely on the default controller a
Which darcs repository? There is the old 0.91 release and the new
elephant-1.0 branch...
Ian
On Sep 22, 2009, at 8:41 PM, Red Daly wrote:
I should also note that I am using the version of elephant from
darcs. And I discovered that when the program went down it was due
to a segfault (I b
Try BDB 4.7 - it's required for the current dev head.
run tests/delscript.sh from tests - it will clean out all the tests
databases. It is possible there are some regressions on head which,
if you reproduce your errors after running delscript, I'll try to look
at this week.
Thank you,
Ian
Did you run the clean script before running the tests? I have exactly
that configuration locally and use it daily without incident. Also,
which BDB version are you using? -Ian
On Sep 19, 2009, at 5:09 PM, Derrell Piper wrote:
> Hi,
>
> Configuration:Mac OS X, 10.6.1 (Snow Leopard)
Hi Leslie,
The policies here have been a thorn in the design for some time. The
first version of schema sync provided lots of configuration options
for sync policies, the second tried to provide a clean default policy;
but I have also had this redefine before open sync problem.
The idea is
Sounds like an opportunity for a cute little macro...
(defmacro with-store ((store) &body body)
`(let ((*store-controller* ,store))
(declare (special *store-controller*))
,@body))
which is now in the current dev tree.
There is also the with-open-store macro which will open
There should be an upgrade path through previous versions. If you use
the upgrade procedure in the 0.9 release on an 0.8 database you should
be good then you should then be able to open that 0.9 DB in the
latest. I can't recall if we need another upgrade to go from 0.9 to
1.0, but I don't
I'm sorry for not replying earlier. I noticed a problem with that
when I did an experiment while I was composing a reply to you and I
haven't had a chance to look into it yet. Shamefully, I don't have
good regression coverage of that feature yet, although I know some
folks use it extensiv
Thank you, this looks great. I'll review it and promote it in the
next week or so unless Leslie beats me to it.
Thank you,
Ian
On Aug 7, 2009, at 7:15 PM, Hiroyuki Komatsu wrote:
> This patch does these things;
>
> o Maybe, big endian machines are nothing affected by this
> patch. I do not
I don't have an objection. -Ian
On Jul 22, 2009, at 9:50 AM, Leslie P. Polzer wrote:
>
> How about it?
>
> A beta tested about 90% isn't all that bad, plus this one
> already fixes a bunch of bugs in a2.
>
> Leslie
>
> --
> http://www.linkedin.com/in/polzer
>
>
> __
Daly wrote:
On Tue, Sep 16, 2008 at 7:20 AM, Ian Eslick
wrote:
There is an :inherit slot keyword option for indexed slots. It
causes subclasses of the defining class to share the index of the
base class. You can inhibit subclass sharing by re-defining the
slot in the base class. I
I've also wondered what parts of syncing run inside a
transaction. ASDF compilation prevents async interruptions
at least but of course another thread could be in the middle
of some op when the sync happens.
Leslie
Synchronization in the sense of on-disk instance updates are all
degree-2 tr
I'd like to do a thread-safety pass on the schema evolution code
first. I'll maybe get to it next week. Anyone want to be a second
pair of eyes?
Ian
On Jun 20, 2009, at 9:58 AM, Leslie P. Polzer wrote:
>
> I suggest we release the first beta of 1.0 soon.
>
> Several fixes have made their w
We have been running into these problems off and on. It must be
related to code for the new schema evolution mechanism introduced in
the 1.0 candidate branch. I thought we had fixed these pathways, but
I will endeavor to reproduce this problem.
Thanks,
Ian
On May 7, 2009, at 8:51 AM, Tomo
>> However, for now gp-export does not back up whole store -- it only
>> iterates
>> through all objects
>> it finds in index and dumps them together with all their slots etc.
>> It is
>> such because it was meant
>> to be working with various stores. (But it supports only elephant/
>> postmod
gp-export sounds very useful. I actually implemented something
similar to help convert databases from one lisp to another (string
serialization is not compatible across lisp implementations). This
would be a more general solution to my hack. I'll look at it when I
get a chance.
Cheers,
You can remove/add btree indexes manually. There is a rebuild-slot-
indices function (or something similar) in 1.0
Sent from my iPhone
On Apr 23, 2009, at 2:36 AM, "Leslie P. Polzer" wrote:
>
>> I've been using elephant 0.91 for quite a while now, with a
>> berkeley 4.6
>> backend, and it's
No it's not. Did you clean the test store controllers with ./
delscript.sh?
On Mar 24, 2009, at 11:21 AM, Leslie P. Polzer wrote:
>
> On an x86 GNU/Linux system with SBCL 1.0.25 and BDB 4.7
> I get 15 failing tests (as follows).
>
> Is this supposed to happen in the latest Elephant head?
>
>
>
Hi Marc,
I'm not sure this ever got into the mainline. However i cannot seem
to apply the darcs patch; would you mind regenerating?
Thank you,
Ian
On Aug 13, 2008, at 2:06 AM, Marc wrote:
> Hi!
>> i forgot to attach the patch to the mail - so other users - if they
>> have
>> the same probl
putting a
break in save-proxy-object and save-snapshot-set and inspecting the
values after each step to see what state isn't being recorded that
would stop this recursion.
Ian
On Mar 20, 2009, at 12:56 AM, Elliott Slaughter wrote:
> On Wed, Mar 18, 2009 at 9:18 PM, Ian Eslick
You need to implement register-object for your metaclass, only
standard classes are 'registered' or kept in the ID table.
Ian
On Mar 18, 2009, at 11:31 PM, Elliott Slaughter wrote:
> Hi,
>
> I have been exploring using snapshot-set in my application, and
> noticed a couple of issues.
>
> F
Hi Glenn and Leslie,
Since we're trying to move with some reasonable speed towards a 1.0
release of Elephant, and clbuild fails to work currently inhibiting
adoption, I would appreciate taking this off the shelf and can help
resolve the remaining issues.
Ian
On Nov 4, 2008, at 8:13 AM, Gle
How does one go about updating the cl-build dependency list?
Ian
On Mar 16, 2009, at 9:21 AM, Leslie P. Polzer wrote:
>
>> cl-build doesn't support the current UFFI head? That's what I use.
>
> I think it does, but a fresh clbuild install of Elephant will
> use the UFFI compatiblity layer of CF
cl-build doesn't support the current UFFI head? That's what I use.
Ian
On Mar 16, 2009, at 7:45 AM, Leslie P. Polzer wrote:
>
>> Wow, that is really a quite awful procedure.
>>
>> I've never used cl-build so will do a test run in a clean environment
>> on that and let you know if I'm able to fi
Wow, that is really a quite awful procedure.
I've never used cl-build so will do a test run in a clean environment
on that and let you know if I'm able to fix some of these problems.
Ian
On Mar 16, 2009, at 6:18 AM, mosi wrote:
> Hi Andrea,
> I`m not at my linux machine, but as far as I can r
That is very out of date; if you check the elephant home page we
recommend you use elephant-1.0 (same path)
Sent from my iPhone
On Mar 15, 2009, at 7:10 PM, Richard KLINDA wrote:
>>>>>> Regarding 'Re: another installation problem'; Ian Eslick adds:
>
>
&g
Which elephant repo are you using?
Ian
On Mar 14, 2009, at 7:40 AM, Richard KLINDA wrote:
> Hello, I'm trying to use elephant on Debian with SBCL 1.0.25 and the
> clbuild installation framework.
>
> The installation goes fine, but when I try to do a (elephant:open-
> store
> '(:BDB "/tmp/4/"))
= to 3..
>
>
> That was slime environment.
> In the sbcl prompt, all 500 tests passed OK.
> I`m baffled as to why this might be.
>
> Thank you very much,
> let`s try some exciting stuff with elephant.
> Best regards,
> mosi
>
>
&
A couple of quick points:
- The latest elephant requires BDB 4.7
- The C compilation step can cause problems when run from
within slime, doing an initial compile from the console typically
fixes this.
- Sometimes SBCL complains the compile failed due to package export
or other issues bu
1 - 100 of 753 matches
Mail list logo
