make check gets bug in lifting-container.h

[David Saunders]

g++4 -m64 -DHAVE_CONFIG_H -I. -I.. -I.. -I../linbox
-D__LINBOX_HAVE_CBLAS -I/usr/local/algebra/gmp/include
-I/usr/local/algebra/givaro/include -g -DLinBoxSrcOnly -Wall -c -o
test-butterfly.o test-butterfly.C
In file included from ../linbox/blackbox/apply.h:23,
from ../linbox/algorithms/det-rational.h:39,
from ../linbox/solutions/det.h:581,
from test-butterfly.C:29:
../linbox/algorithms/lifting-container.h:313: error: ISO C++ forbids
declaration of 'MatrixApplyDomain' with no type
../linbox/algorithms/lifting-container.h:313: error: expected ';' before
'<' token
../linbox/algorithms/lifting-container.h: In constructor
'LinBox::LiftingContainerBase<_Ring,
_IMatrix>::LiftingContainerBase(const _Ring&, const _IMatrix&, const
Vector1&, const Prime_Type&)':
../linbox/algorithms/lifting-container.h:336: error: class
'LinBox::LiftingContainerBase<_Ring, _IMatrix>' does not have any field
named '_MAD'
../linbox/algorithms/lifting-container.h:391: error: '_MAD' was not
declared in this scope
../linbox/algorithms/lifting-container.h: At global scope:
../linbox/algorithms/lifting-container.h:582: error: ISO C++ forbids
declaration of 'BlasApply' with no type
../linbox/algorithms/lifting-container.h:582: error: expected ';' before
'<' token
../linbox/algorithms/lifting-container.h: In constructor
'LinBox::DixonLiftingContainer<_Ring, _Field, _IMatrix,
_FMatrix>::DixonLiftingContainer(const _Ring&, const _Field&, const
_IMatrix&, const _FMatrix&, const VectorIn&, const Prime_Type&)':
../linbox/algorithms/lifting-container.h:597: error: class
'LinBox::DixonLiftingContainer<_Ring, _Field, _IMatrix, _FMatrix>' does
not have any field named '_BA'

[Pascal Giorgi]

Hi Dave,

I do not have such an error on my machine, everything seems to be ok
with lifting-container.
Do you same trouble with test-rational-solve which is also using the
lifting container ?

A last though would be to remove "blackbox/apply.h" inclusion in file
"algorithms/det-rational.h" since it
does not need it, but I have no clue that would cause your error.