Opened 13 years ago

Closed 13 years ago

#28010 closed defect (fixed)

eog does not run after libpng ungrade

Reported by: jwhowse4 Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: drkp (Dan Ports)
Port: eog

Description

On an Intel Mac Pro running Snow Leopard 10.6.6 and XCode 3.2.5 eog crashes when I attempt to run it with the error message

dyld: Library not loaded: /opt/macports/lib/libpng12.0.dylib
  Referenced from: /opt/macports/bin/eog
  Reason: image not found
Trace/BPT trap

I uninstalled eog and tried to recompile it. The compilation fails and the error log file is attached. As an aside inkscape also fails to run with the same error message. I have not tried to recompile it yet.

Attachments (1)

eog_main.log (172.4 KB) - added by jwhowse4 13 years ago.
error log for eog compilation

Download all attachments as: .zip

Change History (5)

Changed 13 years ago by jwhowse4

Attachment: eog_main.log added

error log for eog compilation

comment:1 Changed 13 years ago by drkp (Dan Ports)

Cc: dports@… added
Owner: changed from macports-tickets@… to devans@…
Port: eog added

I just revbumped a bunch of ports that will require a rebuild after the libpng update, including eog and inkscape, so you should do a port selfupdate and port upgrade outdated.

comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Dan's revbump to eog in r75193 should be all that's needed; eog builds fine for me with libpng 1.4.5. Not sure why you're seeing:

/opt/macports/lib/libpng12.la: No such file or directory

Please let us know if you still see this problem after "sudo port selfupdate", "sudo port clean eog", and "sudo port upgrade outdated".

comment:3 in reply to:  2 Changed 13 years ago by drkp (Dan Ports)

Replying to ryandesign@…:

Dan's revbump to eog in r75193 should be all that's needed; eog builds fine for me with libpng 1.4.5. Not sure why you're seeing: /opt/macports/lib/libpng12.la: No such file or directory

If you were wondering where that particular message comes from, it's because one of the dependencies (it was either cairomm or pangomm, I forgot which) built a dylib that didn't link against libpng12, but the libtool .la file included a reference to libpng12 for reasons known only to libtool. I think it has something to with static linking. Worth keeping this in mind when revbumping dependents of a changed library because it's an easy one to miss.

If, on the other hand, you just weren't sure why *he's* seeing that message, then yeah, the revbump should take care of it. :-)

comment:4 Changed 13 years ago by drkp (Dan Ports)

Resolution: fixed
Status: newclosed

I'm assuming this is fixed by the revbump. Please reopen if it's still a problem.

Note: See TracTickets for help on using tickets.