Opened 13 years ago

Closed 12 years ago

#30824 closed defect (worksforme)

xmgr dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib not resolved by posting in description

Reported by: dixond@… Owned by: mlund (Mikael Lund)
Priority: Normal Milestone:
Component: ports Version: 2.0.1
Keywords: Cc:
Port: xmgr openmotif

Description (last modified by jmroot (Joshua Root))

When I enter "xmgr" I get the following

~: xmgr
dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib
  Referenced from: /opt/local/lib/libXm.4.dylib
  Reason: image not found
Trace/BPT trap

I tried following the steps below, but that didn't help. I am currently running mac osx 10.6.8.

A command failed to run with a message referring to libpng12.0.dylib

Error message: dyld: Library not loaded: /opt/local/lib/libpng12.0.dylib

Explanation: 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.

Workaround: We have tried to find all affected ports and incremented the revision number. In most cases a simple upgrade should get them all fixed.

sudo port selfupdate

sudo port upgrade outdated

If this does not help, force a rebuild of the port in question by using the following command:

sudo port -n upgrade --force $portname

You should also file a ticket against the port in question.

Change History (2)

comment:1 Changed 13 years ago by jmroot (Joshua Root)

Description: modified (diff)
Keywords: xmgr removed
Owner: changed from macports-tickets@… to mlund@…
Port: openmotif added

Please remember to cc the maintainer, and to preview and use WikiFormatting.

The openmotif port did get a revision increase when libpng was updated, see r75159. So the only explanation I can come up with is that maybe you upgraded things in the wrong order by using the -n or -R options.

When you say you "tried following the steps below," does that mean you ran this command?

sudo port -n upgrade --force openmotif

comment:2 Changed 12 years ago by jmroot (Joshua Root)

Resolution: worksforme
Status: newclosed

No response; closing. Stuff like this should be taken care of by rev-upgrade now anyway.

Note: See TracTickets for help on using tickets.