public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@sympatico.ca>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] escape from hell: kdelibs
Date: Sun, 2 Jul 2006 08:47:02 -0400	[thread overview]
Message-ID: <20060702124702.GA4808@sympatico.ca> (raw)

First, no criticism of Gentoo's hardworking devs intended or implied.

I thought I'ld try GCC 4.1.1, Glibc 2.4 & update to KDE 3.5.3 .
They're all still "testing", but we do have some responsibility to test,
& they've been there for a while without reports of painful experiences.

Having dealt with GCC & Glibc according to the docs,
I tried to compile Kdelibs 3.5.3 & got a long series of "can't find" msgs
followed by failure: there are a number of similar reports in the Forum.
Flameyes seems to give the authoritative response at Forum 060602 0917 :
  http://forums.gentoo.org/viewtopic-t-467029-postdays-0-postorder-asc-start-50.html?sid=759b61da629afeca0dfc16ee01411a17

Following this advice, I unmerged the previous Kdelibs
& tried again with the same result.  A bit more poking around
& I decided the best course was to return to the original state of affairs
& restore GCC 3.4.5, Glibc 2.3 & KDE 3.5.2 .  However when I did,
Kdelibs 3.5.2-r6 failed with the same error !  So recompile everything again
to try to make sure they were all in sync: same bad result !

Being experienced, I had made a quick-package of Kdelibs 3.5.2 ,
which I now tried to re-install via 'emerge -K': it refused,
demanding Qt 3.3.6 -- no longer in Portage -- , where I had 3.3.6-r1 .

Finally, I tried 'emerge -K --nodeps =kdelibs-3.5.2-r6', which worked !
I've rebooted & restarted KDE & all seems to be back to normal.

However, something is still not right with GCC 4.1.1, Glibc 4.2 & KDE 3.5.3 .
There was a recent request on Gentoo Dev for people to test things
prior to stabilising these items for the next profile, so I HTH (smile).

Anyone else have experiences to share ?  Any known-to-work solution ?

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-07-02 13:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 12:47 Philip Webb [this message]
2006-07-02 15:04 ` [gentoo-user] escape from hell: kdelibs Hemmann, Volker Armin
2006-07-03  3:12   ` Philip Webb
2006-07-03  4:05     ` Hemmann, Volker Armin
2006-07-03 14:06     ` [gentoo-user] kdelibs again: 'moc' & USE flags ? Philip Webb
2006-07-03 16:20       ` Richard Fish
2006-07-03 16:40         ` Philip Webb
2006-07-03 17:51           ` [gentoo-user] kdelibs : solved ! blame confcache ! Philip Webb
2006-07-03 18:28             ` Neil Bothwick
2006-07-03 18:31             ` Rumen Yotov
2006-07-03 22:03           ` [gentoo-user] kdelibs again: 'moc' & USE flags ? Richard Fish
2006-07-04  8:04             ` Philip Webb
2006-07-04 16:28               ` Philip Webb
2006-07-04 22:17                 ` Richard Fish
2006-07-03 17:34         ` Uwe Thiem

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=20060702124702.GA4808@sympatico.ca \
    --to=purslow@sympatico.ca \
    --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