From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cmake-2.8.1 build problems
Date: Fri, 9 Jul 2010 11:49:53 -0700 [thread overview]
Message-ID: <AANLkTilvCOe49ij1ILfHvD8gPqQB-0A5ObhjYDNwsYtY@mail.gmail.com> (raw)
In-Reply-To: <4C376CBB.1060306@gmail.com>
On Fri, Jul 9, 2010 at 11:38 AM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>>
>> On Thu, Jul 8, 2010 at 10:04 AM, Dale<rdalek1967@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
>
> :-) :-)
Thanks to both you and Arttu.
As for libpng I've straightened it out on 3 other machines to date,
all 64-bit, but this last machine is causing me fits. Fortunately I
have two of these machines with the same motherboard, processor, VGA.
Only sound is different. The other one worked out OK with libpng so
I'll likely just slog through a comparison, config file by config
file, to find the differences.
Thanks for the link. It should be helpful.
Cheers,
Mark
next prev parent reply other threads:[~2010-07-09 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 22:10 [gentoo-user] cmake-2.8.1 build problems Mark Knecht
2010-07-08 4:38 ` Dale
2010-07-08 13:32 ` Mark Knecht
2010-07-08 16:22 ` Mark Knecht
2010-07-08 17:04 ` Dale
2010-07-09 15:40 ` Mark Knecht
2010-07-09 18:38 ` Dale
2010-07-09 18:49 ` Mark Knecht [this message]
2010-07-09 19:31 ` Bill Longman
2010-07-09 19:38 ` Dale
2010-07-09 19:41 ` Alan McKinnon
2010-07-09 16:52 ` Arttu V.
2010-07-10 1:33 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTilvCOe49ij1ILfHvD8gPqQB-0A5ObhjYDNwsYtY@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox