I try to emerge quanta and a strange error appear when it try to recompile kde libs 2.2.2 Configure: error: "no known STL type found" i'v KDELib 3.0.1 and now i'm unable to compile new 3.0.2 for this error .
what gcc version are you using?
*** Bug 4493 has been marked as a duplicate of this bug. ***
Could you please give some output where the error shows, with a couple of context paragraphs in either direction?
I had the same errors compiling kde 1.0.2 using gcc 2.95.3 20010315 (release) : checking if Qt compiles without flags... no checking if STL implementation is SGI like... no checking if STL implementation is HP like... no configure: error: "no known STL type found - did you forget to install libstdc++-devel ?" !!! ERROR: The ebuild did not complete successfully. !!! Function kde_src_compile, Line -3993, Exitcode 1 !!! died running ./configure, kde_src_compile:configure !!! emerge aborting on /usr/portage/kde-base/arts/arts-1.0.2.ebuild . If I ./configure at the hand in /var/tmp/portage/arts-1.0.2/, there is no problem at this point...
Oups, an error in the previous comments "compiling arts 1.0.2" not kde... so, i did some research and found that there where a link named i686-pc-linux-gnu-g++ in /usr/bin/ccache. So i moved this folder in /root and then the problem disappears. It seems that this problem come from ccache which is used by ebuild.
I use gcc 2.95.3 you think i must upgrade to 3.1 ? I'v another error to report using kde font installer to install new font for my work, i receive error by mozilla thet can't handle them and do not start. This kde utils write the font path to my XF86config-4 file and after x do not start. Why? I use Mozilla 1.0 gcc 2.95.3 and kde 3.0.1 I try ccache too but now i disable it that it make me some errors.
No, there's no need to upgrade your gcc to 3.1. Both of you: do you have a /usr/bin/i686-pc-linux-gnu-g++ (installed by gcc)? If not, create it as a symlink to /usr/bin/g++ and ee if the problem goes away. ou can re-enable ccache after this too, if I'm right this isn't the source of the problem. Emerging gcc again might help too (create the symlink if I'm right or dispose of whatever else the problem may be if I'm wrong).
Oh, and please report your other bugreport (fonts) separately and in as great detail as possible.
No user response, closing.
