[MacPorts] #42645: ffmpeg @2.1.3 - Configure: cant find libmodplug, libpng15

[MacPorts]

#42645: ffmpeg @2.1.3 - Configure: cant find libmodplug, libpng15
-------------------------+----------------------
  Reporter:  mhfadams@…  |      Owner:  devans@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.2.1
Resolution:              |   Keywords:
      Port:  ffmpeg      |
-------------------------+----------------------
Changes (by cal@…):

 * owner:  macports-tickets@… => devans@…
 * cc: mhfadams@… (removed)
 * cc: jeremyhu@… (added)
 * port:   => ffmpeg


Comment:

 You don't need to Cc yourself when reporting tickets, but please set the
 port field and Cc the port's maintainer.

 Replying to [ticket:42645 mhfadams@…]:
 > --> Error during configure: ffmpeg couldn't locate libmodplug;\\
 > --> Error during configure: ffmpeg couldn't locate libpng15;

 libpng is at 1.6.9 in MacPorts; no surprise it can't find libpng 1.5. As
 to why libmodplug fails I don't know; you would have to attach main.log
 for somebody to be able to debug, but...

 > Errors were solved by manually installing libmodplug  and libpng15
 (./configure --prefix=/opt/local) from non macport sources;

 That's the worst thing you could have done. You should '''never ever'''
 manually install software into MacPorts' prefix. Even worse, that
 operation has probably overwritten files installed by MacPorts, e.g.
 `/opt/local/lib/libpng.dylib`, which other binaries use. That might have
 broken these binaries. Basically you've gotten your MacPorts installation
 into a state where builds are going to fail for random reasons and no way
 for the port maintainers to help you in figuring out what went wrong.
 There's also no easy way to go back to a consistent state short of
 uninstalling all ports, deleting MacPorts and re-installing from scratch.

-- 
Ticket URL: <https://trac.macports.org/ticket/42645#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X