[MacPorts] #41361: octave-devel failed to compile on 10.9

[MacPorts]

#41361: octave-devel failed to compile on 10.9
---------------------------+-------------------------
  Reporter:  azurvii@…     |      Owner:  michaelld@…
      Type:  defect        |     Status:  closed
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.2.1
Resolution:  fixed         |   Keywords:
      Port:  octave-devel  |
---------------------------+-------------------------

Comment (by michaelld@…):

 octave-devel builds all C/C++ code using the configure.compiler setting
 (for a few months now, I think); all fortran code is build using the
 selected variant's compiler. So, at least for -building- octave-devel and
 GraphicsMagick, it seems like so long as the same configure.compiler is
 selected then all should be well (and, it does seem to be the case). That
 said, at least on 10.8 I do find that libGraphicsMagick++.dylib links with
 Apple's libstdc++ while the octave-compiled {{{__magick_read__.oct}}}
 links with MacPorts' libstdc++, which should result in an error during
 runtime.  Interestingly, I can do the following (in 10.8; with "foo.jpg"
 in the octave search path):
 {{{
 % octave
 > foo = imread("foo.jpg");
 > imshow(foo)
 }}}
 and it works. So .... not sure what's going on there since I would expect
 the runtime error.  I think that this issue is complicated; maybe some of
 these people were the ones who rebuilt GraphicsMagick using
 configure.compiler=macports-gcc-4.X and thus just needed to re-rebuild?
 The bottom line for me is that rebuilding GraphicsMagick works, and at the
 end of the day all seems well between octave-devel and GraphicsMagick.

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