Wed, Jul 18, 2012 at 08:37:30AM +0400, Eygene Ryabinkin wrote: > Thu, Jul 12, 2012 at 12:26:15AM -0400, Henry Hu wrote: > > For the png problem, I think that we can use png_jmpbuf for any > > libpng > > >= 1.2.5? It seems to be exist at least from libpng 1.2.5 > > (http://www.libpng.org/pub/png/libpng-1.2.5-manual.html) so it's > > safe to use it? > > Should be. But according to the portability note at > http://www.libpng.org/pub/png/libpng.html > "The libpng 1.5.x series continues the evolution of the libpng API, > finally hiding the contents of the venerable and hoary png_struct and > png_info data structures inside private (i.e., non-installed) header > files." So it is normal to use the "new" API only for >= 1.5.x. > > Mon, Jul 16, 2012 at 01:07:06AM -0700, Doug Barton wrote: > > Where are we at with this? I'm using the latest png with your patch and > > it is working fine, although only a few of my backgrounds are PNGs. > > I had tested it with PNG 1.4.10 -- works fine. So, I had changed > the required library version for png from '15' to '1[45]'. The patch > was modified accordingly, > http://codelabs.ru/fbsd/ports/slim/upgrade-1.3.3-to-1.3.4.diff
Ping! Were there any testers of the updated slim port? If yes, please, speak up. -- Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ]
pgpnJrHKNoLnG.pgp
Description: PGP signature
