can you nm the object which is generated by above shown code, to see that the signature is indeed what you expect.
Vardhan Varma
2009-03-12 15:59:32
+1
A:
In all honesty there's so many things generated by nm I'm currently very confused. The function is present in libmiindsparseimplementation.so though, which is correct afaik?
Ed Woodcock
2009-03-12 16:07:22
use nm -A -C | grep T
Vardhan Varma
2009-03-12 16:56:54
It may be a .lib order issue as someone else noted.just give all your libraries twice (-:or do the painful lorder+tsort magic.
Vardhan Varma
2009-03-12 16:59:13
Ok, using nm I seem to not have the exact function it asked for, I'll update the question.
Ed Woodcock
2009-03-12 17:05:50
A:
Trying to parse (reformat) that line so I can read it...
libmiinddynamic.so: undefined reference to:
ostream & SparseImplementationLib::operator<<
< double, double, SparseImplementationLib::DefaultPtr<double, double> >
(
ostream &,
SparseImplementationLib::AbstractSparseNode<
double, double, SparseImplementationLib::DefaultPtr<double, double> > const
)
If I read that right, then:
- class ActivityType is a double.
- class WeightType is a double.
- *class ptr_type* is a SparseImplementationLib::DefaultPtr<double, double>
And somehow the second argument
const AbstractSparseNode<ActivityType,WeightType>&,
e.g const AbstractSparseNode<double,double>&
has become a:
SparseImplementationLib::AbstractSparseNode<
double,
double,
SparseImplementationLib::DefaultPtr<double, double>
> const &
The template argument counts don't match up. You've defined the second (templated) argument with 2 templated parameters and your error message indicates 3 templated parameters.
Mr.Ree
2009-03-12 16:46:28
Oh, sorry. The AbstractSparseNode has a third defaulted template argument. (It defaults to . . . DefaultPtr<ActivityType,WeightType> =)
Ed Woodcock
2009-03-12 16:49:15