Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - DoTheDog

Pages: [1] 2 3 ... 7
1
Open Embedded / Stupid Oe Question
« on: January 19, 2007, 04:41:56 pm »
Mickeyl,
Is there a good example of something like that? Something that pulls packages from other bb files? I tried, just creating a bb file with just the RDEPENDS line, but it had trouble during do_package.

Rob

2
Open Embedded / Stupid Oe Question
« on: January 18, 2007, 11:35:50 am »
Thanks Mickeyl,
I created the bb files for all those packages, so I guess I am asking, what I need to do so that they can all be included in one ipk? or is that bad form?

Rob

3
Open Embedded / Stupid Oe Question
« on: January 17, 2007, 12:22:48 pm »
Hi all,
I am trying to build an Orbiter for Plutohome for the zaurus using OE. It requires a few libraries that I now have working bb recipes for. But when I build the executable, I get :

Code: [Select]
NOTE: Couldn't find shared library provider for libDCECommon.so
NOTE: Couldn't find shared library provider for libSDL_Helpers.so
NOTE: Couldn't find shared library provider for libSerializeClass.so
NOTE: Couldn't find shared library provider for libPlutoUtils.so

What do I need to add to the bb file so that it will find these or their bb files?

Rob

4
Open Embedded / Failed To Build 3.5.4.1 2.4 For Collie
« on: September 18, 2006, 12:02:30 am »
Hrw,
Thanks for doing that. I am compiling as we speak. My machine isn't very fast either

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  You are better off using OE.

Rob

5
Open Embedded / Failed To Build 3.5.4.1 2.4 For Collie
« on: September 16, 2006, 05:39:46 pm »
Hrw,

Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=141564\"][{POST_SNAPBACK}][/a][/div]

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

6
Open Embedded / Failed To Build 3.5.4.1 2.4 For Collie
« on: September 16, 2006, 10:10:09 am »
lardman,
Thanks for the reply.

Quote
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: [Select]
MACHINE_KERNEL_VERSION = "2.4"
I also changed /org.openembedded.oz354x/conf/machine/collie.conf
to say:
Code: [Select]
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: [Select]

| 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
There are a whole bunch of dbus.c errors then:
Code: [Select]

| 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
My guess is that it is trying to use gcc-3.4.4. I found this in the log:
Code: [Select]
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

7
Open Embedded / Failed To Build 3.5.4.1 2.4 For Collie
« on: September 15, 2006, 08:30:10 am »
Quote
update metadata and build again
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

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 [a href=\"http://handhelds.org/download/projects/toolchain/archive/cross-2.95.3.tar.bz2]http://handhelds.org/download/projects/too...-2.95.3.tar.bz2[/url].
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

8
Open Embedded / Failed To Build 3.5.4.1 2.4 For Collie
« on: September 13, 2006, 11:45:08 pm »
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

9
Open Embedded / Bitbake Do_package Question
« on: August 23, 2006, 10:56:34 pm »
Any help? Please?

10
Open Embedded / Bitbake Do_package Question
« on: August 21, 2006, 02:01:53 am »
Ok, I am sure this is a stupid question. But I have googled and googled and even posted a question on the IRC channel.

Anyway, if any of you are following this saga, I am trying to build the Orbiter for PlutoHome (http://www.plutohome.com). It is a home automation system, and I want to use my Akita as an Orbiter or remote.

Here is the question. I am building a number of libraries that are required for the Orbiter executable. I have actually successfully compiled all the dependencies and the executable itself. However, the ipk's aren't what I expected. The makefiles create .so files and the do_package default seems to put them in -dev.ipk files.

I have tried:
PACKAGES = "serializeclass serializeclass-dev"
FILES_serializeclass = "${libdir}/libSerializeClass.so"
FILES_serializeclass-dev = "${FILES_serializeclass}"
AUTO_LIBNAME_PKGS = "serializeclass"

But that doesn't seem to help. I still get:
NOTE: Not creating empty archive for serializeclass-11424.1.1-r0

I have tried grep'ing but I am flying a bit blind here...

Any help is appreciated.

Thanks,
Rob

11
Open Embedded / Help With Bb File
« on: August 02, 2006, 11:03:12 pm »
Quote
No it isn't, it's a generic task executor, that couple with OE can build stuff for lots of distributions, and one of those is OZ.

I stand corrected. I guess what I meant was that it will build for OZ specifically.

Rob

12
Open Embedded / Help With Bb File
« on: August 01, 2006, 11:59:29 pm »
Quote
  You might wish to look at the how to guide for building with the target being the Nokia 770 in Pluto@Home's wiki.

Pluto@Home Nokia770 Orbiter

Yeah, I saw that one. It looked pretty hard though. Bitbake is made for OZ and I was hoping to be able to do in that environment... Looks like bitbake is difficult as well. I haven't given up yet. Still working on it. I'll report here if I get any farther.

Rob

13
Open Embedded / Help With Bb File
« on: July 20, 2006, 01:03:59 pm »
Ok, I've gotten a bit farther but am throwing some real wierd errors. This is what I did:

I named the .bb file: serializeclass_1.1.1.bb all lower case.
Changed the line

S = "${WORKDIR}/${PN}" to

S = "${WORKDIR}/SerializeClass"

I then went into the Makefile for SerializeClass and changed the
ROOT = ..  to
ROOT = /home/oc60174/oe/build/tmp/work/serializeclass-1.1.1-r0
just to see if it would compile.

It looks like it found the make.rules file in PlutoUtils but now is throwing the following error:
Code: [Select]
oc60174@oc60174:~/oe/build> bitbake serializeclass
NOTE: Using cache in '/home/oc60174/oe/build/tmp/cache'
NOTE: Parsing finished. 2650 cached, 0 parsed, 35 skipped, 0 masked.
NOTE: build 200607201039: started

OE Build Configuration:
BB_VERSION     = "1.4.2"
OE_REVISION    = ""
TARGET_ARCH    = "arm"
TARGET_OS      = "linux"
MACHINE        = "akita"
DISTRO         = "openzaurus"
DISTRO_VERSION = "3.5.4.1"
TARGET_FPU     = "soft"

NOTE: package serializeclass-1.1.1: started
NOTE: package serializeclass-1.1.1-r0: task do_fetch: started
NOTE: package serializeclass-1.1.1-r0: task do_fetch: completed
NOTE: package serializeclass-1.1.1-r0: task do_compile: started
ERROR: function do_compile failed
ERROR: log data follows (/home/oc60174/oe/build/tmp/work/serializeclass-1.1.1-r0/temp/log.do_compile.19772)
| NOTE: make
| g++ -c -I./ -I../../ -I../ -I../DCE/ -I../../DCE -I../VIPShared/ -I../../VIPShared -I/usr/include/mysql -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_DEVEL_DEFINES -DUSE_LZO_DATAGRID -Wall -g -ggdb3 -D_GNU_SOURCE SerializeClass.cpp -o SerializeClass.o
| /usr/include/c++/4.0.2/bits/stl_deque.h: In member function ‘void std::_Deque_base<_Tp, _Alloc>::_M_initialize_map(size_t)’:
| /usr/include/c++/4.0.2/bits/stl_deque.h:452: error: expected unqualified-id before ‘(’ token
| /usr/include/c++/4.0.2/bits/deque.tcc: In member function ‘void std::deque<_Tp, _Alloc>::_M_reallocate_map(size_t, bool)’:
| /usr/include/c++/4.0.2/bits/deque.tcc:747: error: expected unqualified-id before ‘(’ token
| SerializeClass.cpp: In member function ‘bool SerializeClass::SerializeRead(std::string, void*)’:
| SerializeClass.cpp:405: warning: deleting ‘void*’ is undefined
| make: *** [SerializeClass.o] Error 1
| FATAL: oe_runmake failed
NOTE: Task failed: /home/oc60174/oe/build/tmp/work/serializeclass-1.1.1-r0/temp/log.do_compile.19772
NOTE: package serializeclass-1.1.1-r0: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package serializeclass-1.1.1: failed
ERROR: Build of serializeclass failed

Is it a problem with gcc-4? or a problem with the code?

Also, lardman, the source is downloading/unpacking to: ~/oe/build/tmp/work/serializeclass-1.1.1-r0/PlutoUtils
~/oe/build/tmp/work/serializeclass-1.1.1-r0/SerializeClass

Anyhelp is appreciated.

Rob

14
X/Qt / Memory Shortage When Compiling Inside X/qt
« on: July 20, 2006, 08:20:10 am »
Hi Shiroikuma,
How do you bind it in chroot? when I do "echo $TMPDIR" it comes back blank in Pocketworkstation. I can see the card though.

DoTheDog

EDIT:
In qt I tried
"mount -o bind /mnt/card /hdd2/debroot/mnt/card"
and it still comes up blank in pocketworkstation.

Edit2:
Looks like the card is already mounted in debian. mount in qt gives:
/dev/mmcda1 on /usr/mnt.rom/card type vfat (rw,noatime)

So I tried export TMPDIR=/mnt/card/tmp in Pocketworkstation.
Now in chroot echo $TMPDIR, gives /mnt/card/tmp AND in qt I get the same, but I still get the Qt Memory status thing.

Help?

15
X/Qt / Memory Shortage When Compiling Inside X/qt
« on: July 19, 2006, 12:05:28 pm »
Resurrecting an old post. I've been trying to compile a relatively large C++ package native in Pocketworkstation and I keep getting the dreaded Memory Status thing coming up. If I leave it it will crash Pocketworkstation.

I have tried:

In qtopia terminal "export TMPDIR=/mnt/card/tmp" on a 512MB sd card for both root and zaurus. Then "xlauncher debian". Still bombs out.

Also,
Code: [Select]
export TMPDIR=/mnt/card/tmp
su -c 'mount /dev/mmcda1 `cat /etc/debroot`/mnt/card'
in /home/zaurus/.xinitrc
then "xlauncher debian" and it still doesn't work.

I even tried Shiroikuma's open and close qt apps but it takes a long time to do and it eventually bombs out.

Any ideas? help? Meanie?

Pages: [1] 2 3 ... 7