On Tue, Sep 16, 2008 at 3:45 AM, Franz Rammerstorfer <[EMAIL PROTECTED]> wrote: > Following error occurs: > > src/solvers/exact_solution.C: In member function 'void > ExactSolution::_compute_error(const std::string&, const std::string&, > std::__debug::vector<std::complex<double>, > std::allocator<std::complex<double> > >&)': > src/solvers/exact_solution.C:512: error: no match for 'operator<' in > '((std::__debug::vector<std::complex<double>, > std::allocator<std::complex<double> > > >*)error_vals)->std::__debug::vector<_Tp, _Allocator>::operator[] [with > _Tp = std::complex<double>, _Allocator =
> > What's happening ? Looks like we haven't compiled recently with complex variable support enabled. This happens from time to time since none of the main developers use this part of the code much. The latest changes ExactSolution attempt to compare a "Number" (in your case a complex number) to a Real using operator<. This isn't defined. I'm not sure why error_vals should need to be a Number though, as far as I can remember they are all going to be real numbers. Anyone else want to comment? -- John ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
