dheldt wrote:
hi there,
our current tip in the repo does not compile due to the latest patch (Error code compatibility with CoCoALib 0.9915).
You could even say it more drastically: None of our repositories / downloadable sources compile right out of the box.
ApCoCoALib-0.99.05:
Code:
make[4]: Entering directory `/home/karsten/CompileTest/ApCoCoALib-0.99/src/algebraic'
Compiling RegisterServerOpsDoAlg.o
In file included from ../../include/CoCoADortmund/library.H:8,
from RegisterServerOpsDoAlg.C:19:
../../include/CoCoADortmund/NumBLASLapack.H:37:35: error: Accelerate/Accelerate.h: No such file or directory
make[4]: *** [RegisterServerOpsDoAlg.o] Error 1
ApCoCoALib-0.99.07:
Code:
make[4]: Entering directory `/home/karsten/CompileTest2/ApCoCoALib-0.99/src/server'
g++: /home/karsten/numerical-linux-x86//lapack-3.1.0-linux-x86//lapack_LINUX.a: No such file or directory
g++: /home/karsten/numerical-linux-x86//clapack-3.0.0-linux-x86//libI77.a: No such file or directory
g++: /home/karsten/numerical-linux-x86//clapack-3.0.0-linux-x86//libF77.a: No such file or directory
g++: /home/karsten/numerical-linux-x86//Linux_PIIISSE1/lib//libf77blas.a: No such file or directory
g++: /home/karsten/numerical-linux-x86//Linux_PIIISSE1/lib//libatlas.a: No such file or directory
make[4]: *** [CoCoAServer] Error 1
Both of these are because of default compiler flags which assume/require things like the Accelerate framework and numerical libraries which have to get disabled explicitly. As Stefan already wrote, we already looked which CoCoALib version one needs for the code in the repositories. A ./configure there fails by default, too, unless you edit the configure script beforehand, just like a simple make fails above unless you edit the autoconf.mk prior to compilation.
We could either delete those old snapshots from our download page, or otherwise I'd strongly advise to change them so that they compile through without fiddling around at all (who wants/needs to do that is free to do it). In that case there will be download links for the appropriate CoCoALib version accompanying them, too.
Concerning the repositories:
Since the only old downloads that we offer are ApCoCoALib 0.99.05 (compiles against the CoCoALib with the same version, if one fixes the errors above) and ApCoCoALib 0.99.07 (same) I don't really see the need to keep a CoCoALib-0.99.06 repo. The CoCoALib 0.99.12 doesn't compile against any of our ApCoCoALibs as we found out, but maybe we should keep it for diffs against the MSVC version. Our ApCoCoALib 1.00.01 compiles against the CoCoALib 0.99.14, so I'd add download links that one, and I'm preparing a mercurial repository from the CoCoALib CVS which corresponds to the CoCoALib 0.9915 release, because our devel tree compiles against that one.