All,
With kchmviewer, the configure fails with the following:
<snip>
Please remember to use GNU make, often installed as gmake.
Install prefix : /opt/trinity
KDE support : disabled.
Qt includes :
Qt libraries :
chmlib to link : system
checking if lib should be compiled... yes
checking if po should be compiled... yes
checking if src should be compiled... yes
checking that generated files are newer than configure... done
configure: error: conditional "include_x11" was never defined.
Usually this means the macro was only invoked conditionally.
OK, which macro should be checked and in what file?
--
David C. Rankin, J.D.,P.E.
All,
kstreamripper fails to build with a scons error that I have no idea what it is
saying. The error is:
==> Building - tde-kstreamripper...
scons: warning: The Options class is deprecated; use the Variables class instead.
File "/build/src/kstreamripper/admin/generic.py", line 61, in generate
KeyError: 'TQTINCLUDEPATH':
File "/build/src/kstreamripper/SConstruct", line 70:
env = Environment(TARGS=COMMAND_LINE_TARGETS, ARGS=ARGUMENTS,
tools=['default', 'generic', 'kde'], toolpath=['./', './admin'])
File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 999:
apply_tools(self, tools, toolpath)
File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 105:
env.Tool(tool)
File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 1783:
tool(self)
File "/usr/lib/python2.7/site-packages/SCons/Tool/__init__.py", line 180:
self.generate(env, *args, **kw)
File "/build/src/kstreamripper/kde.py", line 458:
env.Append(CXXFLAGS = ['-I'+env['KDEINCLUDEPATH'],
'-I'+env['QTINCLUDEPATH'], '-I'+env['TQTINCLUDEPATH'], '-include', 'tqt.h' ])
File "/usr/lib/python2.7/site-packages/SCons/Environment.py", line 409:
return self._dict[key]
Where do we even start on this one?
--
David C. Rankin, J.D.,P.E.
Tim, All,
After getting around the glibc 2.16/rpcgen issue, the build went well. The
normal packages that succeeded are listed here:
http://www.3111skyline.com/dl/dt/tde/doc/bldlist-0713.txt
The 'used-to-build but now-ftbfs' packages were:
kchmviewer
kdmtheme
krusader
kima
The haven't been able to build yet failures were:
tqscintilla
tqscintilla-plugin
tdebindings
kbfx
kstreamripper
I'll try to look into the failures a little more tonight as well as get to
Darrell's list. I also note Arch has a new version of glibc (2.16-2) out
tonight. Progress only limited by the unavoidable delay in life called -- sleep!
--
David C. Rankin, J.D.,P.E.
Tim, Darrell,
This is probably arch, but I've hit a new tdebase failure regarding rpcgen:
[ 49%] Building CXX object kioslave/man/CMakeFiles/kio_man-module.dir/kio_man.cpp.o
Linking CXX shared module kio_man.so
[ 49%] Built target kio_man-module
[ 49%] Generating kmanpart.moc
Scanning dependencies of target libkmanpart-module
[ 49%] Building CXX object
kioslave/man/CMakeFiles/libkmanpart-module.dir/kmanpart.cpp.o
Linking CXX shared module libkmanpart.so
[ 49%] Built target libkmanpart-module
[ 49%] Generating nfs_prot_xdr.c
cannot find any C preprocessor (cpp)
rpcgen: C preprocessor failed with exit code 1
make[2]: *** [kioslave/nfs/nfs_prot_xdr.c] Error 1
make[1]: *** [kioslave/nfs/CMakeFiles/kio_nfs-module.dir/all] Error 2
make: *** [all] Error 2
Googling, this looks like it is due to some hardcoded path somewhere in tde. I
do not know what changed with the latest gcc update, but it looks like we need
to add preprocessor directives to the code to handle this change. I'll provide
patch update information later on this week.
--
David C. Rankin, J.D.,P.E.
hidey-ho neighbors!
HDAPS is a hard drive monitoring system created by IBM for thinkpad laptops
to protect them in case of dropping/falling/whatever. There was a KDE3
applet called khdapsapplet [0] which would show the status of the system. I
think this is a good candidate for inclusion/porting to trinity. Trinity
seeks to be a desktop environment for serious users and enterprise
environments, and thinkpad also targets that very market. This is a utility
that could be employed by those users who use thinkpads and trinity desktop
(which is a very logical combination).
I would be willing to do the work on this to possibly get it included in
R14 or later. I will be busy all summer however.
What do you guys think?
Calvin
[0] http://kde-apps.org/content/show.php/khdapsmonitor?content=41710
Tim, All,
Just a general heads up. automake 1.12 removes support for AM_C_PROTOTYPES.
We will need to grep the GIT tree to see if this impacts TDE. If the code
still relies on AM_C_PROTOTYPES, then any automake build will fail with:
configure.in:22: error: automatic de-ANSI-fication support has been removed
/usr/share/aclocal-1.12/protos.m4:12: AM_C_PROTOTYPES is expanded from...
configure.in:22: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
The solution is simple, just delete the AM_C_PROTOTYPES reference. I
haven't had time to check yet, but I thought I would pass it along.
--
David C. Rankin, J.D.,P.E.
Hey,
our development page [0] is no longer correct. It says "patches from SVN"
it should say "patches from GIT".
Calvin
[0] http://trinitydesktop.org/development.php
Tim,
Qupzilla is a light weight web browser written in C++ using Qt4. Is this the type of app that should build on Trinity using the TQt3 interface layer?
http://www.qupzilla.com/
Darrell
We have in the sources a shell script that updates a user's profile configuration files to be compatible with the recent R14 XDG changes. The script is installed to $TDEDIR/bin/r14-xdg-update.
The script is called once from starttde and thereafter is not run again from starttde. The wcript can be run manually at any time by passing the "force" parameter at the command line.
If you look at the script you will see some "TODO" comments. There probably are other TODO items that I have not considered.
This script does a good job against its original intent but needs further testing. No user in this team uses Trinity in the exact same way. Therefore robust testing and improvements to the script are needed to cover unforseen corner cases.
We need to find bugs and oversights before we move into release candidate status for R14.0.0.
Please remember the script is only for R14 and cannot be tested in with 3.5.13 or 3.5.13.1. Using the script in those releases will break the user's profile. Testing the script can be performed only with R14.
Thanks much!
Darrell