What caveats should I know with downgrading autoconf/automake?
The port to cmake is a wise long-term strategy but will take time. While svn remains in a mixed autotools and cmake environment, both sets of build tools are needed during the transition.
As I am already two releases behind, I was thinking about moving to the next release of Slackware, which is now in RC status. That move also will allow me to test Trinity in an environment with KDE4 installed.
That upcoming Slackware release comes with autoconf-2.68 and automake-1.11.1.
As explained to me, I cannot build KDE 3.5.10 or Trinity with that version of those tools.
I was thinking about updating to the new Slackware release and then temporarily downgrading to autoconf-2.63 and automake-1.10.1 so I can build and help test Trinity during the long-term port to cmake.
I presume that if I want to build third-party packages for the new Slackware release, I might have to toggle to autoconf-2.68 and automake-1.11.1 to ensure no compatibility problems.
Perhaps I need only downgrade autoconf and not automake. I have no clue if that is possible too.
Will this work?
Darrell
Hi Serghei,
In kdebase, kdebase/kioslave/media/propsdlgplugin does not have a CMake
control file. Could you create one? This is currently holding up
Debian/Ubuntu builds of kdebase.
Thanks!
Tim
Guys,
I can't explain this one. On i686, kpowersave built fine, but on x86_64, the
build fails due to:
CMake Error at cmake/modules/TDEMacros.cmake:20 (message):
#################################################
xscrnsaver are required, but not found on your system
#################################################
Call Stack (most recent call first):
ConfigureChecks.cmake:42 (tde_message_fatal)
CMakeLists.txt:40 (include)
-- Configuring incomplete, errors occurred!
In ConfigureChecks.cmake, we have:
# check for xscrnsaver
pkg_search_module( XSCRNSAVER xscrnsaver )
if( NOT XSCRNSAVER_FOUND )
tde_message_fatal( "xscrnsaver are required, but not found on your system" )
endif()
On Arch the package is actually xscreensaver. On both i686 and x86_64 boxes,
I have 'xscreensaver 5.12-2' installed, but for some reason, this works on i686.
Dunno why...
Where can I look at the actual code for "pkg_search_module()" so I can tell
exactly what it is looking for? It almost seems like I've run into this before,
but can't recall for the life of me what I did to address it?
There must be some other package on the box that works that provides the
dependency that kpowersave is looking for, but how do I figure that out? What
say the experts?
--
David C. Rankin, J.D.,P.E.
We install them with regular packages, since arch users almost always are compiling, developing etc we just include them. While it takes more space it saves alot of work. Sorry for the top post
Calvin Morrison
Kristopher Gamrat <pikidalto(a)gmail.com> wrote:
>On Sun, Mar 13, 2011 at 7:33 AM, calvin morrison <mutantturkey(a)gmail.com> wrote:
>> On 12 March 2011 23:57, Kristopher Gamrat <pikidalto(a)gmail.com> wrote:
>>>
>>> Normally it is forgetting to install the devel package. Or it may be
>>> looking for the 32bit version of xscreensaver, which means it would
>>> need adjusted to check for 64bit. You probably know this, but 64bit
>>> libs tend to go into lib64 instead of lib, so that might be where it
>>> fails because some stuff have it hardcoded to assume 32bit libs. Of
>>> course, I couldn't understand the code very well, so I couldn't tell
>>> you for sure.
>>>
>>> --
>>> Kris
>>> "Piki"
>>> Ark Linux Webmaster
>>> Trinity Desktop Environment Packager
>>
>> All of those assumptions here are wrong for arch :) we don't have
>> devel packages and we don't have a lib64
>
>I haven't seen a distro not have lib64, but I haven't used Arch either
>(except for the time when I tried it and couldn't find something like
>dhclient or dhcpcd to get online, didn't have 64bit then). I also
>haven't seen a distro without dev or devel packages either -- unless
>you guys are installing the devel headers with the main packages (not
>necessary for people who aren't compiling software), I'd think you
>have to put them somewhere?
>
>--
>Kris
>"Piki"
>Ark Linux Webmaster
>Trinity Desktop Environment Packager
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
>For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
>Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
>Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
Tim, Serghei,
I found another constructor problem in kpowersave. Here is a patch:
--- kpowersave/src/inactivity.cpp
+++ kpowersave/src/inactivity.cpp 2011-03-12 18:40:52.000000000 -0600
@@ -325,7 +325,7 @@
blacklisted_running = false;
}
else {
- if (pids.contains(QRegExp::QRegExp("[0-9]"))) {
+ if (pids.contains(QRegExp("[0-9]"))) {
kdDebug() << "BLACKLISTED IS RUNNING" << endl;
blacklisted_running = true;
blacklisted_running_last = idleTime;
Builds fine afterwards:
trinity-app-kpowersave-1215405-1-i686.pkg.tar.xz
--
David C. Rankin, J.D.,P.E.
Serghei,
I almost have kdelibs built, but from what I can tell the common/ symbolic
link in the documentation directories is not being created.
As one example, a symbolic link would normally be present in
/opt/trinity/share/doc/kde/HTML/en/kspell/common, pointing to the
/opt/trinity/share/doc/kde/HTML/en/common directory. This is so that the
KHTML-based documentation renderer can find the needed graphics and style
files.
I would try to fix this myself, but I lack the requisite CMake knowledge
to do it correctly.
Thanks!
Tim
I am currently packaging TDE for use on Arch Linux
I am getting the following errors in kdelibs
QSettings: error creating /.qt
QSettings: error creating /.qt
QSettings: error creating /.qt
QSettings: error creating /.qt
QSettings: error creating /.qt
QSettings::sync: filename is null/empty
QSettings: error creating /.qt
QSettings::sync: filename is null/empty
QSettings: error creating /.qt
QSettings::sync: filename is null/empty
Anyone know what causes these and are they benign?
I have built the svn source to kdevelop and the resulting binaries
produce a system that generally works.
I have installed TDE based on the svn source and it mostly works.
I am using TDE svn as the primary desktop on my laptop.
I have a problem with kdm - it runs but you can not login to a valid
user. It tries to run the desktop then goes back to the login.
If anyone has any pointers on how to fix it I am all ears.
The only thing on my wish list to get ported is Ark, K3b and kpdf.
Thanks for all your effort I am looking forward to the completed TDE, I
know it will be a lot of effort.
I would help in the port but I don't know cmake and by the time I would
get up to speed you guys would be done ;)