Re: compilation pb around CSparse

[Jaroslav Hajek]

On Fri, Nov 21, 2008 at 1:35 PM, Pinçon Bruno
<address@hidden> wrote:
>
> Hello octave help list,
>
> I met a problem in the octave-3.0.3 compilation. I have compiled the last
> SuiteSpare (3.2.0) and then I try to compile octave. The configure step
> seems OK, all sparse stuff seems to be detected, I got this :
>
> UMFPACK libraries: -lumfpack
> AMD libraries: -lamd
> CAMD libraries: -lcamd
> COLAMD libraries: -lcolamd
> CCOLAMD libraries: -lccolamd
> CHOLMOD libraries: -lcholmod
> CXSPARSE libraries: -lcxsparse
>
> But at compile time I got:
>
>
> g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc
> -DHAVE_CONFIG_H -mieee-fp -Wall -W -Wshadow -Wold-style-cast -O2
> CSparse.cc -o pic/CSparse.o
> CSparse.cc: In member function 'ComplexMatrix
> SparseComplexMatrix::fsolve(MatrixType&, const Matrix&,
> octave_idx_type&, double&, void(*)(double), bool) const':
> CSparse.cc:5769: erreur: invalid conversion from 'void (*)(int, char*,
> int, char*)' to 'void (*)(int, const char*, int, const char*)'
> CSparse.cc: In member function 'SparseComplexMatrix
> SparseComplexMatrix::fsolve(MatrixType&, const SparseMatrix&,
> octave_idx_type&, double&, void (*)(double), bool) const':
> CSparse.cc:6012: erreur: invalid conversion from 'void (*)(int, char*,
> int, char*)' to 'void (*)(int, const char*, int, const char*)'
> CSparse.cc: In member function 'ComplexMatrix
> SparseComplexMatrix::fsolve(MatrixType&, const ComplexMatrix&,
> octave_idx_type&, double&, void (*)(double), bool) const':
> CSparse.cc:6303: erreur: invalid conversion from 'void (*)(int, char*,
> int, char*)' to 'void (*)(int, const char*, int, const char*)'
> CSparse.cc: In member function 'SparseComplexMatrix
> SparseComplexMatrix::fsolve(MatrixType&, const SparseComplexMatrix&,
> octave_idx_type&, double&, void (*)(double), bool) const':
> CSparse.cc:6525: erreur: invalid conversion from 'void (*)(int, char*,
> int, char*)' to 'void (*)(int, con
>
>
> Which don't seems to rely on a pb with SuiteSparse but merely an
> internal octave pb with slightly
> different definition/declaration ?
>
> Thanks for any hint.
>

This problem was triggered by a change of API between SuiteSparse 3.1
and 3.2. It's already fixed in both development and 3.0.x tree, see:
http://hg.tw-math.de/release-3-0-x/rev/712d9e045b1e

regards

-- 
RNDr. Jaroslav Hajek
computing expert
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz