#33857: InsightToolkit: error: use of undeclared identifier 'equal' -----------------------------+---------------------- Reporter: junsungp@… | Owner: dweber@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: | Keywords: Port: InsightToolkit | -----------------------------+---------------------- Comment (by jalmar@…): I'm experiencing the same problem with MacPorts version 2.1.3 on Mac OS x 10.8.3 when I try to install the InsightToolkit using the command {{{ sudo port install insighttoolkit -doc -python25 +shared }}} The probleem seemed to be related to the fact Clang rejects a certain kind of construction detailed on the following webpage http://clang.llvm.org/compatibility.html#dep_lookup_bases What the webpage tells you is that the statement {{{ return equal( this->data_block(), rhs.data_block() ); }}} on line 657 of the file InsightToolkit-3.16/Utilities/vxl/core/vnl/vnl_matrix_fixed_ref.h is not a legal construction and should be changed to {{{ return this->equal( this->data_block(), rhs.data_block() ); }}} Notice the 'this->' in front of the the call to equal; from what I understand this is essential to refer base class of the derived class. There are a few more places where you have to change this illegal construction. The same problem exists in the file InsightToolkit-3.16/Code/Common/itkParametricPath.txx On line 46 and line 67 (twice! [2x]) you have to change the calls to 'Evaluate(...)' into 'this->Evaluate(...)' There is another bug as well in the file InsightToolkit-3.16/Code/Common/itkKLMSegmentationBorder.h On line 84, 88, 103, 104, and 109 you have to change the statements with 'rhs.m_Pointer...' into 'rhs->m_Pointer...' (Notice that the dot changes into the arrow) After that, I could build and install the InsightToolkit using the command {{{ sudo port install insighttoolkit -doc -python25 +shared }}} without any further problems. Note sure if this helps any of you. Sorry, I don't know how to create patches, so you'll have to modify the source code yourself. Or maybe someone else can verify these fixes and patch the files for you. I believe they already fixed these particular problems in release 3.20 (see webpage https://itk.icts.uiowa.edu/fisheye/changelog/ITK?cs=68d1a8a60bd919e709e568c9...) -- Ticket URL: <https://trac.macports.org/ticket/33857#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X