I've started a new thread, since this is now a 'make' problem instead of a configure problem. It also looks like this might be an x86_64 issue because I am currently building kdebase on i686 with the *exact* same build scripts and it seems to be working fine. (well until it bombed later -- see at end)

Here is the background from the prior thread:

...

==> Packaging - trinity-kdebase-1218548

...

...

make: *** No rule to make target `install'. Stop. Aborting...

Looking at the Makefile generated in the out-of-source dir, it does NOT contain any install: target. Looking at the Makefile in the original trinity/kdebase directory is does contain install: install-recursive. My bet is that is what needs to be called. I don't know why kdebase is exhibiting this behavior with make targets when tqtinterface, arts, and kdelibs all had no problem with the install: target. Any ideas? I'll try calling make -f ../Makefile and see if that works.

add "-DBUILD_ALL=ON" to cmake arguments

<snip>

Hmm...

I updated the cmake command to:

cmake ../ \ -DCMAKE_INSTALL_PREFIX=${trinity_prefix} \ -DWITH_QT3=ON \ -DBUILD_ALL=ON \ -DCMAKE_SKIP_RPATH=ON make || return 1

I still get the error:

config.status: executing libtool commands

Good - your configure finished. Start make now

-- checking for 'TDE' -- found 'TDE', version 3.5.10 -- Configuring done -- Generating done -- Build files have been written to: /dat_e/david/bld/trinity/kdebase/src ==> Entering fakeroot environment... ==> Determining SVN revision for trinity-kdebase... ==> Starting package()... ==> Packaging - trinity-kdebase-1218548 make: *** No rule to make target `install'. Stop. Aborting...

I have put the trinity/kdebase/Makefile here:

http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-Makefile

the trinity/kdebase/src/Makefile is:

http://www.3111skyline.com/dl/dt/trinity/errors/kdebase_src-Makefile

the config.log is here:

http://www.3111skyline.com/dl/dt/trinity/errors/kdebase-config-3.log

I spoke too soon, the i686 build just died as well:

[ 11%] Generating kickerSettings.cpp Scanning dependencies of target kickermain-shared [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/appletinfo.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/global.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickertip.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/menuinfo.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/panelbutton.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/panner.cpp.o [ 11%] Building CXX object kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o In file included from /usr/include/QtCore/QFile:1:0, from /home/david/arch/pkg/trinity/kdebase/src/kicker/libkicker/kickerSettings.cpp:7: /usr/include/QtCore/qfile.h:53:1: error: ‘QT_BEGIN_HEADER’ does not name a type /usr/include/QtCore/qfile.h:62:27: error: expected initializer before ‘:’ token make[2]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/kickerSettings.cpp.o] Error 1 make[1]: *** [kicker/libkicker/CMakeFiles/kickermain-shared.dir/all] Error 2 make: *** [all] Error 2 Aborting...

Judging from the error, it still looks like it is grabbing Qt4 headers (/usr/include/QtCore). I have /opt/qt first in PATH and I have set:

export CMAKE_PREFIX_PATH=/opt/qt export CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt

So I'm not sure how it is grabbing the /usr/include files (it may be OK) Oh well, that's for tomorrow.

If you have any thoughts, let me know. Thanks.