lmkasoul.blogg.se

You can always run 'port rev-upgrade' again to fix errors. > Found 11 broken ports, determining rebuild orderĭEBUG: Processing port R-app Processing port openmpi-gcc6 +fortranĭEBUG: Processing port openmpi-gcc49 +fortranĭEBUG: Processing port enblend Processing port hugin-app +accelerate+python27ĭEBUG: Processing port luminance-hdr +externalĭEBUG: Processing port ntop Processing port objectmarker Processing port libkdcraw Processing port libVLC +quartzĭEBUG: Processing port rb-eventmachine Processing port rb-twitter-stream Processing port rb-tweetstream Processing port sqlmap +python27ĭEBUG: Processing port openmpi-gcc5 +fortran Openmpi-gcc49 is using libstdc++ (this installation is configured to use libc++) Openmpi-gcc6 is using libstdc++ (this installation is configured to use libc++) Openmpi-gcc5 is using libstdc++ (this installation is configured to use libc++) Sqlmap is using libstdc++ (this installation is configured to use libc++)

Rb-eventmachine is using libstdc++ (this installation is configured to use libc++)

> Found 42 broken files, matching files to ports

When I tried to run port upgrade outdated and/or port rev-upgrade, something failed and I was presented with a list of broken ports, e.g.: Hi, I'm running MP 2.5.4 on a 2010 MBP with the latest version of Sierra (10.12.6/Darwin16.7.0).Īs mentioned in ticket #58072, I recently completed a selfupdate after not doing so for a long while.