...

I really need help with this. kdevelop is the only

package I can't build.

...

Slackware 13.1.

Log:

http://humanreadable.nfshost.com/trinity/build_logs/kdevelop-3.5.13-i486-1-b...

Apparent problem:

cc1: error: tqt.h: No such file or directory

The path to tqt.h is available. See the environment

variables at the

...

beginning of the log. Also the log shows other parts

of the build are

...

finding tqt.h.

I am no CMake expert, but looking at the CMakeLists.txt file for the failing module: http://git.trinitydesktop.org/cgit/tdevelop/tree/parts/ctags2/CMakeLists.txt

and looking at the generated gcc compilation line: cd /dev/shm/kdevelop.build/parts/ctags2 && /usr/bin/gcc -Dlibkdevctags2_module_EXPORTS -DHAVE_CONFIG_H -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -O2 -march=i486 -mtune=i686 -fPIC -I/dev/shm/kdevelop.build/parts/ctags2 -I/dev/shm/kdevelop/lib/interfaces -I/dev/shm/kdevelop/lib/interfaces/extensions -I/dev/shm/kdevelop/lib/util -I/opt/trinity/include -include tqt.h -o CMakeFiles/libkdevctags2-module.dir/readtags.c.o -c /dev/shm/kdevelop/parts/ctags2/readtags.c

I would say that for some reason TQT_INCLUDE_DIRS is not set.

I never heard of this environment variable. There is nothing in the wiki discussing this variable.

With that said, look at the top of the log and you'll see environment variables. The tqt include directory is defined:

CPLUS_INCLUDE_PATH: /opt/trinity/lib/qt3-3.3.8.d/include:/opt/trinity/include:/usr/include:/usr/include/tqt

With that said, I temporarily modified the kdedevelop build script to explicitly export TQT_INCLUDE_DIRS=/usr/include/tqt. The build failed in the same exact way. :(

does this variable need to be declared inthe cmake options?

Where exactly is your tqt.h file located?

/usr/include/tqt/tqt.h

Darrell

...

I never heard of this environment variable. There is

nothing in the wiki

...

discussing this variable.

Sorry, it's not an environment variable. :-) I was unclear about that. It's an internal CMake variable--you can see it in the CMakeLists.txt file I linked to.

Okeydokey.

Can you post your CMake log file?

Here is the only log file I found (CMakeOutput.log):

http://humanreadable.nfshost.com/trinity/build_logs/CMakeOutput.log

Here are my build script options (the same as other build scripts:

rm ${TMP}/${PRGNAM}/CMakeCache.txt 2>/dev/null mkdir ${TMP}/${PRGNAM}.build cd ${TMP}/${PRGNAM}.build cmake ${TMP}/${PRGNAM} \ -DCMAKE_C_FLAGS:STRING="$CPUOPT" \ -DCMAKE_CXX_FLAGS:STRING="$CPUOPT" \ -DCMAKE_INSTALL_PREFIX=${PREFIX} \ -DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \ -DLIB_SUFFIX=${LIBDIRSUFFIX} \ -DMAN_INSTALL_DIR=${MANDIR} \ -DQTDIR=$QTDIR \ -DQT_LIBRARY_DIRS=${QTDIR}/lib \ -DWITH_QT3=ON \ -DUSE_QT3=ON \ -DBUILD_ALL=ON

Also interesting would be the file that contains the internal CMake variables, though I forget the name of it.

When you remember the name I'll send a copy. There are oodles of files with variables and I have no idea which one you are interested. :)

Darrell

...

When you remember the name I'll send a copy. There are

oodles of files

...

with variables and I have no idea which one you are

interested. :)

...

Understood. As you can tell I'm not too familiar with CMake's internal workings--Serghei Amelian is the real expert there. :-)

The file is CMakeCache.txt.

Here are two, the main one and the one from the seemingly affected directory:

Main:

http://humanreadable.nfshost.com/trinity/build_logs/CMakeLists.txt%20(main)

ctags2:

http://humanreadable.nfshost.com/trinity/build_logs/CMakeLists.txt%20(ctags2)

Darrell

...

...

The file is CMakeCache.txt.

Here are two, the main one and the one from the

seemingly affected

...

directory:

Main:

http://humanreadable.nfshost.com/trinity/build_logs/CMakeLists.txt%20(main)

ctags2:

http://humanreadable.nfshost.com/trinity/build_logs/CMakeLists.txt%20(ctags2)

Darrell

CMakeCache, not CMakeLists ;-)

Here : :)

http://humanreadable.nfshost.com/trinity/build_logs/CMakeCache.txt

Darrell

Found the problem. You will need to replace all instances of TQT_INCLUDE_DIRS with TQT_INCLUDEDIR in all of your CMakeLists.txt files.

Patched as directed.

Same exact failure. :( After the build failed I grepped all CMakeLists.txt file and all were patched correctly.

I looked at the kdepim, kdebase, and kdelibs sources, which use cmake. All of the CMakeLists.txt file use TQT_INCLUDE_DIRS rather than TQT_INCLUDE_DIR. Those packages built okay.

Darrell

Found the problem. You will need to replace all instances of TQT_INCLUDE_DIRS with TQT_INCLUDEDIR in all of your CMakeLists.txt files.

After posting my last response I noticed you had typed TQT_INCLUDEDIR and not TQT_INCLUDE_DIR. I did not know whether that was intentional or a typo. Regardless, I modified my patch and built again using TQT_INCLUDEDIR.

The package built. :)

Now, is this a Slackware issue or global?

There are two other patches I need to build kdevelop. I would like to know if this specific fix is global before I submit a bug report.

Darrell