Marius, Thanks for the fast reply! I didn’t see anything in Trac about this, so I had guessed that I had done something wrong in my installation. From what you say, this is not a pilot error.
++Eric From: Marius Schamschula <li...@schamschula.com> Date: Tuesday, September 26, 2017 at 6:47 AM To: "Eric J. Fielding" <eric.j.field...@jpl.nasa.gov> Cc: "macports-users@lists.macports.org" <macports-users@lists.macports.org> Subject: Re: repairing broken port Eric, I looks like py-matplotlib-basemap needs a revision bump. If no one beats me to it, I should get around to this in the afternoon. Marius -- Marius Schamschula On Sep 26, 2017, at 8:42 AM, Fielding, Eric J (329A) <eric.j.field...@jpl.nasa.gov<mailto:eric.j.field...@jpl.nasa.gov>> wrote: I have a file that shows up as broken in the automatic scan of the port command: ---> Scanning binaries for linking errors ---> Found 1 broken file, matching files to ports ---> Found 1 broken port: py27-matplotlib-basemap @1.0.7 /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so I tried uninstalling and installing again “py27-matplotlib-basemap”, but that does not fix this file. I checked the file “_geoslib.so” with “otool –L” and I see that it is linked to an obsolete version of the “libgeos” library (the installed version is libgeos-3.6.2.dylib): % otool -L /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/_geoslib.so: /opt/local/lib/libgeos_c.1.dylib (compatibility version 11.0.0, current version 11.0.0) /opt/local/lib/libgeos-3.5.0.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) How do I get the “_geoslib.so” to update correctly? Should I manually remove it to force MacPorts to rebuild it? Thanks, ++Eric