Your message dated Sun, 16 Feb 2014 22:13:23 +1100 with message-id <20140216111323.ga28...@master.debian.org> and subject line Re: linbox: FTBFS on s390: overloaded 'BlasMatrix(T&, size_t&, size_t&)' is ambiguous has caused the Debian Bug report #723172, regarding linbox: FTBFS on s390: overloaded 'BlasMatrix(T&, size_t&, size_t&)' is ambiguous 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 ow...@bugs.debian.org immediately.) -- 723172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: linbox Version: 1.3.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The s390 build of linbox failed with errors of the form linbox-sage.C:458:36: error: call of overloaded 'BlasMatrix(IntegerRing&, size_t&, size_t&)' is ambiguous linbox-sage.C:458:36: note: candidates are: ../../linbox/matrix/blas-matrix.inl:312:2: note: LinBox::BlasMatrix<_Field>::BlasMatrix(const _Field&, const Integer&, const T&) [with T = long unsigned int, _Field = LinBox::PID_integer, LinBox::Integer = Givaro::Integer] ../../linbox/matrix/blas-matrix.inl:300:2: note: LinBox::BlasMatrix<_Field>::BlasMatrix(const _Field&, const int32_t&, const T&) [with T = long unsigned int, _Field = LinBox::PID_integer, int32_t = int] ../../linbox/matrix/blas-matrix.inl:236:2: note: LinBox::BlasMatrix<_Field>::BlasMatrix(const _Field&, const uint32_t&, const T&) [with T = long unsigned int, _Field = LinBox::PID_integer, uint32_t = unsigned int] ../../linbox/matrix/blas-matrix.inl:245:2: note: LinBox::BlasMatrix<_Field>::BlasMatrix(const _Field&, const int64_t&, const T&) [with T = long unsigned int, _Field = LinBox::PID_integer, int64_t = long long int] ../../linbox/matrix/blas-matrix.inl:287:2: note: LinBox::BlasMatrix<_Field>::BlasMatrix(const _Field&, const uint64_t&, const T&) [with T = long unsigned int, _Field = LinBox::PID_integer, uint64_t = long long unsigned int] because size_t is unsigned long whereas uint32_t is unsigned int, and as such formally distinct even though both are 32-bit unsigned types. To avoid such errors, I would recommend covering long and unsigned long when they formally underly neither (u)int32_t nor (u)int64_t. I've had success with the equivalent of #if SIZEOF_LONG == 4 || defined(__APPLE__) because (u)int32_t is normally (unsigned) int these days, and (u)int64_t is (unsigned) long on 64-bit architectures other than Mac OS X, on which it's always (unsigned) long long. (That special case is of course mainly of concern upstream.) At any rate, could you please take a look? Thanks!
--- End Message ---
--- Begin Message ---Version: 1.3.2-1 On Mon, Sep 16, 2013 at 10:29:31PM -0400, Aaron M. Ucko wrote: > Source: linbox > Version: 1.3.2-1 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > The s390 build of linbox failed with errors of the form It built successfully on s390, see: https://buildd.debian.org/status/fetch.php?pkg=linbox&arch=s390x&ver=1.3.2-1&stamp=1379358157
--- End Message ---
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
