Please provide a build log.

I am building tdenetwork from GIT on Slackware with no such errors. Here are my build options:

cmake $SOURCES_ROOT \
  -DCMAKE_C_FLAGS:STRING="$CPUOPT" \
  -DCMAKE_CXX_FLAGS:STRING="$CPUOPT $DEBUG_CMAKE_OPT" \
  -DCMAKE_INSTALL_PREFIX=${PREFIX} \
  -DSYSCONF_INSTALL_DIR=${SYSCONFDIR} \
  -DLIB_SUFFIX=${LIBDIRSUFFIX} \
  -DMAN_INSTALL_DIR=${MANDIR} \
  -DWITH_ARTS=ON \
  -DWITH_SPEEX=ON \
  -DWITH_WEBCAM=ON \
  -DBUILD_WIFI=ON \
  -DWITH_JINGLE=ON \
  -DBUILD_KOPETE_PROTOCOL_TESTBED=ON \
  -DBUILD_KOPETE_PROTOCOL_GROUPWISE=ON \
  -DBUILD_KOPETE_PROTOCOL_MSN=ON \
  -DBUILD_KOPETE_PROTOCOL_IRC=ON \
  -DBUILD_KOPETE_PROTOCOL_YAHOO=ON \
  -DBUILD_KOPETE_PROTOCOL_WINPOPUP=ON \
  -DBUILD_KOPETE_PROTOCOL_JABBER=ON \
  -DBUILD_ALL=ON || exit 1

I build most Trinity packages from GIT. Just about everything builds. I am using Trinity GIT packages in daily usage. There are a few problems, as reported in bug reports, but very few show stoppers.

Regarding "external programs," which ones are broken? I am able to build ktorrent, amarok, and most other external programs provided in the Trinity applications source tree. There are a few I don't build because they are Debian related and I use Slackware, but I am able to build every external program that I want to build.

If you mean you are trying to build/use the original KDE3 versions of these programs against the Trinity sources, then that makes sense they no longer work. Much like the original KDE3, Trinity is a self contained environment and must be built as a full environment.

I also use KDE 3.5.10 in my daily usage. I don't try to intermix KDE 3.5.10 with Trinity. I treat both as separate environments.

(In reply to comment #1)
> Please provide a build log.
Please simple see to line 64 into file kopete/protocols/sms/services/smsclient.cpp and count brackets '(' and ')':
TQString provider = c->readEntry(TQString("%1:%2").arg("SMSClient").arg("ProviderName");

> I am building tdenetwork from GIT on Slackware with no such errors. Here are my
> build options:
My options:
    -DWITH_JINGLE=ON \
    -DBUILD_KOPETE_PROTOCOL_ALL=ON \
    -DBUILD_KOPETE_PROTOCOL_MSN=OFF \
    -DBUILD_KOPETE_PLUGIN_ALL=ON \
    -DBUILD_KOPETE_PLUGIN_NETMEETING=OFF \
    -DWITH_SPEEX=ON \
    -DWITH_WEBCAM=ON \
    -DWITH_GSM=ON \
    -DWITH_ARTS=OFF \
    -DBUILD_ALL=ON

> Regarding "external programs," which ones are broken? I am able to build
> ktorrent, amarok, and most other external programs provided in the Trinity
> applications source tree. 
I am doing build and maintains for stable version TDE 3.5.13 for distributive ALTLinux. More external programs and some core are some functional broken, mostly after unnecessary renaming with prefix "tq". For example broken ktorrent and amarok and I without problem build its from original sources. Why was it necessary to break the programs into 3.5.13 and next break full compatibility after 3.5.13?

(In reply to comment #0)
> In file kopete/protocols/sms/services/smsclient.cpp present lines 62 70 100
> 107, which exactly error:
> TQString provider =
> c->readEntry(TQString("%1:%2").arg("SMSClient").arg("ProviderName");
> 
> File kopete/protocols/jabber/kioslave/CMakeLists.txt, into section "LINK"
> included twice "idn" which cause build error.

Fixed in GIT hash 6f17856.

> P.S. Do you realy test your mass renaming from edge to edge?

It has been generally well-tested over time, but obviously corner cases and other little-used code may not have been fully verified.  That is the function of users and this bug tracker. :-)

> P.P.S. Why at last you have broken compatibility for build original external
> KDE3 programs, by rename kdeversion.h to tdeversion.h? Do you realy think that
> you have adapted all possible external programs?

Of course not!  You are still free to use the obsolete KDE 3.5.10 source/binaries, and to install external programs on top of that base.  TDE must continue to move forward; however if you think a valuable external program has been abandoned, please file a bug report asking for inclusion of that program into the TDE source tree.

> P.P.P.S. After your "adapting" some external programs work wrong, for last
> stable version TDE: ktorrent, amarok and some other!

This is not surprising.  Keep in mind that those programs had bugs in the last stable version of KDE that have been fixed as well; software changes over its life; as old bugs are stamped out new ones may crop up.