Changes between Initial Version and Version 1 of Ticket #30824
- Timestamp:
- Aug 16, 2011, 7:49:08 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30824
- Property Owner changed from macports-tickets@… to mlund@…
- Property Keywords xmgr removed
- Property Port openmotif added
-
Ticket #30824 – Description
initial v1 1 1 When I enter "xmgr" I get the following 2 {{{ 2 3 ~: xmgr 3 4 dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib … … 5 6 Reason: image not found 6 7 Trace/BPT trap 7 8 }}} 8 9 I tried following the steps below, but that didn't help. I am currently running mac osx 10.6.8. 9 10 10 A command failed to run with a message referring to libpng12.0.dylib11 > A command failed to run with a message referring to libpng12.0.dylib 11 12 12 Error message:13 dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib13 > Error message: 14 > dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib 14 15 15 Explanation:16 When the libpng port was updated from 1.2.x to 1.4.x, the libpng library version changed. Software always links against a specific library version, so the ports you currently have installed that depend on libpng are linked against a now-nonexistent version of the libpng library. To fix this problem, all ports that depend on libpng will need to be rebuilt so that they link with the new version of the libpng library. This may be quite a few ports.16 > Explanation: 17 > When the libpng port was updated from 1.2.x to 1.4.x, the libpng library version changed. Software always links against a specific library version, so the ports you currently have installed that depend on libpng are linked against a now-nonexistent version of the libpng library. To fix this problem, all ports that depend on libpng will need to be rebuilt so that they link with the new version of the libpng library. This may be quite a few ports. 17 18 18 Workaround:19 We have tried to find all affected ports and incremented the revision number. In most cases a simple upgrade should get them all fixed.19 > Workaround: 20 > We have tried to find all affected ports and incremented the revision number. In most cases a simple upgrade should get them all fixed. 20 21 21 sudo port selfupdate 22 sudo port upgrade outdated 22 > sudo port selfupdate 23 23 24 If this does not help, force a rebuild of the port in question by using the following command: 24 > sudo port upgrade outdated 25 25 26 sudo port -n upgrade --force $portname 26 > If this does not help, force a rebuild of the port in question by using the following command: 27 27 28 You should also file a ticket against the port in question. 28 > sudo port -n upgrade --force $portname 29 30 > You should also file a ticket against the port in question.