Your message dated Wed, 18 Mar 2009 15:52:22 +0100 with message-id <20090318145222.GH7697@pc049-u864.lyon.inserm.fr> and subject line Re: Bug#517642: octave3.0: FTBFS: Invalid conversions of function pointers has caused the Debian Bug report #517642, regarding octave3.0: FTBFS: Invalid conversions of function pointers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 517642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517642 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: octave3.0: FTBFS: Invalid conversions of function pointers
- From: Daniel Schepler <schepler@math.berkeley.edu>
- Date: Sat, 28 Feb 2009 22:09:33 -0800
- Message-id: <[🔎] 200902282209.34990.schepler@math.berkeley.edu>
Package: octave3.0 Version: 1:3.0.1-7 Severity: serious When I tried to rebuild octave3.0 against the new suitesparse libraries, I got this in my pbuilder build log (on amd64): ... g++ -c -fPIC -I. -I.. -I../liboctave -I../src -I../libcruft/misc -DHAVE_CONFIG_H -Wall -W -Wshadow -Wold- style-cast -O2 -g 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: 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[3]: *** [pic/CSparse.o] Error 1 make[3]: Leaving directory `/tmp/buildd/octave3.0-3.0.1/liboctave' make[2]: *** [liboctave] Error 2 make[2]: Leaving directory `/tmp/buildd/octave3.0-3.0.1' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/octave3.0-3.0.1' make: *** [make-arch-stamp] Error 2 dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler
--- End Message ---
--- Begin Message ---
- To: Daniel Schepler <schepler@math.berkeley.edu>, 517642-done@bugs.debian.org
- Subject: Re: Bug#517642: octave3.0: FTBFS: Invalid conversions of function pointers
- From: Rafael Laboissiere <rafael@debian.org>
- Date: Wed, 18 Mar 2009 15:52:22 +0100
- Message-id: <20090318145222.GH7697@pc049-u864.lyon.inserm.fr>
- In-reply-to: <[🔎] 20090301083228.GA17377@pc049-u864.lyon.inserm.fr>
- References: <[🔎] 200902282209.34990.schepler@math.berkeley.edu> <[🔎] 20090301083228.GA17377@pc049-u864.lyon.inserm.fr>
* Rafael Laboissiere <rafael@debian.org> [2009-03-01 09:32]: > * Daniel Schepler <schepler@math.berkeley.edu> [2009-02-28 22:09]: > > > When I tried to rebuild octave3.0 against the new suitesparse libraries, I got > > this in my pbuilder build log (on amd64): > > This problem is normal and has already been fixed in experimental, version > 1:3.0.4~rc5-1. We are waiting for the liblapack transition to be sorted out > before uploading to unstable. This will hopefully happen soon. Fixed since long now. I am hereby closing this bug reported. -- Rafael
--- End Message ---