hmm it's even more complicated

On my other box, which has a more or less similar version running (I copied the whole disk of the other system to thisone a year ago, but kept them as synchrone as possible) I didn't have kdeinit complaining for libstdc++.so.6, but here I can't set a background picture, image previews don't work,... After updating gcc, everything works again.

What did the new kdelibs-3.2.2-2 do to cause all these problems?? 3.2.2-1 worked fine with the old gcc.

[damir@Asteraceae /]$ pacman -Qo /usr/lib/libstdc++.so.6
/usr/lib/libstdc++.so.6 is owned by gcc 3.4.0-1

and as gcc 3.4.0-1 is the standard now in the db of archlinux, you should use this gcc to run kdelibs with it (as you do now) --- kdelibs 3.2.2-2 also runs fine with gcc 3.3.x-y , but NOT with any of the gcc 2.x.y!

your system was still bootable: you have to press [ctrl][alt][f2] to go to the text-login

i cannot set gcc>=3.4.0 for kdelibs, because it is compiled against 3.3.3 and is known to run on any 3.x

-> close as "not a bug" - OK?

well you could set kdelibs gcc>=3.0.0 :)
then the bug will be gone and every 3.x can run it

I think I tried all ctrl alt fx but I must have missed f2 then :/
or maybe it didn't work because xfree was respawning kdeinit very fast

(not that it's that important, if it takes you 5 hours to compile and upload the package, you might as well wait for another kde release and update kdelibs then :)

a gcc>=3 is actually implied by using arch, because there is no 2.x pkg

if we take a look at the details, you are right with gcc>=3 (but quite no pkg in arch works with gcc=2.x) ... i will include gcc>=3 in the next release (it's too big for me to be uploaded in the next time)

hmm

now that I'm thinking

I was not using gcc 2.x but 3.2.3
it was the 3.2.x -> 3.3 upgrade that made a lot of apps break

so kdelibs doesn't work with every gcc >= 3.x since 3.2.3 gives a lot of problems

sorry for the confusion :(

ohh ... now it's more logical ;-)

... i had a look at the things in general and found out that actually xfree86 resolves the dependency of gcc for kdebase (over other pkgs) --- but kde has no deps to xfree86 or x ... funny

i will have a look at these "marginal deps" in the next time - thanx for bringing the subject up

note: please keep your whole system up-to-date --- then such upgrades like gcc 3.2.3 -> 3.3.1 are no problem for you in most cases --- and update it with pacman -Suy and not only one or 2 pkgs is often the best way

gcc 3.2.3 -> 3.3 was a problem because the compiler became much stricter

I also use a lot of custom apps that are not in pacman, which wouldn't compile with the new gcc - even the kernel wouldn't

that's why I held it back, but I guesse most programs can be compiled with the new gcc now

I pacman -Syu on a daily base :)

kde needs a rebuild against gcc 3.4.0, but as in about a month 3.2.3 will be released - it is maybe not really that important for 3.2.2 <-> gcc

kde 3.2.3 was compiled whole against gcc 3.4, so closing this bug