On 05/10/2010 08:11 PM, Gilles Dartiguelongue wrote: > Hello guys, > > as I'm sure some of you already experimented, the libpng upgrade didn't > exactly went smoothly on my chroots. Reason seems to be that libpng > usage is odd, it provides both libpng14.* and libpng.* files. Some > packages likes to use versioned libs while some other don't and it seems > to lead to giant mess in *.la files (for example).
Should we advise users to do something like: find /usr/lib -name '*.la' | xargs sed -i -e '/^dep/s:-lpng12:-lpng14:' ( Replace lib with lib64 on multilib system. ) > > My question are: > * is there a draft news item as a simple revdep-rebuild or portage > preserved-libs feature doesn't cut it (for good reasons) that I could > test ? -lpng12 vs. -lpng14 I guess, or then my big blockers in libpng ebuilds messed it up... those will go away soon, if arch's are fast enough with helping with the stable bug. > * what is the recommended way to link to libpng (versioned lib or not) > * corollary to previous question, should we enforce link to versioned > lib only ? > You get correct lib to link from `pkg-config --libs libpng` or if you need to avoid pkg-config, then e.g. AC_CHECK_LIB for unversioned png. Funny enough, I've also seen this done: libpng14 libpng12 libpng13 libpng In Cairo's configure. :) libpng13 for windows foo libpng for bsd foo libpng12 and 14 for linux foo bleh
