[elephant-devel] Testing unstable

Just checked out unstable with Postmodern with a clean db: [successful tests] X...ffSynchronizing IDX-EIGHT in (POSTMODERN (POSTGRESQL 127.0.0.1 elepm2 postgres PORT 5433)) WARNING: Error while executing prepared sta

[elephant-devel] Testing Henrik's latest patches....

I've tested Henrik's latest patches to the postmodern back-end. They are green on my 64-bit linux system. Unfortunately, I am not sure that this version is compatible with the previous (not officially released version.) Perhaps foolishly, I went ahead and deployed the previous version to my liv

[elephant-devel] Testing OpenMCL 1.1 (64-bit)

Anyone interested in running some tests on OpenMCL 1.1? (Or at least helping me configure my Intel Mac to do it)? FYI - Lispworks passes all tests under Mac OS now. Frank, do you want to test the latest on Windows? Let me know if there are problems and I can debug on this end. I promote

Re: [elephant-devel] Testing

should mean that not every lisp-on-windows-user has MSVC installed (and is able to use it. cygwin is easy to install). Best regards, Frank -Ursprüngliche Nachricht- Von: Elephant bugs and development Gesendet: 19.02.07 21:26:09 An: Elephant bugs and development Betreff: Re: [elephant-devel

Re: [elephant-devel] Testing

(and is able to use it. cygwin is easy to install). Best regards, Frank > -Ursprüngliche Nachricht- > Von: Elephant bugs and development > Gesendet: 19.02.07 21:26:09 > An: Elephant bugs and development > Betreff: Re: [elephant-devel] Testing > Thanks for trying that.

Re: [elephant-devel] Testing

Thanks for trying that. Do you know if there's a way with the cygwin gcc compiler to use a .def file instead of generating a .o with the exports? I'm pretty sure MSVC has one. We'll also need a set of build commands for MSVC... I suspect we may have broken the build of libmemutil when we

Re: [elephant-devel] Testing

gcc -shared -mno-cygwin -mwindows -std=c99 --export-all-symbols libberkeley-db.def libberkeley-db.c -o libberkeley-db.dll produces cc1: error: unrecognized command line option "-fexport-all-symbols" Further: gcc -mno-cygwin -mwindows -c -Wall -std=c99 -L/c/Programme/Oracle/Berkeley\ DB\ 4.5.

Re: [elephant-devel] Testing

Does this work for generating the DLL for libberkeley-db.c? gcc -shared -mno-cygwin -mwindows -std=c99 --export-all-symbols libberkeley-db.def libberkeley-db.c -o libberkeley-db.dll I can include the memutils .def file so this single command is easy to invoke from asdf instead of via a shel

Re: [elephant-devel] Testing

Thanks to everyone who is doing testing. We'll take the feedback from these runs and clean things up a bit before asking for another round of testing. I think we'll accelerate the 0.6.1 release so there is a definite target to test for. The remaining features: Serializer efficiency impro

[elephant-devel] Testing

I tried the new elephant on winXP. 1. Allegro8 trial: Error: In :IMPORT list, the symbol "ARRAY-TYPE-FROM-BYTE" not found in package # [condition type: PACKAGE-ERROR] when loading c:\lisp\binaries\allegro-a8.0-mswindows-x86\lisp\libraries\elephant\src\elephant\serializer1.fasl 2. LispWorks

Re: [elephant-devel] Testing

Scribit Ian Eslick dies 22/01/2007 hora 18:37: > - Most changes I just made are subsumed by testing the existing > regressions on different platforms, such as running the regression on > 64-bit machines with a 64-bit lisp. I'll run the tests under Debian Etch on an amd64. The same box is running i

[elephant-devel] Testing

Test coverage issues: - Most changes I just made are subsumed by testing the existing regressions on different platforms, such as running the regression on 64-bit machines with a 64-bit lisp. - An 0.6.0 DB to 0.6.1 DB migration test (to be added) will validate the new multiple-serializer