All,
tdmtheme is failing at the beginning of make with:
make[2]: Entering directory `/build/src/kdmtheme/src' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c -o tdmtheme.lo tdmtheme.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c tdmtheme.cpp -fPIC -DPIC -o .libs/tdmtheme.o tdmtheme.cpp:344:24: fatal error: tdmtheme.moc: No such file or directory compilation terminated.
What is supposed to generate tdmtheme.moc and where is it supposed to be located once it is generated properly?
On 07/15/2012 01:01 AM, David C. Rankin wrote:
All,
tdmtheme is failing at the beginning of make with:
make[2]: Entering directory `/build/src/kdmtheme/src' /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c -o tdmtheme.lo tdmtheme.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c tdmtheme.cpp -fPIC -DPIC -o .libs/tdmtheme.o tdmtheme.cpp:344:24: fatal error: tdmtheme.moc: No such file or directory compilation terminated.
What is supposed to generate tdmtheme.moc and where is it supposed to be located once it is generated properly?
If you look at the error above (it took me a while to clue in), the package being built is kdmtheme from the applications/kdmtheme source, but for some reason the build is looking for 'tdmtheme.com' and isn't going to find it because this is 'kdmtheme'...
It looks like a kdm->tdm sed went awry... Where/how to fix??
If you look at the error above (it took me a while to clue in), the package being built is kdmtheme from the applications/kdmtheme source, but for some reason the build is looking for 'tdmtheme.com' and isn't going to find it because this is 'kdmtheme'...
It looks like a kdm->tdm sed went awry... Where/how to fix??
I am able to build the package here. What should the package contents be, just in case I'm not building correctly?
In /opt/trinity/lib I see kcm_tdmtheme.so and kcm_tdmtheme.la. I see a desktop file in /opt/trinity/share/applications/tde. And an index.cache.bz2 and docbook file.
Darrell
On 07/20/2012 04:09 PM, Darrell Anderson wrote:
I am able to build the package here. What should the package contents be, just in case I'm not building correctly?
In /opt/trinity/lib I see kcm_tdmtheme.so and kcm_tdmtheme.la. I see a desktop file in /opt/trinity/share/applications/tde. And an index.cache.bz2 and docbook file.
Darrell
It is a kcontrol entry to configure kdmtheme. Handy! If I'm thinking correctly, it should provide 'System Adminstration -> KDM Theme Manager'
Why are you not getting a tdmtheme.moc failure??
I can't fake that and I can't do anything in the build script to mess it up either??
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c -o tdmtheme.lo tdmtheme.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c tdmtheme.cpp -fPIC -DPIC -o .libs/tdmtheme.o tdmtheme.cpp:344:24: fatal error: tdmtheme.moc: No such file or directory
It is a kcontrol entry to configure kdmtheme. Handy! If I'm thinking correctly, it should provide 'System Adminstration -> KDM Theme Manager'
Yes, but what should the contents of a properly built package contain?
Why are you not getting a tdmtheme.moc failure??
I don't know and I looked behind the curtain too. :-) Possibly because glibc 2.15 installed rather than 2.16?
Darrell
On 07/20/2012 04:45 PM, Darrell Anderson wrote:
Yes, but what should the contents of a properly built package contain?
Now you are asking trick questions... Short answer - I'll have to look. If it is a properly installed package, then you should see this in kcontol:
http://www.3111skyline.com/dl/dt/trinity/ss/kdm_theme.jpg
Why are you not getting a tdmtheme.moc failure??
I don't know and I looked behind the curtain too. :-) Possibly because glibc 2.15 installed rather than 2.16?
Yes, damn, that bothers me. Why in the heck would a glibc update cause things to break (wait... don't answer that...), meaning the SOB should be backwards compatible unless it follows the same vein as gcc and tightened the syntax/semantics a bit more. I have an email out on the Arch list as well regarding build failures with the new glibc and whether the type I'm seeing are expected.
It is a kcontrol entry to configure kdmtheme. Handy! If I'm thinking correctly, it should provide 'System Adminstration -> KDM Theme Manager'
I installed the package and everything works, but not until I edited the tdmrc file.
I suspect the problem is here:
[X-*-Core] AllowNullPasswd=false AllowRootLogin=true AllowShutdown=Root AutoReLogin=false ClientLogFile=.xsession-errors-%s Reset=/etc/trinity/tdm/Xreset Session=/etc/trinity/tdm/Xsession Setup=/etc/trinity/tdm/Xsetup Startup=/etc/trinity/tdm/Xstartup
The default tdmrc had file paths of /opt/trinity/share/config/tdm. After I changed them to the way my system works, then the tdmtheme module worked correctly.
Change those four paths to where your tdm config files are installed.
Darrell
On 07/20/2012 05:26 PM, Darrell Anderson wrote:
Change those four paths to where your tdm config files are installed.
Those will be user and distro specific in most cases. Suse, Arch and most others I know have put /opt package config files with the installs in /opt. All of my themes go in /opt/trinity/share/apps/tdm/themes and the tdm related configs go in /opt/trinity/share/config/tdm.
I hope they are not hard coded in the code or we might just have found out why my tdm login for o2_enterprise, etc.. just quit working. Did you change the path information in the GIT tree??
Those will be user and distro specific in most cases. Suse, Arch and most others I know have put /opt package config files with the installs in /opt. All of my themes go in /opt/trinity/share/apps/tdm/themes and the tdm related configs go in /opt/trinity/share/config/tdm.
Same here, although the Slackware tradition is to create a sym link to /etc/trinity/tdm. On reflection, I don't know why changing those four keys made a difference. At the moment I think something else was the cause of the failure. I'll have to find another copy and test more methodically.
I hope they are not hard coded in the code or we might just have found out why my tdm login for o2_enterprise, etc.. just quit working. Did you change the path information in the GIT tree??
No, only the active copy on my system. The only comment I can offer with certainty is themes did not work until after I grabbed an older copy of tdmrc and replaced the new copy.
From what I understand browsing through the code, the file paths are not fully hard-coded. They are defined like this:
{ "X-*-Core", "Setup", "%s/tdm/Xsetup", 0 }, { "X-*-Core", "Startup", "%s/tdm/Xstartup", 0 }, { "X-*-Core", "Reset", "%s/tdm/Xreset", 0 }, { "X-*-Core", "Session", "%s/tdm/Xsession", 0 },
The tdmrc file needs to be generated during the build process and does not exist anywhere until generated using the gentdmconf command. There are several parameters that can be used. One of which is "--no-old" which then ignores xdm configurations. The traditional way of generating the tdmrc file in the Slackware build script:
$PKG${PREFIX}/bin/gentdmconf --no-old --no-old-scripts --no-backup --in $PKG/etc/trinity/tdm
Darrell
On 07/21/2012 10:36 AM, Darrell Anderson wrote:
No, only the active copy on my system. The only comment I can offer with certainty is themes did not work until after I grabbed an older copy of tdmrc and replaced the new copy.
From what I understand browsing through the code, the file paths are not fully hard-coded. They are defined like this:
{ "X-*-Core", "Setup", "%s/tdm/Xsetup", 0 }, { "X-*-Core", "Startup", "%s/tdm/Xstartup", 0 }, { "X-*-Core", "Reset", "%s/tdm/Xreset", 0 }, { "X-*-Core", "Session", "%s/tdm/Xsession", 0 },
This is working correctly. I get the correct path information in tdmrc. I've been through it with a fine-toothed comb (line by bloody line) and tdmrc isn't doing anything that would prevent the chooser dialog from displaying. I'll double check, but I have even replace the first tdmrc with another and it still isn't doing what it should. I've looked, but will look again at the enterprise.xml file. I don't think that is suspect, because you look at the
The tdmrc file needs to be generated during the build process and does not exist anywhere until generated using the gentdmconf command. There are several parameters that can be used. One of which is "--no-old" which then ignores xdm configurations. The traditional way of generating the tdmrc file in the Slackware build script:
$PKG${PREFIX}/bin/gentdmconf --no-old --no-old-scripts --no-backup --in $PKG/etc/trinity/tdm
What I'm thinking is there is something in kcontrol -> System Administration -> Login Manager that is conflicting with the theme set in tdmrc?? (that's my next theory)
On 07/21/2012 07:11 PM, David C. Rankin wrote:
What I'm thinking is there is something in kcontrol -> System Administration -> Login Manager that is conflicting with the theme set in tdmrc?? (that's my next theory)
Next major observation. The XDG login is a _WINDOW_ not a graphic. I can grab the titlebar for the greeter and move it around the tdm login screen. I have also noticed that the logout "End Current Session" graphic is also in a _WINDOW_ and not the normal graphic I'm used to seeing.
So whatever is going on, it isn't displaying the 'graphic' files on greeter display and logout -- it is just giving a default _window_. There is some name somewhere that either has a 'k' where it should have a 't' or a 't' where it should have a 'k'.
Where is anything related to login/logout logged by the system? Not in .xsession-errors, I've looked. Any ideas?
On 07/20/2012 04:20 PM, David C. Rankin wrote:
On 07/20/2012 04:09 PM, Darrell Anderson wrote:
I am able to build the package here. What should the package contents be, just in case I'm not building correctly?
In /opt/trinity/lib I see kcm_tdmtheme.so and kcm_tdmtheme.la. I see a desktop file in /opt/trinity/share/applications/tde. And an index.cache.bz2 and docbook file.
Darrell
It is a kcontrol entry to configure kdmtheme. Handy! If I'm thinking correctly, it should provide 'System Adminstration -> KDM Theme Manager'
Why are you not getting a tdmtheme.moc failure??
I can't fake that and I can't do anything in the build script to mess it up either??
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c -o tdmtheme.lo tdmtheme.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I. -include tqt.h -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g3 -fno-inline -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -I/usr/include/tqt -MT tdmtheme.lo -MD -MP -MF .deps/tdmtheme.Tpo -c tdmtheme.cpp -fPIC -DPIC -o .libs/tdmtheme.o tdmtheme.cpp:344:24: fatal error: tdmtheme.moc: No such file or directory
The error is correct, there is no tdmtheme.moc generated:
16:34 supersff:~/bld/david/build/src/kdmtheme/src> l total 88 drwxr-xr-x 4 nobody nobody 4096 Jul 20 16:22 . drwxr-xr-x 8 nobody nobody 4096 Jul 20 16:22 .. drwxr-xr-x 2 nobody nobody 4096 Jul 20 16:22 .deps drwxr-xr-x 2 nobody nobody 4096 Jul 20 16:22 .libs -rw-r--r-- 1 nobody nobody 24197 Jul 20 16:22 Makefile -rw-r--r-- 1 nobody nobody 419 Feb 8 17:58 Makefile.am -rw-r--r-- 1 nobody nobody 23640 Jul 20 16:22 Makefile.in -rw-r--r-- 1 nobody nobody 11730 Feb 8 17:58 tdmtheme.cpp -rw-r--r-- 1 nobody nobody 928 Jun 8 19:08 tdmtheme.desktop -rw-r--r-- 1 nobody nobody 2402 Mar 11 12:14 tdmtheme.h
What triggers it's generation?
-
Darrell Anderson -
David C. Rankin