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

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> 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
Hrw
post Sep 14 2006, 11:29 AM
Post #2





Group: Members
Posts: 1,376
Joined: 11-January 04
From: Poznań, Poland
Member No.: 1,413



update metadata and build again
Go to the top of the page
 
+Quote Post
DoTheDog
post Sep 15 2006, 04:30 AM
Post #3





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



QUOTE(Hrw @ Sep 14 2006, 01:29 PM)
update metadata and build again
*


Hrw,
Thanks for the help. I updated (actually I rebuilt the environment) and I get a little farther. Now I have a problem in that it dies while building linux-openzaurus-2.6.17-r25. I am trying to build this for 2.4. I also noted it is building gcc-cross-3.4.4-r4 but I want it to use 2.95. I have downloaded and set up the 2.95 like this:

wget http://handhelds.org/download/projects/too...-2.95.3.tar.bz2.
mkdir -p /usr/local/arm
cp ~/media/usbdisk/collie/cross-2.95.3.tar.bz2 /usr/local/arm
cd /usr/local/arm
tar -xjf cross-2.95.3.tar.bz2
cd /usr/local/arm/2.95.3/bin
mv arm-linux-gcc arm-linux-gcc-2.95
mv arm-linux-ld arm-linux-ld-2.11.2
export PATH=/media/usbdisk/collie/bitbake/bin:/usr/local/arm/2.95.3/bin$PATH
export BBPATH=/media/usbdisk/collie/build:/media/usbdisk/collie/bitbake/tmp/org.openembedded.oz354x

In my local.conf I have:
ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95"
MACHINE = "collie"
TARGET_ARCH = "arm"
DISTRO = "openzaurus-3.5.4.1"
KERNEL_VERSION = "2.4"

Here is the error:
<clip>
| CC arch/arm/common/rtctime.o
| CC arch/arm/common/locomo.o
| arch/arm/common/locomo.c: In function `locomo_frontlight_set':
| arch/arm/common/locomo.c:1064: warning: passing arg 1 of `locomo_gpio_write' from incompatible pointer type
| arch/arm/common/locomo.c:1066: warning: passing arg 1 of `locomo_gpio_write' from incompatible pointer type
| CC arch/arm/common/sharpsl_param.o
| CC arch/arm/common/scoop.o
| LD arch/arm/common/built-in.o
| CC arch/arm/mach-sa1100/clock.o
| CC arch/arm/mach-sa1100/generic.o
| CC arch/arm/mach-sa1100/irq.o
| CC arch/arm/mach-sa1100/dma.o
| CC arch/arm/mach-sa1100/time.o
| CC arch/arm/mach-sa1100/collie.o
| arch/arm/mach-sa1100/collie.c: In function `collie_uart_set_mctrl':
| arch/arm/mach-sa1100/collie.c:99: error: `uart_dev' undeclared (first use in this function)
| arch/arm/mach-sa1100/collie.c:99: error: (Each undeclared identifier is reported only once
| arch/arm/mach-sa1100/collie.c:99: error: for each function it appears in.)
| arch/arm/mach-sa1100/collie.c:102: error: invalid type argument of `->'
| arch/arm/mach-sa1100/collie.c:104: error: invalid type argument of `->'
| arch/arm/mach-sa1100/collie.c:107: error: invalid type argument of `->'
| arch/arm/mach-sa1100/collie.c:109: error: invalid type argument of `->'
| arch/arm/mach-sa1100/collie.c: In function `collie_uart_get_mctrl':
| arch/arm/mach-sa1100/collie.c:116: error: `uart_dev' undeclared (first use in this function)
| arch/arm/mach-sa1100/collie.c:118: error: invalid type argument of `->'
| arch/arm/mach-sa1100/collie.c: In function `collie_uart_probe':
| arch/arm/mach-sa1100/collie.c:134: error: `uart_dev' undeclared (first use in this function)
| arch/arm/mach-sa1100/collie.c: In function `collie_uart_remove':
| arch/arm/mach-sa1100/collie.c:140: error: `uart_dev' undeclared (first use in this function)
| make[1]: *** [arch/arm/mach-sa1100/collie.o] Error 1
| make: *** [arch/arm/mach-sa1100] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /media/usbdisk/collie/bitbake-1.4/tmp/work/linux-openzaurus-2.6.17-r25/temp/log.do_compile.17407
NOTE: package linux-openzaurus-2.6.17-r25: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package linux-openzaurus-2.6.17: failed
ERROR: Build of gpe-image failed
</clip>

What am I doing wrong?

Rob
Go to the top of the page
 
+Quote Post
lardman
post Sep 15 2006, 07:30 AM
Post #4





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



QUOTE
dies while building linux-openzaurus-2.6.17-r25


QUOTE
I am trying to build this for 2.4.


QUOTE
I also noted it is building gcc-cross-3.4.4-r4 but I want it to use 2.95.


3.xx is correct for the 2.6.x kernels, and it's trying to build a 2.6.x kernel atm.

It would appear it's not building the one you want.


QUOTE
In my local.conf I have:
ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95"
MACHINE = "collie"
TARGET_ARCH = "arm"
DISTRO = "openzaurus-3.5.4.1"
KERNEL_VERSION = "2.4"


I didn't think that KERNEL_VERSION is valid for the Collie, however I'm not sure as I've not been using bitbake for a while (holiday) so this may have changed.

I'll ask hrw.


Si
Go to the top of the page
 
+Quote Post
lardman
post Sep 15 2006, 07:34 AM
Post #5





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 #6





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
Hrw
post Sep 16 2006, 09:55 AM
Post #7





Group: Members
Posts: 1,376
Joined: 11-January 04
From: Poznań, Poland
Member No.: 1,413



2.4/2.6 switch was needed for you because .oz354x is now used to build 3.5.4.2-rc rather then 3.5.4.1. This switch was ok.
dbus error is something which I try to resolve now.
Go to the top of the page
 
+Quote Post
DoTheDog
post Sep 16 2006, 01:39 PM
Post #8





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



Hrw,

QUOTE(Hrw @ Sep 16 2006, 11:55 AM)
2.4/2.6 switch was needed for you because .oz354x is now used to build 3.5.4.2-rc rather then 3.5.4.1. This switch was ok.
dbus error is something which I try to resolve now.
*


Thank you for helping on this. I am actually trying to build this for a couple of other people, just trying to help out.

Rob
Go to the top of the page
 
+Quote Post
Hrw
post Sep 17 2006, 07:32 AM
Post #9





Group: Members
Posts: 1,376
Joined: 11-January 04
From: Poznań, Poland
Member No.: 1,413



1. set MACHINE_KERNEL_VERSION = "2.4" in conf/local.conf
2. update metadata
3. build

I just finished building of bootstrap/gpe/opie images for OZ 3.5.4.1 for collie with 2.4.18-crapix kernel. It took 3 days (my machine is not fastest one).
Go to the top of the page
 
+Quote Post
miskinis
post Sep 17 2006, 05:07 PM
Post #10





Group: Members
Posts: 333
Joined: 8-January 05
From: North East, USA Today
Member No.: 6,159



QUOTE(Hrw @ Sep 17 2006, 11:32 AM)
1. set MACHINE_KERNEL_VERSION = "2.4" in conf/local.conf
2. update metadata
3. build

I just finished building of bootstrap/gpe/opie images for OZ 3.5.4.1 for collie with 2.4.18-crapix kernel. It took 3 days (my machine is not fastest one).
*


Wow, I'd love to know how fast your machine is... I have been contemplating setting
up a kernel building environment for the Z, SL-5500 to start with. I remember seeing
the "right arrow held down continously causes suspend" issue fixed in an OZ
kernel patch, and I'm currently hunting down a good set of kernel sources to use.

Now, I'd ultimately like (love) to be able to compile a new kernel on the SL-5500
itself, probably 2.4 (I know you are a 2.6 fan) but I only have experience with
2.0.35 through 2.4.* on PCs.

Am I insane to actually persue an on-board kernel compilation, and development
environment?
Go to the top of the page
 
+Quote Post
DoTheDog
post Sep 17 2006, 08:02 PM
Post #11





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



Hrw,
Thanks for doing that. I am compiling as we speak. My machine isn't very fast either wink.gif

I did notice though that it is compiling:
gcc-cross-initial-3.4.4-r4
linux-libc-headers-2.6.11.1

Is it supposed to compile those?

Also, is there a way to check to make sure it is using gcc 2.95?

miskinis,
I tried compiling some pretty big things on a spitz and it kept puking running out of memory. And it took forever wink.gif You are better off using OE.

Rob
Go to the top of the page
 
+Quote Post
Hrw
post Sep 18 2006, 12:48 AM
Post #12





Group: Members
Posts: 1,376
Joined: 11-January 04
From: Poznań, Poland
Member No.: 1,413



GCC 2.95 is needed ONLY for 2.4 zaurus kernels. Cxx00 machines does not use 2.4 kernel in OZ.

Below you see list of things which bitbake would build to compile kernel. Versions will be different in .oz354x branch but list would be similiar.
CODE
10:45 hrw@work:oz-dev$ bitbake -n virtual/kernel
NOTE: Using cache in '/home/hrw/devel/build/oz-dev/tmp/cache'
NOTE: Handling BitBake files: \ (4002/4002) [100 %]
NOTE: Parsing finished. 3870 cached, 0 parsed, 132 skipped, 0 masked.

NOTE: Machine ID assigned by tinderbox: 115
NOTE: build 200609181045: started

OE Build Configuration:
BB_VERSION     = "1.6.1"
OE_REVISION    = "<unknown>"
TARGET_ARCH    = "arm"
TARGET_OS      = "linux"
MACHINE        = "tosa"
DISTRO         = "openzaurus"
DISTRO_VERSION = "hrw-test"
TARGET_FPU     = "soft"

NOTE: package quilt-native-0.45: started
NOTE: package quilt-native-0.45: completed
NOTE: package ipkg-utils-native-1.6+cvs20050404: started
NOTE: package ipkg-utils-native-1.6+cvs20050404: completed
NOTE: package gnu-config-native-0.1+cvs20050701: started
NOTE: package gnu-config-native-0.1+cvs20050701: completed
NOTE: package m4-native-1.4.2: started
NOTE: package m4-native-1.4.2: completed
NOTE: package autoconf-native-2.59: started
NOTE: package autoconf-native-2.59: completed
NOTE: package automake-native-1.9.3: started
NOTE: package automake-native-1.9.3: completed
NOTE: package libtool-native-1.5.10: started
NOTE: package libtool-native-1.5.10: completed
NOTE: package file-native-4.16: started
NOTE: package file-native-4.16: completed
NOTE: package pax-utils-native-0.1.13: started
NOTE: package pax-utils-native-0.1.13: completed
NOTE: package gettext-native-0.14.1: started
NOTE: package gettext-native-0.14.1: completed
NOTE: package flex-native-2.5.31: started
NOTE: package flex-native-2.5.31: completed
NOTE: package bison-native-2.0: started
NOTE: package bison-native-2.0: completed
NOTE: package binutils-cross-2.16: started
NOTE: package binutils-cross-2.16: completed
NOTE: package gcc-cross-initial-3.4.4: started
NOTE: package gcc-cross-initial-3.4.4: completed
NOTE: package linux-libc-headers-2.6.11.1: started
NOTE: package linux-libc-headers-2.6.11.1: completed
NOTE: package qemu-qop-nogfx-native-0.8.0+svn20060913: started
NOTE: package qemu-qop-nogfx-native-0.8.0+svn20060913: completed
NOTE: package glibc-2.3.5+cvs20050627: started
NOTE: package glibc-2.3.5+cvs20050627: completed
NOTE: package gcc-cross-3.4.4: started
NOTE: package gcc-cross-3.4.4: completed
NOTE: package module-init-tools-cross-3.2.2: started
NOTE: package module-init-tools-cross-3.2.2: completed
NOTE: package update-modules-1.0: started
NOTE: package update-modules-1.0: completed
NOTE: package linux-openzaurus-2.6.17: started
NOTE: package linux-openzaurus-2.6.17: completed
NOTE: build 200609181045: completed
Build statistics:
 Attempted builds: 21
10:45 hrw@work:oz-dev$
Go to the top of the page
 
+Quote Post

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

 



RSS Lo-Fi Version Time is now: 20th April 2014 - 12:15 AM