Re: Octave-3.0.2 make problem.

[Jordi Gutiérrez Hermoso]

2008/10/6 Oka Kurniawan <address@hidden>:
>>When I compile Octave-3.0.2 on Zenwalk Snapshot which has SuiteSparse-3.2,
>>make continues for some time and then stops with the error message given
>>below:
>
>>CSparse.cc: In member function 'ComplexMatrix
>>SparseComplexMatrix::fsolve(MatrixType&, const Matrix&, octave_idx_type&,
>>double&, void (*)(double), bool) const':
>>CSparse.cc:5769: error: 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: error: 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: error: 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: error: invalid conversion from 'void (*)(int, char*, int,
>>char*)' to 'void (*)(int, const char*, int, const char*)'
>>make[2]: *** [pic/CSparse.o] Error 1
>>make[2]: Leaving directory `/root/octave/octave-3.0.2/liboctave'
>>make[1]: *** [liboctave] Error 2
>>make[1]: Leaving directory `/root/octave/octave-3.0.2'
>>make: *** [all] Error 2
>
>>What is the solution? This problem was not there when I compiled with
>>SuiteSparse-3.1.
>
> I also have this problem. I tried with octave 3.0.2 and 3.0.3
>
> anyone have idea to solve this?

The fix was really easy. I wish I had gotten around to doing it, but
Jaroslav Hajek beat me to it. ;-)

This issue should now be fixed in Octave 3.0.3

HTH,
- Jordi G. H.