>Ok, old error (http://paste.pocoo.org/show/454963/) returned. Could >this be something with my building env, or it is cmake/trinity >related? Hello, I've just encountered the same symptom while compiling the kdelibs from SVN on RHEL 6: dcopserver.cpp not linking, preprocessing macros HAVE_SYS_STAT_H (and others) being ignored ... I then discovered that my freshly compiled QT 3.3.8d (from SVN too) has installed a file "include/config.h", which is included in kdelibs compilation INSTEAD of the "build/config.h" generated by cmake. So I compared the RHEL6-provided QT3 (3.3.8b) with the TDE-provided QT3 (3.3.8d) and I found that 3.3.8d installs a lot of new files that did not exist in 3.3.8b : I don't know if this is a QT change or a RHEL specific behaviour. Here is the full list of NEW files that I get on an installed 3.3.8d, compared to 3.3.8b : > /usr/lib64/qt-3.3/bin/createcw > /usr/lib64/qt-3.3/bin/makeqpf > /usr/lib64/qt-3.3/bin/mergetr > /usr/lib64/qt-3.3/bin/msg2qm > /usr/lib64/qt-3.3/include/btree.h > /usr/lib64/qt-3.3/include/config.h > /usr/lib64/qt-3.3/include/crc32.h > /usr/lib64/qt-3.3/include/debian_qsql_odbc.h > /usr/lib64/qt-3.3/include/deflate.h > /usr/lib64/qt-3.3/include/ftglue.h > /usr/lib64/qt-3.3/include/ftxgdef.h > /usr/lib64/qt-3.3/include/ftxgpos.h > /usr/lib64/qt-3.3/include/ftxgsub.h > /usr/lib64/qt-3.3/include/ftxopen.h > /usr/lib64/qt-3.3/include/ftxopenf.h > /usr/lib64/qt-3.3/include/hash.h > /usr/lib64/qt-3.3/include/inffast.h > /usr/lib64/qt-3.3/include/inffixed.h > /usr/lib64/qt-3.3/include/inflate.h > /usr/lib64/qt-3.3/include/inftrees.h > /usr/lib64/qt-3.3/include/jchuff.h > /usr/lib64/qt-3.3/include/jconfig.h > /usr/lib64/qt-3.3/include/jdct.h > /usr/lib64/qt-3.3/include/jdhuff.h > /usr/lib64/qt-3.3/include/jerror.h > /usr/lib64/qt-3.3/include/jinclude.h > /usr/lib64/qt-3.3/include/jmemsys.h > /usr/lib64/qt-3.3/include/jmorecfg.h > /usr/lib64/qt-3.3/include/jpegint.h > /usr/lib64/qt-3.3/include/jpeglib.h > /usr/lib64/qt-3.3/include/jversion.h > /usr/lib64/qt-3.3/include/libmng.h > /usr/lib64/qt-3.3/include/libmng_chunk_io.h > /usr/lib64/qt-3.3/include/libmng_chunk_prc.h > /usr/lib64/qt-3.3/include/libmng_chunks.h > /usr/lib64/qt-3.3/include/libmng_cms.h > /usr/lib64/qt-3.3/include/libmng_conf.h > /usr/lib64/qt-3.3/include/libmng_data.h > /usr/lib64/qt-3.3/include/libmng_display.h > /usr/lib64/qt-3.3/include/libmng_dither.h > /usr/lib64/qt-3.3/include/libmng_error.h > /usr/lib64/qt-3.3/include/libmng_filter.h > /usr/lib64/qt-3.3/include/libmng_jpeg.h > /usr/lib64/qt-3.3/include/libmng_memory.h > /usr/lib64/qt-3.3/include/libmng_object_prc.h > /usr/lib64/qt-3.3/include/libmng_objects.h > /usr/lib64/qt-3.3/include/libmng_pixels.h > /usr/lib64/qt-3.3/include/libmng_read.h > /usr/lib64/qt-3.3/include/libmng_trace.h > /usr/lib64/qt-3.3/include/libmng_types.h > /usr/lib64/qt-3.3/include/libmng_write.h > /usr/lib64/qt-3.3/include/libmng_zlib.h > /usr/lib64/qt-3.3/include/moc_yacc.h > /usr/lib64/qt-3.3/include/opcodes.h > /usr/lib64/qt-3.3/include/os.h > /usr/lib64/qt-3.3/include/otlbuffer.h > /usr/lib64/qt-3.3/include/pager.h > /usr/lib64/qt-3.3/include/parse.h > /usr/lib64/qt-3.3/include/png.h > /usr/lib64/qt-3.3/include/pngasmrd.h > /usr/lib64/qt-3.3/include/pngconf.h > /usr/lib64/qt-3.3/include/sqlite.h > /usr/lib64/qt-3.3/include/sqliteInt.h > /usr/lib64/qt-3.3/include/trees.h > /usr/lib64/qt-3.3/include/vdbe.h > /usr/lib64/qt-3.3/include/vdbeInt.h > /usr/lib64/qt-3.3/include/zconf.h > /usr/lib64/qt-3.3/include/zconf.in.h > /usr/lib64/qt-3.3/include/zlib.h > /usr/lib64/qt-3.3/include/zutil.h > /usr/lib64/qt-3.3/mkspecs/linux-g++-sparc > /usr/lib64/qt-3.3/mkspecs/linux-g++-sparc/qmake.conf > /usr/lib64/qt-3.3/mkspecs/linux-g++-sparc/qplatformdefs.h In my case, I simply deleted all these files, and now the 'config.h' problem is gone. I hope it can help you. Francois Andriot