#41238: Octave parcellfun panics ---------------------------+------------------------- Reporter: tom_olin@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: octave-devel | ---------------------------+------------------------- Comment (by michaelld@…): Oh; I think I know the issue. I changed octave-devel recently to decouple the c/c++ and fortran compilers. Building octave-devel requires linking using the fortran compiler, which uses that compiler's libstdc++ runtime, which is provided by libgcc. Packages are build using the c/c++ compiler, which will in general be different than the fortran compiler (suite), and use a different c++ runtime. In my case, I have clang as the c/c++ compiler, and gfortran-mp-4.8 as the fortran compiler (via +gcc48). Clang uses /usr/lib/libstdc++ in 10.8 and earlier, while gfortran-mp-4.8 uses /opt/local/lib/libgcc/libstdc++.6.dylib. You can't have both c++ runtimes at the same time. So, I need to fix mkoctfile to use the fortran compiler; or, something like that. YA reason MacPorts needs a single c++ runtime, as will be the case for 10.9 (or, I'm pretty sure that's the case). What fun! You should be able to get around this by setting the variant and compiler to be the same, e.g. {{{ sudo port install octave-devel +gcc47 configure.compiler=macports-gcc-4.7 }}} You might still need to reinstall octave-general. -- Ticket URL: <https://trac.macports.org/ticket/41238#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X