Re: [eigen] buildtests fail with gcc, icc, suncc and mingw (3.0.4/Debian/amd64)

[Anton Gladky <gladky.anton@xxxxxxxxx>]

Hi Nicolas,

I am a Debian maintainer of eigen3.
eigen3-3.0.4 was successfully built on all available platforms [1].
Moreover 3.1.0~alpha is in "experimental" branch [2] and it seems no
problems there as well.

But you should have "unstable" (sid) or "testing"(Wheezy) version of
Debian to have it.

There is a small issue with doc generation (required a patch [3], the
bug will be filed), but buildtests are passing
on all main platforms almost without problems.

[1] https://buildd.debian.org/status/package.php?p=eigen3
[2] https://buildd.debian.org/status/package.php?p=eigen3
[3] http://anonscm.debian.org/gitweb/?p=debian-science/packages/eigen3.git;a=blob;f=debian/patches/fix-doc-generation.patch;h=3c488ca33a4e015e84f098db940118e1056c6f24;hb=HEAD

Anton



On Fri, Dec 16, 2011 at 4:38 PM, Nicolas Limare
<nicolas.limare@xxxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> This is my first message on the list. I am Nicolas, working with some
> image processing codes.
>
> I tried to test Eigen on my machine (Debien 6.0 Squeeze amd64) and it
> failed with all the compilers.
>
> $ mkdir eigen; cd eigen
> $ wget http://bitbucket.org/eigen/eigen/get/3.0.4.tar.bz2
> $ tar xjf 3.0.4.tar.bz2; cd eigen-eigen-13a11181fc5a
> $ mkdir build; cd build
>
> $ cmake ../; make buildtests
>
> # default compiler, GNU g++ 4.4.5
> # -> the compiler throws some warnings about GOTO and ASSIGN
> #    then the compilation fails on alink problem
> # -> log attached as gcc.log
>
> $ rm -rf *
> $ CXX=icc cmake ../; make buildtests
>
> # try with Intel icc 12.0.4
> # -> the compiler throws the same warnings and link fails at the same point
> # -> log attached as icc.log
>
> $ rm -rf *
> $ CXX=sunCC cmake ../; make buildtests
>
> # try with Sun/Oracle sunCC 5.11
> # -> the compiler prints some C++ error messages and stops
> # -> log attached as suncc.log
>
> $ rm -rf *
> $ CXX=i586-mingw32msvc-g++ cmake ../; make buildtests
>
> # for the fun...
> # try a cross-compilation with GNU/MinGW i586-mingw32msvc-g++ 4.4.4
> # -> the compiler prints some (other) C++ error messages and stops
> # -> log attached as mingw.log
>
> Are these known bugs. Are the build tests known to sometimes fail?
>
> As far as I can remember I did not touch the gcc packages on my
> system, so there should be no configuration error. Did someone succeed
> in testing Eigen on Debian Squeeze with gcc?
>
> I may have botched something when installing icc and suncc, so I am
> not 100% sure that the problem with these compilers is not on my
> side. Did anyone try to test Eigen with icc or suncc? Dit it work?
>
> The Eigen web says "Eigen is standard C++98 and so should
> theoretically be compatible with any compliant compiler. Whenever we
> use some non-standard feature, that is optional and can be
> disabled." How do I disable everything non-standard (grep standard
> doc/* didn't help). Shouldn't every non-standard code be disabled by
> default, and only enabled when the compiler is known to support them?
>
> PS: It is the first time I touch Eigen. I may have handled it
> upside-down without noticing.
>
> --
> Nicolas LIMARE - CMLA - ENS Cachan    http://www.cmla.ens-cachan.fr/~limare/
> IPOL - image processing on line                          http://www.ipol.im/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAk7rZgAACgkQvviFAPpCP09n4QCfbhLlfADSTjhsD9EZ/KfVaP9/
> VYUAnjEKOBC2LURbKZ1DS7vVR/NNmCKh
> =95V1
> -----END PGP SIGNATURE-----
>