Mark Knecht wrote:
On Thu, Jul 8, 2010 at 10:04 AM, Dale<rdalek1...@gmail.com> wrote:
Mark Knecht wrote:
I see there's a 2.8.1-r2 release this morning. Hopefully that will
solve my problems.
Cheers,
Mark
Ahhh, you are running unstable. I'm stable and using
dev-util/cmake-2.6.4-r3 so the fact that I have had no issues may be because
I am still on stable.
Dale
:-) :-)
Interestingly I am not running testing. I do _not_ have
ACCEPT_KEYWORDS="~amd64"
in my make.conf file and as best I can tell I didn't unmask or ask for
any version higher than stable. However the machine continues to try
and build testing on the cmake package only. To get around this in the
short term I masked the 2.8.1 series and got past that problem. Now
I'm just left with so many libpng errors I'm not sure I'll ever get it
sorted out.
Really, this weekend I need to understand this cmake problem. The
machine is not happy about something...
Cheers,
Mark
It may be stable for ~amd64. I'm on x86 where it is not stable.
The libpng issue has been discussed. Basically, go to a console, remove
the old libpng using emerge -C, then rm the old libpng files, emerge the
new libpng and run revdep-rebuild. It will rebuild a lot of packages.
I have KDE installed here and it rebuilt a LOT of that. You most likely
won't have a GUI during that either.
I think the most important part was to emerge -C and then rm the old
directory to make certain there was nothing left behind of the old
libpng. This is a link to a blog that I followed and it went pretty
well for me.
http://blog.flameeyes.eu/2010/06/29/stable-users-libpng-update
Hope that helps.
Dale
:-) :-)
