1i5t5.duncan at cox
Oct 11, 2011, 4:00 PM
Post #3 of 7
V. Ram posted on Tue, 11 Oct 2011 13:28:06 -0700 as excerpted:
Re: kde-sunset: qt-meta-3.3.8b-r2 build failure with libpng < 1.5
[In reply to]
> Hello all and particularly kde-sunset team members:
> I did a fresh installation of gentoo from scratch, AMD64, with all
> stable packages and no keywords. I setup the kde-sunset overlay as per
> libpng is at 1.4.8-r1 (stable)
> During the emerge for kde-base/kdebase-startkde-3.5.10-r5 , the
> qt-meta-3.3.8b-r2 build failed with:
> kernel/qpngio.cpp:1153:48: error: png_process_data_pause was not
> declared in this scope.
> make: Leaving directory
> It looks like this may be due to the application of the libpng 1.5 patch
> from bug# 384953 without first checking to to see what version of libpng
> is installed.
> I'm not sure what I ought to do at this point. if I try to use libpng
> ~amd64 , I get a block with gdk-pixbuf-2.24.0-r1 . I've also read that
> revdep-rebuild with the libpng update is still problematic and that some
> applications still do not work with with libpng 1.5 .
> Suggestions on the best path forward?
FWIW, libpng-1.5 is soon to be stabilized, with remaining apps that don't
work with it masked for removal.
As it happens, there's a really long thread on gentoo-dev about it ATM,
since someone wasn't following mask-for-removal policy and at least one
package was removed before the 30-days-in-packagemask clock expired,
causing the package maintainer, who happened to be on vacation and thus
not catch it in time given the far shorter than normal masking, to
complain rather loudly about the policy violation.
But for what concerns this, I'd suggest keywording libpng-1.5.x for the
time being and doing the necessary rebuilds, as it's very close to being
stabilized anyway, and whatever remaining packages break with it are very
possibly going to be removed (if they haven't been already, AFAIK
everything they know about is either fixed or masked by now) in any case.
> Also, independently, it looks like there are no ebuilds for hal any more
> even though the kde-sunset packages look for the hal USE flag. I was
> never a big fan of hal, but automounting of media under KDE 3.5 is still
> nice to have, and as I understand it, without hal, that will no longer
> occur. Any recommendations on this issue as well?
As I, at a rather great time and hassle cost, switched to kde4 when
upstream was dumping kde3 (despite promises to the contrary, but that's
history now), and kde4 switched from hal with 4.6, I have little current
info on either end of this.
However, from what I've read, this is one of the things the trinity folks
are-dealing/have-dealt with since hal is pretty clearly toast at this
point. Since I've not even touched kde-sunset overlay, I've no idea if
there's builds for their releases or not, but if so, I'd presume they'd
be 3.5.11+. So you may wish to try those (if available) and see what
happens. But hopefully someone with rather more reliable and kde-sunset
specific information replies with better guidance here than I'm able to
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman