OY take arson for example: emerge arson [SNIP!] checking for Qt... configure: error: Qt (>= Qt 3.0.2) (library qt-mt) not found. Please check your installation! For more details about this problem, look at the end of config.log. Make sure that you have compiled Qt with thread support! If I do a /var/tmp/portage/arson-0.9.6/work/arson-0.9.6-kde3/configure it configure with no problems like so: checking for Qt... libraries /usr/qt/3/lib, headers /usr/qt/3/include using -mt can some one explain this to me?
Just to let you know what qt 2 programs do not have the same problem
Please give me (attach, not via mail) your config.log from the builddir (the one generated when it fails to find qt). Also, please give me /var/tmp/portage/<dir>/temp/eclass-debug.log.
Look at the config.log line 1038. This is the actual error: it can't find i686-pc-linux-gnu-g++ - hm... This looks like PATH / environment setting trouble to me, which would explain the difference between manual compiling (shell's environment) and emerging (somewhat different env). 1. What compiler are you using (gcc, what version)? Where do you have your i686-pc-linux-gnu-g++ - maybe not in the standard location for some reason (which is /usr/bin)? 2. Do you use ccache? With a custom config or the standard portage one from the latest versions? 3. Any other interesting env. setting trouble/peculairities/customizations that might bear on the issue?
Oh, and I completely forgot: maybe you have an i586-pc-linux-gnu-g++ or something else that isn't an i686?
#slocate 686-pc-linux-gnu-g++ /usr/bin/ccache/i686-pc-linux-gnu-g++ /usr/bin/i686-pc-linux-gnu-g++-3.0 /usr/bin/i686-pc-linux-gnu-g++-3.1 yes I use ccache and yes it is from portage, I worked around the problem by downgrading to portage 2.0.5. But that is not really a fix. I do nothing wierd with env, and I have a i686.
Hi! Just a workaround, but it works fine here: ln -s /usr/bin/i686-pc-linux-gnu-gcc /usr/bin/i686-pc-linux-gnu-g++ Markus
Please forget my last comment. The qt-check works with this symlink but afterwards there's a linking problem. Sorry!
Am I totally nuts? Finally: The symlink should be of course: ln -s /usr/bin/g++ /usr/bin/i686-pc-linux-gnu-g++
Yes, exactly, that's the symlink you ned to have. Ones with -3.0 and -3.1 at the end are not enough, many configure scripts (like the kde ones) assume the existence of a /usr/bin/$CHOST-g++. So, now that you've made the symlink the problem should be gone. As to why it wasn't there in the first place, it's likely the problem with the gcc ebuilds that was fixed a few days ago (there was an announcement). This symlink disappearing is one of the problem's symptoms, and you might want to remerge gcc to make sure the symlink is created. However, I don't know how the gcc 3.0 and 3.1 side-by-side setup is managed ebuild-wise, and remerging gcc will probably make it default. But you know how you set that up better than me :-) So, hopefully this bug can be losed, at least the kde part.
Closing, then.
