Kurt, Please remove the 10.9 from the distribution field of libpng16 in 10.7 branch and switch the gdal.info to use libpng16. I am pretty certain you are just seeing false positives in the gdal png.py autotest due to corrupted png files in their testsuite. The error messages you see with libpng16 in the png.py autotest...
ERROR 1: data/test.png, band 1: IReadBlock failed at X offset 0, Y offset 29 are identical to these reported for licq... https://github.com/licq-im/licq/pull/32 Note the comment in their bug report... The PNG images of the Mirabilis skin fail to load with libpng 1.6. The error, "IDAT: invalid distance too far back", is triggered by bad CMF bytes in these PNG files. I used optipng (statically linked against libpng 1.4.12) to optimize, and thus fix, the affected images. So upstream needs to regenerate the test png files used in the autotest for gdal to have uncorrupted CMF bytes in their png files as well. Jack ps Thanks in advance for eliminating the needless pollution of libpng15 back onto 10.9 machines. ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
