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 14, 2009, at 6:49 AM, Lukas Gießmann wrote:

> Hi,
> 
> I am wondering about my installation of elephant 1.0.
> 
> I just tried to install elephant 1.0 directly from the darcs repository by 
> the command "darcs 
> gethttp://www.common-lisp.net/project/elephant/darcs/elephant-1.0"; and/or 
> "darcs get 
> --tag=ELEPHANT-1-0-A2http://www.common-lisp.net/project/elephant/darcs/elephant-1.0";.
>  When the repository was downloaded on the system, darcs displayed the 
> message "Warning: CRC errors found. These are probably harmless but should be 
> repaired.
> See 'darcs gzcrcs --help' for more information."
> The commands "darcs gzcrcs --check" and "darcs gzcrcs --repair" had no 
> effects.
> 
> When I was loading elephant on sbcl with slime, it stopped to work at the 
> command "gcc -L/usr/local/BerkeleyDB.4.5/lib/ 
> -I/usr/local/BerkeleyDB.4.5/include/ -shared -march=x86-64 -fPIC -Wall -g -O2 
> -g /home/lukas/.sbcl/site/elephant-1.0/src/db-bdb/libberkeley-db.c -o 
> /var/cache/common-lisp-controller/1000/sbcl/local/home/lukas/.sbcl/site/elephant-1.0/src/db-bdb/libberkeley-db.so
>  -lm".
> 
> My work-around was to execute the last command in the shell and to recompile 
> elephant in slime/sbcl.
> I am not sure if this is a bug or if I did something wrong?
> Maybe there is someone with the same problem?
> 
> 
> Best regards
> 
> Lukas
> 
> Alle E-Mail-Adressen online auf einen Blick Ich will 
> Hotmail!_______________________________________________
> elephant-devel site list
> elephant-devel@common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel

_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

Reply via email to