[oe] Problem building dbus-glib-0.72

Andrew Paulsen andrew.paulsen at gmail.com
Fri Nov 17 14:47:19 UTC 2006


I'm getting some errors building gpe-image, specifically on the
dbus-glib-0.72 package, that seem to be related to include path
problems.

My local.conf has these settings:
MACHINE = "compulab-pxa270"
DISTRO = "familiar-unstable"

And the log leading up to the error is:
NOTE: package dbus-glib-0.72: started
NOTE: package dbus-glib-0.72-r0: task do_compile: started
NOTE: SITE files
/home/packet/OpenEmbedded/org.openembedded.dev/site/endian-little
/home/packet/OpenEmbedded/org.openembedded.dev/site/arm-linux
ERROR: function do_compile failed
ERROR: log data follows
(/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/temp/log.do_compile.7567)
| NOTE: make
| make  all-recursive
| make[1]: Entering directory
`/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72'
| Making all in dbus
| make[2]: Entering directory
`/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72/dbus'
| make  all-recursive
| make[3]: Entering directory
`/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72/dbus'
| Making all in .
| make[4]: Entering directory
`/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72/dbus'
| if /bin/sh ../arm-linux-libtool --tag=CC --mode=compile
arm-linux-gcc -march=armv5te -mtune=xscale -DHAVE_CONFIG_H -I.
-I/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72/dbus
-I.. -I/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72
-I..  -I/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include/glib-2.0
-I/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/lib/glib-2.0/include
   -DDBUS_COMPILATION=1 -DDBUS_LOCALEDIR=\"/usr/share/locale\"
-DDBUS_API_SUBJECT_TO_CHANGE=1
-isystem/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include
-isystem/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2
-Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
-Wsign-compare -MT dbus-glib.lo -MD -MP -MF ".deps/dbus-glib.Tpo" -c
-o dbus-glib.lo dbus-glib.c; \
|       then mv -f ".deps/dbus-glib.Tpo" ".deps/dbus-glib.Plo"; else
rm -f ".deps/dbus-glib.Tpo"; exit 1; fi
|  arm-linux-gcc -march=armv5te -mtune=xscale -DHAVE_CONFIG_H -I.
-I/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72/dbus
-I.. -I/home/packet/OpenEmbedded/build/tmp/work/armv5te-linux/dbus-glib-0.72-r0/dbus-glib-0.72
-I.. -I/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include/glib-2.0
-I/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/lib/glib-2.0/include
-DDBUS_COMPILATION=1 -DDBUS_LOCALEDIR=\"/usr/share/locale\"
-DDBUS_API_SUBJECT_TO_CHANGE=1
-isystem/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include
-isystem/home/packet/OpenEmbedded/build/tmp/staging/arm-linux/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2
-Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal
-Wsign-compare -MT dbus-glib.lo -MD -MP -MF .deps/dbus-glib.Tpo -c
dbus-glib.c  -fPIC -DPIC -o .libs/dbus-glib.o
| In file included from dbus-glib.c:25:
| dbus-glib.h:28:30: dbus/dbus-shared.h: No such file or directory

<...and a bunch more of these...>


Sure enough, the missing files aren't in the -I paths:
packet at linuxdev0:~/OpenEmbedded/build/$ find tmp -name dbus-shared.h
tmp/work/i686-linux/dbus-native-0.94-r0/dbus-0.94/dbus/dbus-shared.h
tmp/work/armv5te-linux/dbus-0.92-r1/dbus-0.92/dbus/dbus-shared.h
tmp/work/armv5te-linux/dbus-0.92-r1/install/dbus-dev/usr/include/dbus-1.0/dbus/dbus-shared.h
tmp/staging/i686-linux/include/dbus-1.0/dbus/dbus-shared.h
tmp/staging/arm-linux/include/dbus-1.0/dbus/dbus-shared.h


I'm new to this so I would really appreciate some guidance.




More information about the Openembedded-devel mailing list