Just tried to install qt-core-4.5.0_rc1 on a fresh install and I get the following error during src_compile: >>> Starting src_compile Could not find mkspecs for your QMAKESPEC(linux-g++) after trying: /usr/share/qt4/mkspecs Error processing project file: /var/tmp/paludis/x11-libs-qt-core-4.5.0_rc1/work/qt-x11-opensource-src-4.5.0-rc1/src/tools /bootstrap/bootstrap.pro !!! ERROR in x11-libs/qt-core-4.5.0_rc1: !!! In build_directories at line 833 !!! qmake failed !!! Call stack: !!! * build_directories (/var/tmp/paludis/x11-libs-qt-core-4.5.0_rc1/temp/loadsaveenv:833) !!! * qt4-build_src_compile (/var/tmp/paludis/x11-libs-qt-core-4.5.0_rc1/temp/loadsaveenv:4176) !!! * src_compile (/var/tmp/paludis/x11-libs-qt-core-4.5.0_rc1/temp/loadsaveenv:4442) !!! * ebuild_f_compile (/usr/libexec/paludis/2/src_compile.bash:54) !!! * ebuild_main (/usr/libexec/paludis/ebuild.bash:482) !!! * main (/usr/libexec/paludis/ebuild.bash:498) diefunc: making ebuild PID 25392 exit with error die trap: exiting with error. Install error: * In program paludis -i qt-core: * When performing install action from command line: * When executing install task: * When installing 'x11-libs/qt-core-4.5.0_rc1:4::gentoo': * When running an ebuild command on 'x11-libs/qt-core-4.5.0_rc1:4::gentoo': * Install error: Install failed for 'x11-libs/qt-core-4.5.0_rc1:4::gentoo'
This problem *might* be related to recent changes to qt4-build eclass. I will need some extra information if possible. Are you building qt-core with custom-cxxflags enabled? If yes, could you post here your CFLAGS? Also I would like you to attach the following files ( no matter if you are using custom-cxxflags or not ) "${S}"/mkspecs/$(qt_mkspecs_dir)/qmake.conf and "${S}"/mkspecs/common/g++.conf just after the compilation failure. Thank you
Created attachment 182696 [details] mkspecs/linux-g++/qmake.conf I actually did use custom-cxxflags but I also tried without. My current flags: export CHOST="x86_64-pc-linux-gnu" export CFLAGS="-march=core2 -O2 -pipe" export CXXFLAGS="${CFLAGS}" export LDFLAGS="-Wl,-O2,--hash-style=gnu,--sort-common,--as-needed" export MAKEOPTS="-j3"
Created attachment 182697 [details] mkspecs/common/g++.conf
Ok I narrow down the problem This snippet is completely wrong in your system ______________________________ Could not find mkspecs for your QMAKESPEC(linux-g++) after trying: /usr/share/qt4/mkspecs Error processing project file: /var/tmp/paludis/x11-libs-qt-core-4.5.0_rc1/work/qt-x11-opensource-src-4.5.0-rc1/src/tools /bootstrap/bootstrap.pro __________________________________ the generated Makefile is looking for mkspecs on /usr/share/qt4/mkspecs but it was supposed to look for them on "${S}"/mkspecs. Thats is really odd If you open "${S}"/src/tools/bootstrap/Makefile you will confirm my conclusion. The thing is that I cannot understand why qmake generates a completely wrong Makefile. Also , I ve never run to this problem again myself or seen it from any other user. So it is user/system specific. Could it be a paludis issue? or enviromental?
Created attachment 182705 [details] qt-x11-opensource-src-4.5.0-rc1/src/tools/bootstrap/Makefile hmm, negative. There's nothing about "/usr/share/qt4/mkspecs" in the mentioned file...
Created attachment 182714 [details] x11-libs/qt-core build log I am using Paludis, too, and I can confirm this error. # paludis --info paludis 0.34.4 Paludis build information: Compiler: CXX: x86_64-pc-linux-gnu-g++ 4.3.3 CXXFLAGS: -O3 -march=native -pipe -fomit-frame-pointer LDFLAGS: -Wl,-O1 DATE: 2009-02-14T15:32:38+0200 Libraries: C++ Library: GNU libstdc++ 20090124 Reduced Privs: reduced_uid: 101 reduced_uid->name: paludisbuild reduced_uid->dir: /var/tmp/paludis reduced_gid: 409 reduced_gid->name: paludisbuild Paths: DATADIR: /usr/share LIBDIR: /usr/lib64 LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc PYTHONINSTALLDIR: RUBYINSTALLDIR: /usr/lib64/ruby/site_ruby/1.8/x86_64-linux Environment: Format: paludis Config dir: /etc/paludis World file: /var/db/pkg/world
Ok, Makefiles are generated correctly as I can see from this build log. This should be a paludis bug since we never had such reports from portage users. Tiziano, do you want to ping paludis developers about this? I am afraid I cant do much since paludis is not officially supported. If somebody can reproduce this bug using portage pms, we will take a deeper look on this.
Fixed on cvs Closing
