libmng versions 1.0.4, 1.0.5, 1.0.7 and 1.0.8 DEPEND on the lcms library, but they don't actually compile against it. This happens because they expect lcms.h, but the header file is present as lcms/lcms.h. The ebuilds already patch against the source file that includes it, but not the part of configure that checks whether it is present - as a result, it doesn't get as far as trying to include the header file. Reproducible: Always Steps to Reproduce: 1. emerge libmng, any of the versions mentioned above. 2a. Watch the output from configure for messages about lcms.h 2b. When it has compiled, run "ldd /usr/lib/libmng.so" Actual Results: 2a. configure says that lcms.h is not present. 2b. libmng.so is not linked against liblcms.so Expected Results: 2a. configure should find lcms.h (actually lcms/lcms.h) 2b. libmng.so should be linked against liblcms.so Patches coming....
Created attachment 48415 [details, diff] patch for libmng-1.0.4.ebuild
Created attachment 48416 [details, diff] patch for libmng-1.0.5.ebuild
Created attachment 48417 [details, diff] patch for libmng-1.0.7.ebuild
Created attachment 48418 [details, diff] patch for libmng-1.0.8.ebuild
I should point out that more recent versions of lcms-1.13.ebuild fix this bug within LCMS. I'm a little surprised the r-version wasn't bumped.
This should be fixed in libmng-1.0.8-r1