Robert Crawford wrote:
> I just completed the kde install on my main box. I had a few problems on
> my test box, but after I did another emerge sync, and upgraded my automake
> and autoconf, I compiled without a hitch.
> I recommend doing another sync, and the updates first, and if you have
> any
> other 3.2 betas or rc's installed, boot to gnome or a terminal, and
> unmerge them first. ( first rename your .kde folder to oldkde, so you can
> copy back your bookmarks and/or configs later). The last emerge sync
> apparently corrected a bunch of compiling problems in the ebuilds. There's
> some threads on the forum talking about these things, but the newest sync
> fixes them, and all the patches are not needed now.
Robert,
thanks for your reply. Unfortunately, my problems are not solved yet. If
anything, they seem to get worse. Here's what I did:
- switched to gnome and unmerged all kde-ebuilds, including the 3.2rc1
ebuilds I had installed earlier.
- emerge sync
- tried to install kde3.2 with
ACCEPT_KEYWORDS="~x86" emerge kde
- arts and kdelibs got installed without problems, kdebase produces the same
error message.
- tried to update my system with
emerge -U world
- here I ran into another problem with madplay which I'm trying to fix as
suggested in
http://www.mail-archive.com/[EMAIL PROTECTED]/msg32655.html .
Since this is a relatively new install, I'm almost willing to do a
reinstall. Maybe my experimenting with ~x86 to install kde3.2rc1 mixed
something up. The only thing I can think of to try is to compare my
settings with a "known good" configuration. Would you mind telling me which
versions of autoconf, automake and m4 are installed on your machine? Maybe
this helps.
regards
Jerry
--
[EMAIL PROTECTED] mailing list
