From: Hatger, Carsten (Carsten.Hatger_at_[hidden])
Date: 2006-07-04 03:29:30
hi all,
I'm not quite sure whether this is the right place where to put my question, lets give it a try.
I think there is a macro (re-)definition bug in the ublas bindings concerning clapack, lapack & atlas.
Consider a class that uses both clapack and lapack routines. If matrices storage layout is mixed (which ist a must, then), either row-based for proper use with clapack&atlas or column-based for use with lapack and both headerfiles
#include <boost/numeric/bindings/atlas/clapack.hpp>
#include <boost/numeric/bindings/lapack/lapack.hpp>
are included within one msvc7.1 project the macro BOOST_NUMERIC_BINDINGS_FORTRAN defaults to true and subsequent checks for routines using row-major will fail with boost::STATIC_ASSERTION_FAILURE.
However, if the macro BOOST_NUMERIC_BINDINGS_NO_STRUCTURE_CHECK is defined globally compilation completes sucessfully and resulting code seems to work as expected.
Is this by design, my fault (I hope so) or a bug?
best regards,
carsten
--
name: carsten hatger
location: appelstraße 9a
30167 hannover
germany
phone: ++49 511 762 3726
fax: ++49 511 762 2780
mail: mailto:carsten.hatger_at_[hidden]
web: http://www.ikg.uni-hannover.de