Hi all,
I have a project can pass compiling and run very well on ubuntu. I am trying to 
port it to OS X 10.9.
But I ran into a compiling problem.

I asked my compiling problem at this thread.
http://fenicsproject.org/qa/5383/undefined-symbols-dolfin-error-during-link-on-os-x-10-9
I got an answer from johannr<http://fenicsproject.org/qa/user/johannr>. He 
recommended me to use fenics 1.4.0 to compile it.
I tried to use 1.4.0 to compile my project, but there are a lot of errors like 
these below during compiling.
When I used 1.3.0 to compile my project, I didn't run into any compiling error 
except link errors.

Can someone help tell me how to resolve this problem?
Thank you very much.

Compiling errors,
/Applications/FEniCS.app/Contents/Resources/include/dolfin/fem/DofMap.h:66:5: 
note:   no known conversion for argument 1 from 
'boost::shared_ptr<ufc::dofmap>' to 'std::shared_ptr<const ufc::dofmap>'
In file included from ../MultiDimCancerSimu/src/pde/react_diff.h:9:0,
                 from 
../MultiDimCancerSimu/src/env/src/../include/reactiondiffwrapper.h:5,
                 from 
../MultiDimCancerSimu/src/env/src/reactiondiffwrapper.cpp:4:
../MultiDimCancerSimu/src/pde/ReactionDiffusion.h: In constructor 
'ReactionDiffusion::CoefficientSpace_diff::CoefficientSpace_diff(const 
dolfin::Mesh&, const dolfin::SubDomain&)':
../MultiDimCancerSimu/src/pde/ReactionDiffusion.h:2200:180: error: no matching 
function for call to 
'dolfin::FiniteElement::FiniteElement(boost::shared_ptr<ufc::finite_element>)'
                           boost::shared_ptr<const dolfin::FiniteElement>(new 
dolfin::FiniteElement(boost::shared_ptr<ufc::finite_element>(new 
reactiondiffusion_finite_element_0()))),

/Applications/FEniCS.app/Contents/Resources/include/dolfin/fem/FiniteElement.h:35:9:
 note:   no known conversion for argument 1 from 
'boost::shared_ptr<ufc::finite_element>' to 'const dolfin::FiniteElement&'
In file included from ../MultiDimCancerSimu/src/pde/react_diff.h:9:0,
                 from 
../MultiDimCancerSimu/src/env/src/../include/reactiondiffwrapper.h:5,
                 from 
../MultiDimCancerSimu/src/env/src/reactiondiffwrapper.cpp:4:
../MultiDimCancerSimu/src/pde/ReactionDiffusion.h:2412:157: error: no matching 
function for call to 'dolfin::DofMap::DofMap(boost::shared_ptr<ufc::dofmap>, 
const dolfin::Mesh&)'
                           boost::shared_ptr<const dolfin::DofMap>(new 
dolfin::DofMap(boost::shared_ptr<ufc::dofmap>(new 
reactiondiffusion_dofmap_1()), *mesh)))                                         
                                                                                
                                                                                
                                            ^

../MultiDimCancerSimu/src/pde/ReactionDiffusion.h: In member function 'virtual 
ufc::cell_integral* reactiondiffusion_form_1::create_default_cell_integral() 
const':
../MultiDimCancerSimu/src/pde/ReactionDiffusion.h:2128:60: error: invalid 
new-expression of abstract class type 
'reactiondiffusion_cell_integral_1_otherwise'
     return new reactiondiffusion_cell_integral_1_otherwise();
                                                            ^


Thanks,<http://fenicsproject.org/qa/user/johannr>
Xiaohui

Houston Methodist. Leading Medicine. Houston Methodist is ranked by U.S.News & 
World Report as one of America's "Best Hospitals" in 11 specialties and 
designated as a Magnet hospital for excellence in nursing.  Houston Methodist 
has also been named to FORTUNEĀ®  Magazine's "100 Best Companies to Work ForĀ®" 
list for nine years in a row. Visit us at  houstonmethodist.org. Follow us at  
twitter.com/MethodistHosp and facebook.com/HoustonMethodist.  
***CONFIDENTIALITY NOTICE*** This e-mail is the property of Houston Methodist 
and/or its relevant affiliates and may contain restricted and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited. If you are not the 
intended recipient (or authorized to receive for the recipient), please contact 
the sender and delete all copies of the message. Thank you.
_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to