21 Feb
2012
21 Feb
'12
6:12 a.m.
*-DWITH_HAL option defaults to OFF. I set that option to ON and I think
then the problems disappeared.*
Nailed it! Thanks so much Darrell .... it would have taken me an age to
find this. Do you use this for all packages?
Jay
On Mon, Feb 20, 2012 at 10:22 PM, Jay <jayflood(a)gmail.com> wrote:
Thanks. I am not using the CPLUS_INCLUDE_PATH
variable. I checked the
CmakeCache.txt file and there is indeed the given paths:
DBUS_INCLUDEDIR:INTERNAL=/usr/include
DBUS_INCLUDE_DIRS:INTERNAL=/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
Changing the include path in consolekit.h got me one step further (as
expected) and the next header in the same path was missed.
I will try with -DWITH_HAL=ON and then try adding one level deeper (where
the header lives) to the CMakeCache.txt: DBUS_INCLUDE_DIRS:INTERNAL=*
/usr/include/dbus-1.0/dbus*;/usr/lib/dbus-1.0/include
CMakesMyHeadAche
Jay
On Mon, Feb 20, 2012 at 10:04 PM, Darrell Anderson <
humanreadable(a)yahoo.com> wrote:
While
compiling from latest git (20th Feb
2012) i got as far as tdebase. At around the 90% mark it
failed.
git/tde/main/tdebase/tdm/backend/consolekit.c:31:23:
fatal error: dbus/dbus.h: No such file or directory
compilation terminated.
consolekit.c contains the following include:
#include <dbus/dbus.h>
when the actual headers path is
/usr/include/dbus-1.0/dbus/dbus.h
Rebuilding now with a symlink to see how far i get.
I recall running into that problem a while back. I don't remember what
caused the problem. That might have been when I discovered the -DWITH_HAL
option defaults to OFF. I set that option to ON and I think then the
problems disappeared.
The cmake configuration files should automatically detect the dbus-1.0
files. In the tdebase build directory, check the CMakeCache.txt file for
lines like this:
DBUS_CFLAGS:INTERNAL=-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
DBUS_INCLUDE_DIRS:INTERNAL=/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
DBUS_STATIC_CFLAGS:INTERNAL=-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
DBUS_STATIC_INCLUDE_DIRS:INTERNAL=/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
DBUS_TQT_CFLAGS:INTERNAL=-I/opt/trinity/include;-I/opt/trinity/include/dbus-1.0;-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
DBUS_TQT_INCLUDE_DIRS:INTERNAL=/opt/trinity/include;/opt/trinity/include/dbus-1.0;/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
DBUS_TQT_STATIC_CFLAGS:INTERNAL=-I/opt/trinity/include;-I/opt/trinity/include/dbus-1.0;-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
DBUS_TQT_STATIC_INCLUDE_DIRS:INTERNAL=/opt/trinity/include;/opt/trinity/include/dbus-1.0;/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
HAL_CFLAGS:INTERNAL=-DDBUS_API_SUBJECT_TO_CHANGE;-I/usr/include/hal;-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
HAL_INCLUDE_DIRS:INTERNAL=/usr/include/hal;/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
HAL_STATIC_CFLAGS:INTERNAL=-DDBUS_API_SUBJECT_TO_CHANGE;-I/usr/include/hal;-I/usr/include/dbus-1.0;-I/usr/lib/dbus-1.0/include
HAL_STATIC_INCLUDE_DIRS:INTERNAL=/usr/include/hal;/usr/include/dbus-1.0;/usr/lib/dbus-1.0/include
Also, FWIW, by any chance are you setting the CPLUS_INCLUDE_PATH
environment variable? I had all kinds of weird build problems using that
variable, which is some kind of oddball carry over in Slackware build
scripts from days long past.
Oh, I just built everything today in Slackware 13.1 against Qt3. So the
package does build. :)
Darrell
---------------------------------------------------------------------
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 messages on the web archive:
http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting