OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: deadite66 on February 16, 2008, 10:18:12 am
-
been trying all morning to get this to work but no luck
host machine is ubuntu gutsy x86
target is Zaurus C3200 spitz
moon@sakura:~/OE/build$ bitbake base-image
NOTE: Handling BitBake files: \ (4965/4965) [100 %]
NOTE: Parsing finished. 4739 cached, 0 parsed, 226 skipped, 0 masked.
NOTE: build 200802161508: started
OE Build Configuration:
BB_VERSION = "1.8.8"
OE_REVISION = "ae6e884558b73791ef6c6aa8d6c2dff00277dfdc"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "spitz"
DISTRO = "angstrom"
DISTRO_VERSION = "2007.12-r4"
TARGET_FPU = "soft"
NOTE: Resolving missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Running task 190 of 1353 (ID: 1027, /home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/glib-2.0/glib-2.0-native_2.12.4.bb, do_compile)
NOTE: Running task 191 of 1353 (ID: 922, /home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/python/python-native_2.5.1.bb, do_patch)
NOTE: package glib-2.0-native-2.12.4: started
NOTE: package glib-2.0-native-2.12.4-r1: task do_compile: started
NOTE: package python-native-2.5.1: started
NOTE: package python-native-2.5.1-ml1: task do_patch: started
NOTE: Applying patch 'bindir-libdir.patch'
NOTE: Applying patch 'cross-distutils.patch'
ERROR: function do_compile failed
ERROR: log data follows (/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/temp/log.do_compile.27152)
| NOTE: make -j4
| make all-recursive
| make[1]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4'
| Making all in .
| make[2]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4'
| make[2]: Nothing to be done for `all-am'.
| make[2]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4'
| Making all in m4macros
| make[2]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/m4macros'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/m4macros'
| Making all in glib
| make[2]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| make all-recursive
| make[3]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| Making all in libcharset
| make[4]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib/libcharset'
| make[4]: Nothing to be done for `all'.
| make[4]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib/libcharset'
| make[4]: Entering directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| if /bin/bash ../i686-linux-libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_DEPRECATED -DGLIB_COMPILATION -isystem/home/moon/OE/build/tmp/angstrom/staging/i686-linux/include -pthread -isystem/home/moon/OE/build/tmp/angstrom/staging/i686-linux/include -Os -Wall -MT gconvert.lo -MD -MP -MF ".deps/gconvert.Tpo" -c -o gconvert.lo gconvert.c; \
| then mv -f ".deps/gconvert.Tpo" ".deps/gconvert.Plo"; else rm -f ".deps/gconvert.Tpo"; exit 1; fi
| gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -DG_LOG_DOMAIN=\"GLib\" -DG_DISABLE_CAST_CHECKS -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_DEPRECATED -DGLIB_COMPILATION -isystem/home/moon/OE/build/tmp/angstrom/staging/i686-linux/include -pthread -isystem/home/moon/OE/build/tmp/angstrom/staging/i686-linux/include -Os -Wall -MT gconvert.lo -MD -MP -MF .deps/gconvert.Tpo -c gconvert.c -fPIC -DPIC -o .libs/gconvert.o
| gconvert.c:48:2: error: #error GNU libiconv not in use but included iconv.h is from libiconv
| gconvert.c:92: warning: 'visibility' attribute ignored on non-class types
| make[4]: *** [gconvert.lo] Error 1
| make[4]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4/glib'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/glib-2.12.4'
| make: *** [all] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /home/moon/OE/build/tmp/angstrom/work/i686-linux/glib-2.0-native-2.12.4-r1/temp/log.do_compile.27152
NOTE: package glib-2.0-native-2.12.4-r1: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package glib-2.0-native-2.12.4: failed
ERROR: Build of /home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/glib-2.0/glib-2.0-native_2.12.4.bb do_compile failed
ERROR: Task 1027 (/home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/glib-2.0/glib-2.0-native_2.12.4.bb, do_compile) failed
NOTE: Waiting for 1 active tasks to finish
NOTE: 1: /home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/python/python-native_2.5.1.bb, do_patch (27153)
NOTE: Applying patch 'dont-modify-shebang-line.patch'
NOTE: Applying patch 'default-is-optimized.patch'
NOTE: package python-native-2.5.1-ml1: task do_patch: completed
NOTE: package python-native-2.5.1: completed
NOTE: Tasks Summary: Attempted 189 tasks of which 189 didn't need to be rerun and 1 failed.
ERROR: '/home/moon/OE/org.openembedded.angstrom-2007.12-stable/packages/glib-2.0/glib-2.0-native_2.12.4.bb' failed
moon@sakura:~/OE/build$
any ideas?
-
http://angstrom-distribution.org/ (http://angstrom-distribution.org/) -> contact -> follow instructions
-
ok sent to devel list, though please be gentle i'm not a developer only building this becouse no one it seems wanted to reply to my request of building rt73-k2wrlz on the devel or user list.
-
http://angstrom-distribution.org/ (http://angstrom-distribution.org/) -> contact -> follow instructions
I don't seem to notice any SLA on Angstrom support, so it's not unreasonable for someone to look elsewhere when angstrom list is /dev/null
-
I don't seem to notice any SLA on Angstrom support, so it's not unreasonable for someone to look elsewhere when angstrom list is /dev/null
Nice put Speculatrix. I couldn't agree with you more.
-
after much googleing and luck it looks like i've got it working now, decided to start from scratch in a fresh ubuntu gutsy install in vmware.
pretty much all of the problems i had was figuring out dependancys OE needed which don't seem to be listed including one accident where installing kfind apparently added the app or library my current OE sticking point was.
another was qemu-native failing to compile which was solved by just installing it from repos and adding one line to local.conf.
its still downloading and compiling away so fingers crossed.
so the angstrom and OE setup instructions are very basic.
-
yay got rt73-k2wrlz-2.0.1 compiled, installed and it works fine o/
p.s.
no replies to my post on angstrom-devel
-
yay got rt73-k2wrlz-2.0.1 compiled, installed and it works fine o/
p.s.
no replies to my post on angstrom-devel
great work. are you able to write a bitbake recipe?
(*edit* I can't help you, I never got further than the first three steps of setting up OE, it was too much hassle!)
-
great work. are you able to write a bitbake recipe?
no idea.
the entirety of my compiling skills is ./configure and make
-
great work. are you able to write a bitbake recipe?
no idea.
the entirety of my compiling skills is ./configure and make
he he, well, I'm a little ahead of you, but too lazy to learn OE. when they produce a vmware or qemu image which has everything ready to go for developing zaurus applications, maybe I'll have a go.