[MacPorts] #40806: octave-devel:

[MacPorts]

#40806: octave-devel:
---------------------------+-------------------------
  Reporter:  ram@…         |      Owner:  michaelld@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.2.0
Resolution:                |   Keywords:  mavericks
      Port:  octave-devel  |
---------------------------+-------------------------

Comment (by michaelld@…):

 The entry
 {{{
 __ZN6Magick9CoderInfoC1ERKNSt3__112basic_stringIcNS1_11char_traitsIcEENS1_9allocatorIcEEEE
 }}}
 is what we're looking for, but it seems incorrect. It demangles to (for
 me, running 10.8):
 {{{
 Magick::CoderInfo::CoderInfo(std::__1::basic_string<char,
 std::__1::char_traits<char>, std::__1::allocator<char> > const&)
 }}}
 with the extra "!__1::" (without the "!") compared with the error you got.
 So, either Octave or GraphicsMagick is messing with std::string.  Looking
 at the code for GraphicsMagick++
 (GraphicsMagick-1.3.18/Magick++/lib/CoderInfo.cpp:37) reads
 {{{
 Magick::CoderInfo::CoderInfo ( const std::string &name_ )
 }}}
 so, I'd guess that it is your install of GraphicsMagick that is the
 culprit here, not Octave.

 One way to test this is to create a simple program which uses std::string,
 compile and link it, then do an "nm -a" on the resulting binary and see
 which mangled C++ expression comes up (using std::basic_string or
 std::!__1::basic_string).

-- 
Ticket URL: <https://trac.macports.org/ticket/40806#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X