OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Failed To Build 3.5.4.1 2.4 For Collie, Is this a bug?
DoTheDog
post Sep 13 2006, 07:45 PM
Post #1





Group: Members
Posts: 92
Joined: 9-August 05
Member No.: 7,823



Hi,
I am trying to build a gpe-image for collie kernel 3.5.4.1 however, it always pukes on checking for GCONF_DBUS. Is this a bug or a problem with my config? d-bus was built earlier in the image compile. Here is the error:
clip
| checking whether the ccache arm-linux-g77 -march=armv4 -mtune=xscale linker (arm-linux-ld) supports shared libraries... yes
| checking dynamic linker characteristics... GNU/Linux ld.so
| checking how to hardcode library paths into programs... immediate
| checking whether stripping libraries is possible... yes
| FYI: Using default config source xml::${sysconfdir}/gconf/gconf.xml.defaults for schema installation
| FYI: Will build with debug checks but no debug spew
| checking for gtkdoc-mkdb... false
| checking for db2html... true
| checking for GCONF_DBUS... configure: error: You need either ORBit or D-BUS for IPC
| FATAL: oe_runconf failed
NOTE: Task failed: /media/usbdisk/collie/bitbake-1.4/tmp/work/gconf-dbus-0.0cvs20060102-r9/temp/log.do_configure.14955
NOTE: package gconf-dbus-0.0cvs20060102-r9: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package gconf-dbus-0.0cvs20060102: failed
ERROR: Build of gpe-image failed
/clip

Should I submit a bug report? or is this some problem with my environment?

DoTheDog
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
lardman
post Sep 15 2006, 07:34 AM
Post #2





Group: Members
Posts: 4,515
Joined: 25-October 03
From: Bath, UK
Member No.: 464



hrw tells me that is should be:

MACHINE_KERNEL_VERSION rather than KERNEL_VERSION


Si
Go to the top of the page
 
+Quote Post
DoTheDog
post Sep 16 2006, 06:10 AM
Post #3





Group: Members
Posts: 92
Joined: 9-August 05
Member No.: 7,823



lardman,
Thanks for the reply.

QUOTE(lardman @ Sep 15 2006, 09:34 AM)
hrw tells me that is should be:
MACHINE_KERNEL_VERSION rather than KERNEL_VERSION


Here is what I tried:

I changed my local.conf to:
CODE
MACHINE_KERNEL_VERSION = "2.4"


I also changed /org.openembedded.oz354x/conf/machine/collie.conf
to say:
CODE
MACHINE_KERNEL_VERSION ?= "2.4"


It did build the following in the tmp/work dir:
collie-kernel-24-8-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-32-0-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-32-32-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-40-24-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-48-16-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-58-6-2.4.18-rmk7-pxa3-embedix-r23
collie-kernel-64-0-2.4.18-rmk7-pxa3-embedix-r23
collie-kernels-2.4-embedix-1.0-r2

I am assuming that is good.

It is also building:
gcc-cross-3.4.4-r4
gcc-cross-initial-3.4.4-r4

Should it be doing that?

The gpe-image build is now failing building bluez-utils-dbus-2.25-r1
error below:
CODE
<clip>
| if ccache arm-linux-gcc -march=armv4 -mtune=xscale -DHAVE_CONFIG_H -I. -I/media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/bluez-utils-2.25/hcid -I.. -I/media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/bluez-utils-2.25/common  -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include/dbus-1.0 -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib/dbus-1.0/include   -DDBUS_API_SUBJECT_TO_CHANGE -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include/dbus-1.0 -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib/dbus-1.0/include   -DDBUS_API_SUBJECT_TO_CHANGE -DENABLE_DBUS -DDBUS_API_SUBJECT_TO_CHANGE -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include -fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2 -D_FORTIFY_SOURCE=2 -MT dbus.o -MD -MP -MF ".deps/dbus.Tpo" -c -o dbus.o dbus.c; \
| then mv -f ".deps/dbus.Tpo" ".deps/dbus.Po"; else rm -f ".deps/dbus.Tpo"; exit 1; fi
| dbus.c:287: error: `DBUS_TYPE_INVALID_AS_STRING' undeclared here (not in a function)
| dbus.c:287: error: initializer element is not constant
| dbus.c:287: error: (near initialization for `device_services[0].signature')
| dbus.c:287: error: initializer element is not constant
| dbus.c:287: error: (near initialization for `device_services[0]')
| dbus.c:288: error: initializer element is not constant
</clip>

There are a whole bunch of dbus.c errors then:
CODE
<clip>
| dbus.c:1772: error: parse error before "DBUS_TYPE_UINT16_AS_STRING"
| dbus.c:1811: error: `DBUS_TYPE_STRUCT' undeclared (first use in this function)
| dbus.c:1812: error: `DBUS_TYPE_UINT16' undeclared (first use in this function)
| dbus.c: In function `handle_device_list_req':
| dbus.c:2450: error: `DBUS_STRUCT_BEGIN_CHAR_AS_STRING' undeclared (first use in this function)
| dbus.c:2450: error: parse error before "DBUS_TYPE_STRING_AS_STRING"
| dbus.c:2510: error: `DBUS_TYPE_STRUCT' undeclared (first use in this function)
| make[2]: *** [dbus.o] Error 1
| make[2]: Leaving directory `/media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/bluez-utils-2.25/hcid'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/bluez-utils-2.25'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/temp/log.do_compile.8398
NOTE: package bluez-utils-dbus-2.25-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package bluez-utils-dbus-2.25: failed
ERROR: Build of gpe-image failed
</clip>

My guess is that it is trying to use gcc-3.4.4. I found this in the log:
CODE
ccache arm-linux-gcc -march=armv4 -mtune=xscale -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include/dbus-1.0 -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib/dbus-1.0/include -DDBUS_API_SUBJECT_TO_CHANGE -I/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/include -fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2 -D_FORTIFY_SOURCE=2 -Wl,-rpath-link -Wl,/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib -Wl,-O1 -o .libs/bluetoothd main.o  -L/media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib /media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib/libdbus-1.so -lnsl -L/usr/lib /media/usbdisk/collie/bitbake-1.4/tmp/staging/arm-linux/lib/libbluetooth.so ../common/libtextfile.a
/media/usbdisk/collie/bitbake-1.4/tmp/cross/lib/gcc/arm-linux/3.4.4/../../../../arm-linux/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s
/media/usbdisk/collie/bitbake-1.4/tmp/cross/lib/gcc/arm-linux/3.4.4/../../../../arm-linux/bin/ld: skipping incompatible /usr/lib/libgcc_s.so when searching for -lgcc_s
creating bluetoothd
make[2]: Leaving directory `/media/usbdisk/collie/bitbake-1.4/tmp/work/bluez-utils-dbus-2.25-r1/bluez-utils-2.25/daemon'
Making all in tools

Any Ideas?

Another stupid question; how do you tell what gcc version bitbake is using to compile?

Rob
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 27th November 2014 - 05:33 PM