Created attachment 697 [details]
The output of compilation is stored in attachment.
Details about my gcc:
$ gcc -v
Using built-in specs.
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-126.96.36.199/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC)
> error: SuiteSparse_long was not declared in this scope
This looks like a compatibility problem with your SuiteSparse. Can you tell what version of libsuitesparse-dev you have installed?
I have found some traces in /usr/share/doc/ that there is installed SuiteSparse devel 3.4.0.
I guess we need at least version 4.x at the moment. We should enhance the FindCholmod.cmake/FindSPQR.cmake for that. It seems that the SuiteSparse_config.h header in the corresponding directory contains a usable version number. Alternatively, we could make a test_compile to determine if the version is ok.
If someone wants to provide a patch, have a look at the other Find*.cmake files.
-- GitLab Migration Automatic Message --
This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1202.