Openmoko - User contributions [en]

Talk:MokoMakefile

2008-08-08T10:51:28Z

Jas: /* problem with make openmoko-devel-image */ me too

== MokoMakefile won't work on Ubuntu Hardy Heron ==
Hello, there!

Since my upgrade to Hardy Heron MokoMakefile seems to be broken on my ubuntu box. I already tried several times to download a new Makefile into a fresh directory - without success. What I get is always:

:~/moko$ make image
( cd build && . ../setup-env && \
( bitbake openmoko-devel-image u-boot-openmoko ) )
ERROR: Openembedded's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

/proc/sys/vm/mmap_min_addr is not 0. This will cause problems with qemu so please fix the value (as root).

make: *** [openmoko-devel-image] Error 1

For another report on this problem see also: http://lists.openmoko.org/pipermail/community/2008-May/017545.html

When trying to compile the april software update (ASU) this error doesn't occour, though.

=== solution ===

<pre>
$ sudoedit /etc/sysctl.conf
</pre>

And add 'vm.mmap_min_addr = 0' (without quotes) to that file.

== The paths that are mentioned on this page are partially wrong ==
I am not sure enough what the paths should be, but - two things have changed since the section "developing with mokomakefile/How to add your own shiny new application" of this page was created:
- The path where the packages are kept, and
- Where to add the information that we have added a new package.

== Update git to 1.5! ==

Version git-1.4 does not work, check your version with the command

<pre>
git --version
</pre>

and install at least git version 1.5 if not already present.

== Fails on a 32bit machine - try again without ccache? ==

<pre>/bin/sh ./libtool --mode=compile ccache gcc -DHAVE_CONFIG_H -I.... -W... -O2 -c -o libbfd.lo build/tmp/work/armv4t-linux/binutils-cross-2.17-r0/binutils-2.17/bfd/libbfd.c
ccache gcc -DHAVE_CONFIG_H -I... -W... -O2 -c /usr/local/oe/build/tmp/work/armv4t-linux/binutils-cross-2.17-r0/binutils-2.17/bfd/libbfd.c -o t shift count >= width of type
make[5]: *** [libbfd.lo] Error 1
</pre>

Any insight here? --[[User:Adam|Adam]] 23:10, 15 May 2007 (CEST)
: Try without ccache (did you get it compiled meanwhile or can we remove this?) --[[User:BernhardKaindl|BernhardKaindl]] 23:05, 19 September 2007 (CEST)

== Facing Problems with ogg libraries ==
just get the path and delete the .bb file that causes the problem
== Building on Fedora Core 6 ==

Install stuff needed for OpenMoko:
# yum install python m4 make wget curl ftp cvs monotone subversion \
tar bzip2 gzip unzip python-psyco ccache perl texinfo texi2html \
diffstat openjade docbook-style-dsssl docbook-style-xsl docbook-dtds \
docbook-utils sed bison bc glibc-devel gcc binutils pcre pcre-devel git \
quilt groff linuxdoc-tools patch compat-gcc-34 lynx netpbm
(notice ''compat-gcc-34'' wich was needed for FC6 (gcc 4 installed), and ''lynx'' which is needed by ''qemu'' (no fallback to ''wget'', ''curl'', or ''links'' at the moment and no check for it, resulting in strange "sleep" errors when trying to build without ''lynx'').

Build it:
$ make setup
$ make openmoko-devel-image
$ unset LD_LIBRARY_PATH
$ make update-makefile && make update && make setup && make openmoko-devel-image

I have also done a
$ unset LD_LIBRARY_PATH; make update-makefile && nice make update && nice make setup && nice make all
(This takes several hours)

Build qemu:
$ make qemu

Run it:
# echo 1024 > /proc/sys/dev/rtc/max-user-freq
$ make run-qemu
This will bring up the OpenMoko :) Use SPACE for AUX and ENTER for POWER.
Not quite the same as holding a Neo1973 in your hands I would guess, but this is the best we can do for now. Thanks!

== Building on Ubuntu Feisty ==

MokoMakefile requires more than 512 MB of RAM + Swap space (around 1GB?).

If you need swap, please '''check that its size under Feisty is not null'''!

[https://bugs.launchpad.net/ubuntu/+bug/105490 Bug #105490] describes the current issue and offers a workaround (23 Jul 07).

== Fails trying to build bluez-utils ==
on Gentoo Linux, it fails compiling bluez-utils (I've tried also "make clean-package-bluez-utils" before the following command)

do a "make build-package-libusb; make clean-package-bluez-utils" and it should continue (the bluez-utils .bb is missing the libusb dependency)

== openSUSE 10.1 and 10.2 workarounds ==

ltrace package fails to build with error:
<pre>
...
checking for pid_t... yes
checking for getopt... yes
checking for getopt_long... yes
checking gelf.h usability... no
checking gelf.h presence... no
checking for gelf.h... no
configure: error: ***** gelf.h not found *****
FATAL: oe_runconf failed
</pre>

'''FIX: '''
edit ''/home/moko/build/tmp/work/armv4t-linux/ltrace-0.4-r0/ltrace-0.4/configure.ac''
at line 44: remove the following block:
<pre>
for path in /usr/include/elfutils /usr/local/include/elfutils \
/usr/include/libelf /usr/local/include/libelf; do
if test -f ${path}/gelf.h; then
CPPFLAGS="$CPPFLAGS -I ${path}"
fi
done
</pre>
( it adds /usr/include/elfutils to path, which causes cross-compile badness error )

=== QEMU build fails to compile USB code ===
<pre>
/usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user' declared void
/usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_handle_control':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:103: error: invalid application of `sizeof' to incomplete type `usbdevfs_ctrltran
sfer'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_handle_data':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:120: error: storage size of 'bt' isn't known
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:132: error: invalid application of `sizeof' to incomplete type `usbdevfs_bulktran
sfer'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:120: warning: unused variable `bt'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c: In function `usb_host_device_open':
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:199: error: storage size of 'ctrl' isn't known
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:202: error: invalid application of `sizeof' to incomplete type `usbdevfs_ioctl'
/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c:199: warning: unused variable `ctrl'
make[2]: *** [usb-linux.o] Error 1
</pre>

'''FIX: '''
edit ''/home/moko/openmoko/trunk/src/host/qemu-neo1973/usb-linux.c''
at line 29 add the following (before ''#include <linux/usbdevice_fs.h>'')
<pre>
#include <linux/compiler.h>
</pre>
hint: there is a copy of the file in ''/home/moko/build/tmp/work/i686-linux/qemu-native-0.9.0+cvs20070613-r5/qemu/usb-linux.c''

''see: http://osdir.com/ml/emulators.kvm.devel/2007-01/msg00101.html''

== Cannot satisfy fstests ==
<pre>
make openmoko-devel-image
...
| Collected errors:
| ERROR: Cannot satisfy the following dependencies for task-openmoko-debug:
| fstests
NOTE: Task failed: /no-backup/Moko/build/tmp/work/fic-gta01-linux/openmoko-devel-image-1.0-r0/temp/log.do_rootfs.25036
NOTE: package openmoko-devel-image-1.0-r0: task do_rootfs: failed
ERROR: TaskFailed event exception, aborting
</pre>
Failed on debian etch 2007-07-20
Solution from mailing list post from hardskinone, report of an irc chat
<pre>
I got help in IRC channel. I do following steps
* remove fstest from oe/packages/tasks/task-openmoko.bb ,
* increase PR field by one
* make openmoko-devel-image
</pre>

== conflicting types for 'futimens' ==

if you encounter the following error:

| In file included from utimecmp.c:40:
| utimens.h:2: error: conflicting types for 'futimens'
| /usr/include/sys/stat.h:370: error: previous declaration of 'futimens' was here

a patch is needed because your glibc is too new. grab & enable the patch as follows

cd openembedded/packages/coreutils
mv coreutils_5.3.0.bb coreutils_5.3.0.orig
wget http://www.openembedded.org/repo/org.openembedded.dev/packages/coreutils/coreutils_5.3.0.bb
cd -
cd openembedded/packages/coreutils/coreutils-5.3.0
wget http://www.openembedded.org/repo/org.openembedded.dev/packages/coreutils/coreutils-5.3.0/futimens.patch
cd -

== Workaround for problems compiling mtd-utils ==

Change the line on <code>openembedded/packages/mtd/mtd-utils_1.0.0+git.bb</code> which reads:

SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=master \

to:

SRC_URI = "git://git.infradead.org/mtd-utils.git;protocol=git;tag=a6fa706fe9e7696b4b2045edf9698c3bac07e3e3 \

which forces the recipe to use an older revision (the one which worked last time I built the image on my computer).

Be sure to remember to undo the change later, or else you will not get any new changes to that package. --[[User:CesarB|CesarB]] 04:48, 25 July 2007 (CEST)

Note: these patches should be updated - the lzo patch is included in the current version, so backing off to the previous version and repatching seems silly. I was able to make it through this part of the build by applying the remaining patches manually. --[[User:Mellon|Ted Lemon]] 15:44, 29 July 2007 (CDT)

== Monotone segfaulting on Ubuntu Feisty Fawn/PPC ==
If you are running Ubuntu Feisty Fawn on a PowerPC computer you will experience problems running monotone. To fix this issue you need to install monotone as well as the libboost packages from Gutsy. The easiest way to accomplish this is to add the gutsy repositories to your sources.list
and change the preferences to look like this:

Package: *
Pin: release a=feisty
Pin-Priority: 700

Package: *
Pin: release a=gutsy
Pin-Priority: -100

Package: libc6 libc6-dev tzdata util-linux libgcc1 libstdc++6 monotone
Pin: release a=gutsy
Pin-Priority: 800

Package: libboost-*
Pin: release a=gutsy
Pin-Priority: 800

After doing this install monotone in this way:
apt-get -t gutsy install monotone.
That should install monotone 0.35 with updated (and working) boost libraries.

== Fails on ncurses install in Fedora 7 with a "tic -x" message ==
Adjust the following command to your system, then run it:
export LD_LIBRARY_PATH=/home/moko/build/tmp/work/x86_64-linux/ncurses-native-5.4-r8/ncurses-5.4/lib
Then start make again and it should pick up where it left off.

You can get a list of potential paths to use with the following command from you main moko directory:
find . | grep libncurses

The basic problem is that it is linking against your main system libraries instead of the OpenEmbedded ones.

There's probably a cleaner way of handling this - please update this entry if you know it.

This has been fixed in Openembedded, see [http://bugs.openembedded.org/show_bug.cgi?id=2554 Openembedded Bug #2554] for further details.

== uboot-gta01 fails to build ==
Changes in the GIT of U-Boot make the OpenMoko patches unapplyable. For the use of Revision ''cc3023b9f95d7ac959a764471a65001062aecf41'' and everything will be fine for now.

== Perl fails to build ==
After following every bit of advice I can find to 'make clean' and nuke the perl build directories, every build comes up with:

| make[1]: Entering directory `/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7'
| make[1]: *** No rule to make target `<command-line>', needed by `miniperlmain.o'. Stop.
| make[1]: Leaving directory `/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7'
| FATAL: oe_runmake failed
NOTE: Task failed: /src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/temp/log.do_compile.19531
NOTE: package perl-native-5.8.7-r3: task do_compile: failed

Solution turned out to be editing
/src/openmoko/build/tmp/work/i686-linux/perl-native-5.8.7-r3/perl-5.8.7/makedepend.SH and at line 169 change the regexp to eat references to "<command.line>" to catch what was leaking through.

== glibc fails to build ==
If you see an error like

<pre>

NOTE: package glibc-2.6.1: started
NOTE: package glibc-2.6.1-r10: task do_configure: started
ERROR: function do_configure failed
ERROR: log data follows (/home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gn
ueabi/glibc-2.6.1-r10/temp/log.do_configure.11446)
| NOTE: Running /home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/gli
bc-2.6.1-r10/glibc-2.6.1/configure --build=i686-linux
--host=arm-angstrom-linux-gnueabi --target=arm-angstrom-linux-
gnueabi --prefix=/usr --exec_prefix=/usr
--bindir=/usr/bin --sbindir=/usr/sbin --li
bexecdir=/usr/libexec --datadir=/usr/share --sy
sconfdir=/etc --sharedstatedir=/usr/com --localstate
dir=/var --libdir=/usr/lib --includedir=/usr/in
clude --oldincludedir=/usr/include --infodir=/u
sr/share/info --mandir=/usr/share/man --enab
le-kernel=2.4.0 --without-cvs --disable-profile --disable-debug --without-gd
--enable-clocale=gnu --enable-add-ons=ports,nptl,libidn --with-headers=/hom
e/alex/moko/build/tmp/staging/arm-angstrom-linux-gnueabi/usr/include --without
-selinux --without-fp --without-fp ...
| configure: loading site script /home/alex/moko/openembedded/site/endian-little
| configure: loading site script /home/alex/moko/openembedded/site/common-linux
| configure: loading site script /home/alex/moko/openembedded/site/common-glibc
| configure: loading site script /home/alex/moko/openembedded/site/arm-common
| configure: loading site script /home/alex/moko/openembedded/site/arm-linux
| configure: loading site script /home/alex/moko/openembedded/site/common
| configure: loading site script /home/alex/moko/openembedded/site/common
| checking build system type... i686-pc-linux-gnu
| checking host system type... arm-angstrom-linux-gnueabi
| checking add-on ports for preconfigure fragments... am33 arm hppa m68k mips
| configure: running configure fragment for add-on nptl
| configure: running configure fragment for add-on libidn
| checking sysdep dirs... ports/sysdeps/arm/elf ports/sysdeps/unix/sysv/linux/ar
m/eabi/nptl ports/sysdeps/unix/sysv/linux/arm/eabi sysdeps/unix/sysv/linux/arm/e
abi ports/sysdeps/unix/sysv/linux/arm/nptl ports/sysdeps/unix/sysv/linux/arm sys
deps/unix/sysv/linux/arm ports/sysdeps/unix/sysv/linux nptl/sysdeps/unix/sysv/li
nux nptl/sysdeps/pthread sysdeps/pthread sysdeps/unix/sysv/linux sysdeps/gnu sys
deps/unix/common sysdeps/unix/mman sysdeps/unix/inet ports/sysdeps/unix/sysv npt
l/sysdeps/unix/sysv sysdeps/unix/sysv ports/sysdeps/unix/arm ports/sysdeps/unix
nptl/sysdeps/unix sysdeps/unix sysdeps/posix ports/sysdeps/arm/eabi ports/sysdep
s/arm/nptl ports/sysdeps/arm sysdeps/wordsize-32 sysdeps/ieee754/flt-32 sysdeps/
ieee754/dbl-64 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
| checking for a BSD-compatible install... /home/alex/moko/build/tmp/staging/i68
6-linux/usr/bin/install -c
| checking whether ln -s works... yes
| checking for arm-angstrom-linux-gnueabi-gcc... arm-angstrom-linux-gnueabi-gcc
-march=armv4t -mtune=arm920t
| checking for suffix of object files... o
| checking whether we are using the GNU C compiler... yes
| checking whether arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t a
ccepts -g... yes
| checking for arm-angstrom-linux-gnueabi-gcc -march=armv4t -mtune=arm920t optio
n to accept ANSI C... none needed
| checking for gcc... gcc
| checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc -E
| configure: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails san
ity check
| See `config.log' for more details.
| FATAL: oe_runconf failed
NOTE: Task failed: /home/alex/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-2.6.1-r10/temp/log.do_configure.11446
NOTE: package glibc-2.6.1-r10: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package glibc-2.6.1: failed
ERROR: Build of /home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb do_co
nfigure failed
ERROR: Task 7 (/home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb, do_co
nfigure) failed
NOTE: Tasks Summary: Attempted 448 tasks of which 440 didn't need to be rerun an
d 1 failed.
ERROR: '/home/alex/moko/openembedded/packages/glibc/glibc_2.6.1.bb' failed
NOTE: build 200808041052: completed

</pre>

Try

cd source
rm glibc*2.6.1*
cd ../build
. ../setup-env
bitbake -crebuild glibc

if this doesn't help, you have to do this

cd build
. ../setup-env
bitbake -f -c fetch gcc-cross-initial && bitbake gcc-cross-initial && bitbake -crebuild glibc

== Gettext fails to build ==
Gettext's build is broken unless you have emacs installed. Crazy though it seems. You will see an error like:

<pre>

| WARNING: Warnings can be ignored. :-)
| if test "no" != no; then \
| set x; \
| list='po-mode.el po-compat.el'; for p in $list; do \
| if test -f "$p"; then d=; else d="./"; fi; \
| set x "$@" "$d$p"; shift; \
| done; \
| shift; \
| EMACS="no" /bin/bash ../../config/elisp-comp "$@" || exit 1; \
| if test "no" != no; then \
| set x; \
| list='po-mode.el po-compat.el'; for p in $list; do \
| if test -f "$p"; then d=; else d="./"; fi; \
| set x "$@" "$d$p"; shift; \
| done; \
| shift; \
| EMACS="no" /bin/bash ../../config/elisp-comp "$@" || exit 1; \
| else : ; fi
| mv: cannot move `elc-temp' to `elc-stamp': No such file or directory
| make[5]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[5]: *** [elc-stamp] Error 1
| make[5]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[4]: *** [po-mode.elc] Error 2
| make[4]: *** Waiting for unfinished jobs....
| make[4]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools/misc'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1/gettext-tools'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/raster/moko/build/tmp/work/i686-linux/gettext-native-0.14.1-r5/gettext-0.14.1'
| FATAL: oe_runmake failed

</pre>

The solution is simple - install emacs (example below for debian/ubuntu) and try again:

<pre>

sudo apt-get install emacs
make clean-package-gettext-native-0.14.1-r5
make openmoko-devel-image

</pre>

== Building OpenMoko with chroot ==

There may be hundreds of issues which may cause that OpenMoko fails to build on your system, so it might be more straightforward to just install a standardized build environment in which the openmoko build runs in chroot, independent of your distribution.

There is now a (not fully working) script which is able to set up a 32-bit openSUSE 10.3 build environment for building OpenMoko posted on distro-devel: [http://lists.openmoko.org/pipermail/distro-devel/2007-November/000076.html]

On gentoo and debian-like distribution, you can use debootstrap to quickly setup a base chroot.

Please note that in addition to the common /dev, /sys and /proc, /dev/shm should also be mounted with --bind option. It is at least required to build a qtopia-x11 image. (Otherwise you will get some semaphore 'function not implemented' errors at qtopia-x11 installation stage).

== Fails compiling binutils-cross on Gentoo/AMD64 and openSUSE/x86_64 ==

make setup works fine, but when running make openmoko-devel-image it fails with the following:

<pre>
| make[4]: Entering directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty/testsuite'
| make[4]: Nothing to be done for `install'.
| make[4]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty/testsuite'
| make[3]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi/libiberty'
| make[2]: Nothing to be done for `install-target'.
| make[2]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi'
| make[1]: Leaving directory `build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/binutils-2.18/build.x86_64-linux.arm-angstrom-linux-gnueabi'
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross/lib/gcc-lib: No such file or directory
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross/lib: No such file or directory
| rmdir: build/tmp/cross//home/techiem2/Moko/build/tmp/cross: No such file or directory
| mv: cannot stat `build/tmp/cross/lib/libiberty.a': No such file or directory
NOTE: Task failed: build/tmp/work/armv4t-angstrom-linux-gnueabi/binutils-cross-2.18-r0/temp/log.do_stage.9730
NOTE: package binutils-cross-2.18-r0: task do_populate_staging: failed
ERROR: TaskFailed event exception, aborting
NOTE: package binutils-cross-2.18: failed
ERROR: Build of openembedded/packages/binutils/binutils-cross_2.18.bb do_populate_staging failed
ERROR: Task 1641 (openembedded/packages/binutils/binutils-cross_2.18.bb, do_populate_staging) failed
NOTE: Tasks Summary: Attempted 107 tasks of which 107 didn't need to be rerun and 1 failed.
ERROR: 'openembedded/packages/binutils/binutils-cross_2.18.bb' failed
make: *** [openmoko-devel-image] Error 1
</pre>

The final reason why the build cannot continue is:
mv: cannot stat `/home/techiem2/Moko/build/tmp/cross/lib/libiberty.a': No such file or directory

=== The lib64 issue ===

Likely, Gentoo/AMD64 uses lib64 instead of lib as the library directory for x86_64 libraries. It's l likey that many (or all?) AMD64 distributions do for their 64-bit binaries. On openSUSE-x86_64, the same happens. Debian/x86-64 seems to either not use lib64 or is somehow supported by the openmoko distribution.

On multilib/lib64 platforms like Gentoo/x86_64 and openSUSE-x86_64, the openmoko build runs into a final problem at the end of build: It tries to use fakeroot which uses LD_PRELOAD to fake a different root directory and in the final stages, after hours of compiling, fakeroot execution causes warning messages because on multilib/lib64 systems as they have two versions of many libraries, the 64-bit libraries are in /lib64, /usr/lib64 and oder lib64 paths, while the 32-bit libraries are in /lib, /usr/lib and other lib paths. Some tool on these lib64 distributions are adapted to install 64-bit libraries to lib64, but this seems to fail when cross-compiling.

At least on openSUSE-10.3 the missing libiberty.a was installed to build/tmp/cross/lib64/libiberty.a, which looks wrong, and it is if this libiberty.a file contains 32-bit arm objects. If it contains 64-bit x86_64 objects, it's fine, but openembedded/openmoko is not expecting it in a lib64 directory. I am not sure what is the case.

The lib64 fakeroot issue requires to change the openembedded build scripts, which is doable. But it's not very easy to find the correct script and patch it correctly. If you feel adventourus, go ahead and try to build openmoko on a lib64 distribution, but it's easyer to set up a complete 32-bit chroot environment and run a normal build in it.

After seeing this, I assumed that openmoko/openembedded was clearly not tested with lib64 build hosts and since that would mean that even if I'd fix that error, many others could follow, and as I was not interested to fix the lib64 bugs but rather wanted to see something running first, I decided to make openmoko/openembedded think that it was running on a normal 32-bit non-lib64 machine.

There are several ways to do that:
* You install an 32bit x86-Linux somewhere and use that for building:
** Do a native install and dual-boot the 32bit x86-linux (That's for dummies which do not know the other tricks)
** Install 32bit x86-Linux in a virtual machine (Takes powerful hardware and has some overhead too). Use [http://gentoo-wiki.com/VirtualBox VirtualBox], for example.
* you can install a 32-bit development system in to a chroot jail and compile there (also quite some setup and inconvinience). See [http://www.gentoo.org/proj/en/base/amd64/howtos/chroot.xml the gentoo guide]

=== Building on SuSE Linux 10.3-AMD64 with -m32 (not finished) ===

Install the following packages for the 32-bit C/C++ compiler target option -m32 to work and to compile what is needed

gcc42-32bit gcc42libgcc42-32bit glibc-devel-32bit libstdc++-devel-32bit ncurses-devel-32bit zlib-devel-32bit (maybe also gtk2-devel-32bit)

The openSUSE 10.3-AMD64 has no libopenssl-devel-32bit, but you can install the 32-bit rpm from the i586 10.3 rpm tree:

libopenssl-devel

You should also make sure that gdbm-devel is not installed.
The multilib support in ld has an issue which surfaces when it is called from perl's Configure script to complile a test program with -Lgdbm. If gdbm-devel is installed, it finds /usr/lib64/libgdbm.so, but since it's not compatible with 32-bit, it skips it, but also does not search the specified -Lpath where the OpenEmbedded-built libgdbm.so is already installed. To work around this, uninstall /usr/lib64/libgdbm.so with:
rpm -e gdbm-devel

Note these need to be the 32-bit cpp33 and gcc33 rpms as the 64-bit gcc33 rpms for openSUSE do not support the 32-bit target.

To make the OpenMoko build think that its running on 32-bit i686, use linux32 (changes uname -m to i686 in the new shell):

linux32 bash

And set up gcc scripts which force the use of gcc-3.3 (it can only generate 32-bit assembly) for all compilation:

mkdir bin;cd bin
echo '/usr/bin/${0##*/}-3.3 -m32 "$@"' >gcc
echo '/usr/bin/${0##*/} -m elf_i386 "$@"' >ld
echo '/usr/bin/${0##*/} --32 "$@"' >gas
sed -i '1i#!/bin/sh' gcc gas ld
chmod 755 gcc gas ld
ln -s gcc cc
ln -s gcc c++
ln -s gcc g++
ln -s gas as
echo PATH=\""$PWD":\$PATH\" >.setup-gcc-m32
cd -

Then set the path and test it:

source bin/.setup-gcc-m32
type gcc

== More package requirements ==

On my system (Kubuntu 6.10) build failed with message "ERROR: QEMU requires SDL or Cocoa for graphical output" because package <tt>libsdl-image1.2-dev</tt> was missing. Use <tt>apt-get install libsdl-image1.2-dev</tt> to install. Additionally I had to install packages <tt>cvs</tt> and <tt>diffstat</tt>. I was also asked to install Psyco JIT Compiler (package <tt>python-psyco</tt>) to increase performance. Nevertheless <tt>make flash-qemu-local</tt> took some hours, but now I finally can get an impression of the phone that I am looking for! -- [[User:Nichtich|Nichtich]] 00:26, 20 September 2007 (CEST)

== pango-directfb failed to build due to missing Glib 2.14.x ==

The latest(as of Sept. 25, 2007) build started to fail with the following error:

| checking for GLIB... no
| configure: error:
| *** Glib 2.14.0 or better is required. The latest version of
| *** Glib is always available from ftp://ftp.gtk.org/.
| FATAL: oe_runconf failed
NOTE: Task failed:
/media/sdc1/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/\
pango-directfb-1.18.1-r0/temp/log.do_configure.19927
NOTE: package pango-directfb-1.18.1-r0: task do_configure: failed
ERROR: TaskFailed event exception, aborting
NOTE: package pango-directfb-1.18.1: failed
ERROR: Build of /media/sdc1/moko/openembedded/packages/pango/\
pango-directfb_1.18.1.bb do_configure failed

The Glib included in the build tree seems to be only 2.12.12, so looks like something
is broken in term of dependency.

This had happened on both of Fedora 7 and Debian Etch. I am running the latest
MokoMakefile with OM-2007.2. The funny thing is that the build had worked only
couple nights ago. Any idea? I will update anything I find here and also on my blog(see my user profile).
[[User:ttz|ttz]] Wed Sep 26 12:17:33 CDT 2007

pango-directfb had been removed from OE for now due to the report of it breaking builds like OpenMoko.

[[User:ttz|ttz]] Thu Oct 4 10:20:12 CDT 2007

== uicmoc4 failes to compile ==

This is solved by installing libz-dev

Or, look at [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=747 Bug #747]

== svn: REPORT request failed on '/repos/tasks/!svn/vcc/default' ==

osiris$ make update
...
Fetching external item into 'trunk/src/target/OM-2007.2/applications/openmoko-today2/libkoto'
svn: REPORT request failed on '/repos/tasks/!svn/vcc/default'
svn: REPORT of '/repos/tasks/!svn/vcc/default': 200 OK (http://svn.o-hand.com)
make: *** [update-openmoko] Error 1

osiris$ cd openmoko/trunk/src/target/OM-2007.2/applications/openmoko-today2//libkoto/
osiris$ svn up -r HEAD
svn: REPORT request failed on '/repos/tasks/!svn/vcc/default'
svn: REPORT of '/repos/tasks/!svn/vcc/default': 200 OK (http://svn.o-hand.com)

Anyone know about this one?
--[[User:Blackh|Blackh]] 00:11, 12 October 2007 (CEST)

== bootparam_prot.h fails to install in glibc-intermediate-2.5 package (Debian sid) ==

| install: cannot stat
`/home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/glibc-2.5/sunrpc/rpcsvc/bootparam_prot.h'
No such file or directory
NOTE: Task failed: /home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/temp/log.do_stage.3940

For some reason, on Debian, the rpcgen command needs "-Y /usr/bin" added to the end of it or it won't work ("cannot find any C preprocessor (cpp)"). This can be fixed by hand...

cd /home/blackh/src/openmoko/moko/build/tmp/work/armv4t-angstrom-linux-gnueabi/
glibc-intermediate-2.5-r7/glibc-2.5/sunrpc/rpcsvc
for f in *.x ; do rpcgen -h $f -o ${f%%.x}.h -Y /usr/bin ; done

This command will generate the right files and you can resume the build with

make openmoko-devel-image

Here is a better fix - put this script, calling it rpcgen, somewhere in your PATH before /usr/bin:

#!/bin/sh
exec /usr/bin/rpcgen -Y /usr/bin "$@"

--[[User:Blackh|Blackh]] 05:17, 12 October 2007 (CEST)

== Cannot find SVN openmoko-terminal2 ==
I'm having an issue when building MokoMakeFile where it is unable to find http://svn.openmoko.org/trunk/src/target/OM-2007.2/applications/openmoko-terminal2. Any ideas on how to fix this?

--[[User:cartera|cartera]]

== problem with make openmoko-devel-image ==

when i try to do my first make openmoko-devel-image I obtain this error:

<pre>
NOTE: Running task 844 of 5445 (ID: 671, /home/xraver/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb, do_fetch)
NOTE: package linux-openmoko-2.6.24+git20080422: started
NOTE: package linux-openmoko-1_2.6.24+git20080422-r0: task do_fetch: started
NOTE: fetch http://downloads.openmoko.org/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz
--08:47:41-- http://downloads.openmoko.org/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz
=> `/home/xraver/moko/sources/git_git.openmoko.org.git.kernel.git_4194.tar.gz'
Risoluzione di downloads.openmoko.org in corso... 88.198.93.219
Connessione a downloads.openmoko.org|88.198.93.219:80... connesso.
HTTP richiesta inviata, aspetto la risposta... 404 Not Found
08:47:41 ERRORE 404: Not Found.
</pre>

In this location http://downloads.openmoko.org/sources/ the file git_git.openmoko.org.git.kernel.git_4194.tar.gz does not exist.
Any solutions?

--[[User:xraver|Giorgio Ravera]]

I get a similar error
<pre>
NOTE: package linux-openmoko-2.6.24+git0+855f715f8568a50391d1526ab2954925c08dab79: started
NOTE: package linux-openmoko-2_2.6.24+git0+855f715f8568a50391d1526ab2954925c08dab79-r2: task do_fetch: started
fatal: The remote end hung up unexpectedly
fatal: Fetch failure: git://git.openmoko.org/git/kernel.git
NOTE: Running task 1268 of 7057 (ID: 4365, /home/vale/moko/openembedded/packages/libpng/libpng-native_1.2.20.bb, do_package_stage)
NOTE: Task failed: Fetch failed: Fetch command export PATH=/home/vale/moko/build/tmp/staging/x86_64-linux/usr/bin/arm-angstrom-linux-gnueabi:/home/vale/moko/build/tmp/staging/x86_64-linux/usr/sbin:/home/vale/moko/build/tmp/staging/x86_64-linux/usr/bin:/home/vale/moko/build/tmp/cross/bin:/home/vale/moko/build/tmp/staging/x86_64-linux/sbin:/home/vale/moko/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games; git fetch git://git.openmoko.org/git/kernel.git stable failed with signal 128, output:
fatal: The remote end hung up unexpectedly
fatal: Fetch failure: git://git.openmoko.org/git/kernel.git

NOTE: package linux-openmoko-2_2.6.24+git0+855f715f8568a50391d1526ab2954925c08dab79-r2: task do_fetch: failed
ERROR: TaskFailed event exception, aborting
NOTE: package linux-openmoko-2.6.24+git0+855f715f8568a50391d1526ab2954925c08dab79: failed
ERROR: Build of /home/vale/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb do_fetch failed
...
ERROR: Task 911 (/home/vale/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb, do_fetch) failed
...
NOTE: Tasks Summary: Attempted 1265 tasks of which 1258 didn't need to be rerun and 1 failed.
ERROR: '/home/vale/moko/openembedded/packages/linux/linux-openmoko_2.6.24+git.bb' failed
NOTE: build 200808080806: completed
make: *** [openmoko-devel-image] Fehler 1
</pre>

--[[User:bubbas|bubbas]]

I have the same error as bubbas... any ideas?

--[[User:jas|jas]]

== Wishlist: Make qemu optional ==

Hi,

I’ve just set up MokoMakefile, and after <tt>make setup</tt> I tried to get a package with <tt>make build-package-openmoko-messages2</tt>, but it’s spending a lot of time and disk space on building native libraries and qemu – something that I have not asked for. It would be nice if I could build packages for my phone without having to build unneccessary stuff.

Thanks,
Joachim

== SVN Certificate issues for Gentoo users ==

Note for Gentoo users: I think Portage creates a ~/.subversion directory as root if you've ever compiled a svn ebuild via "sudo emerge". If this happens, certificates won't be saved, so you have to take back ownership of the directory:

<pre>
chown -R $USER ~/.subversion
</pre>

Before running a svn co from the openmoko svn server to accept the certificate, otherwise the authentication information will not be saved.
[[User:Kelvie|kelvie]] 06:05, 18 July 2008 (UTC)

GSM

2007-08-03T09:43:37Z

Jas: /* GSM 07.05 - Additional AT commands (SMS and CBS) */

'''GSM''', ([http://en.wikipedia.com/wiki/GSM Global System for Mobile communications]) is the phone standard and network type supported by the [[Neo1973]]. Future phones may support other standards.

GSM covers making phone calls, sending '''SMS''' text messages, and access to Internet via '''GPRS'''. A '''SIM''' ([http://en.wikipedia.org/wiki/Subscriber_Identity_Module Subscriber Identity Module]) card is given along the contract with an operator, and the customer inserts the card in the phone to authorize it. The card is plastic (approximately 15mm*23mm*1mm) with several gold contacts on, and it determines the mobile phone 'number' and what network the phone is on.

The Neo1973 phone can be used with any operator that has a GSM network; it is quad-band and thus supports every frequency (850, 900, 1800, and 1900 MHz). Thus it will work in most countries, with the exception of some of the US and some other parts of the world that completely lack GSM coverage.

== Applications ==

Calls can be placed using the graphical [[Dialer]] or the textual gsmd-tool.

Rest needs to be done on the command-line [[manually using GSM]] and [[manually using GPRS]], until [[gsmd]] supports more.

== Programming ==

The GSM features (including dialing, SMS, GPRS, and SIM access) will be programmed via [[gsmd]].

== Standards information ==

You can find a full list of GSM/3GPP standards at [http://webapp.etsi.org/key/key.asp?full_list=y this ETSI site] (attention! more than 2000 entries) or at [http://pda.etsi.org/pda/queryform.asp the light-weight ETSI site].

=== GSM 02.07 - Required features ===

See [[GSM02.07]].

=== GSM 07.07 - Main AT commands ===

07.07 describes the main commands used by the [[Gsmd]] software of the Openmoko system to communicate via a serial interface with the [[GSM]] subsystem of the phone.

* http://www.ctiforum.com/standard/standard/etsi/0707.pdf

For more, see [[Hardware:AT Commands]].

Note that the descendant of this specification is [http://www.3gpp.org/ftp/Specs/html-info/27007.htm 3GPP TS 27.007 - AT command set for User Equipment (UE)]. (Does OpenMoko support any of these newer versions?)

=== GSM 07.05 - Additional AT commands (SMS and CBS) ===

* http://www.ctiforum.com/standard/standard/etsi/0705.pdf

A more user-friendly resource is:

* http://www.developershome.com/sms/

=== GSM 07.10 - Multiplexing ===

* direct link?

{{Languages|SIM}}
[[Category:Applications]]
[[Category:Hardware]]

MokoMakefile

2007-08-02T00:36:20Z

Jas: /* QEMU */

==MokoMakefile==
MokoMakefile is a fully automated way of setting up an OpenMoko development environment. It is an invaluable tool for getting new developers up and running with a build environment which is configured the same as all the other existing developers. It brings the same repeatability to build environment creation and maintenance as that which OpenEmbedded brings to the main task of actually building embedded software distributions.

Note that MokoMakefile does *not* replace bitbake, or svn, or monotone, or openembedded, or qmake, or anything else. It is a wrapper around all that to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by OpenMoko. Note that you need about 7 GB of available disk space for MokoMakefile to succeed. Please check that your RAM + swap partition space is greater than 512 MB (around 1GB?).

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of OpenMoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Building_OpenMoko_from_scratch|official OpenMoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

=== Before you begin ===
'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

If you have previously built with dash as your sh shell then your perl compile is probably broken. One symptom is that the build will error and whine about an 'Unterminated quote string'. Another symptom is a message that says 'You haven't done a "make depend" yet!' If you get these then you need to:
make clean-package-perl
make clean-package-perl-native
and rebuild.

If all else fails then just rm -rf the perl work dir and the perl stamps. Here's an i686 host example:
rm -rf build/tmp/work/i686-linux/perl-native-5.8.7-r3
rm -f build/tmp/stamps/i686-linux/perl*

As of r99, MokoMakefile has patches which should make it build correctly with dash.

You need to get mtn and svn for make.
sudo apt-get install subversion monotone

=== Installation ===
Here are the steps to use it:

1 - Make sure your build host is set up according to:
http://www.openembedded.org/wiki/OEandYourDistro
2 - Create your $OMDIR directory (note that you can change ~/moko to any directory you like):
mkdir ~/moko ; cd ~/moko
3 - Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.nslu2-linux.org/svnroot/mokomakefile/trunk/Makefile
4 - Set up the environment:
make setup
5 - Start building. Before starting a lengthy make process, check in Tips section about how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image

This will set up the recommended directory structure as described in [[Building OpenMoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

===Updating the environment===
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To update the OpenMoko repository checkout and the MokoMakefile patches to the latest version:
make update

3 - To make sure that any recent changes to the build directory structure have been applied:
make setup

A quick way to rebuild a new image with the latest updates:
make update-makefile && make update setup openmoko-devel-image

===Reporting Problems===

First, make sure that the problem is reproducible after running

make update-makefile ; make update ; make setup

then running

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

then running

make all

If you can get the error to occur three times in a row after running that sequence of commands three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].

===Work-arounds===

Work-arounds for temporary or isolated problems should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

===Tips===
*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly.

*If you an encounter an error with monotone similar to the following:
mtn: misuse: database /home/''username''/moko/OE.mtn is laid out according to an old schema
Then you need to upgrade OE.mtn Use the following command while in ~/moko:
# mtn --db OE.mtn db migrate

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

*For amd64 host users you need the patch from http://bugs.openembedded.org/show_bug.cgi?id=1765 to build db3-native

===QEMU===
The MokoMakefile now has support for automatically building, flashing, and running [[OpenMoko under QEMU|the new Neo1973 emulator]] (which is based on QEMU).

Dependencies:

*gcc 3.4 or 3.3 ('apt-get install gcc-3.4' in Ubuntu 7.04)
*lynx ('apt-get install lynx' in Ubuntu 7.04)
*netpbm ('apt-get install netpbm' in Ubuntu 7.04)
*sdl-devel ('apt-get install libsdl1.2-dev in Ubuntu .704')
*mkdosfs ('apt-get install dosfstools' in Debian 4.0)

“'''make qemu'''” will build qemu-neo1973, download the latest official OpenMoko images, flash the images into the virtual NAND flash, create an empty virtual SD card, and run the emulator (you still need to install the makefile as mentioned above, however).

Other targets are “'''make download-images'''” (to download the latest official images), “'''make flash-qemu-official'''” (to flash those images) and “'''make flash-qemu-local'''” (which will flash your latest locally built images), which can then be followed by “''''make run-qemu'''” or “'''make run-qemu-snapshot'''” to run the emulator with the most recently flashed images. You can also use “''''make qemu-copy-package-''foo'''''” to copy the <code>.ipk</code> file for package ''foo'' to the virtual SD card, and later use “''''ipkg install /media/mmcblk0/''file'''''” from within the emulated Neo1973 to install the package.

Make sure you have the “lynx” and “netpbm” packages installed on your build host first.

You're also invited to read more about how to run [[OpenMoko under QEMU]] in the article dedicated to this subject.

===Developing with MokoMakefile===

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR
. ./setup-env
cd build
bitbake -c unpack openmoko-messages
cd ../build/tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
...make the changes...
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/oe/packages/mycoolpackage
quilt add trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/oe/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update all

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [http://wiki.openmoko.org/wiki/Building_a_hello_world_application Hello World!] tutorial available too.

===Testimonials===
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", and "MokoMakefile rocks!".

Project page:
http://mokomakefile.projects.openmoko.org/

{{Languages|MokoMakefile}}

[[Category:Developer]]
[[Category:Guides]]

User:Jas

2007-07-31T15:58:13Z

Jas: Initial version

Simon Josefsson, http://josefsson.org/

* OpenMoko interests:
** Creating a crypto-GSM phone
** Controlling EIB/KNX-controlled intelligent house systems

Neo1973 compatible cellphone providers

2007-07-15T06:51:38Z

Jas: add info for sweden

{|align=right
|__TOC__
|}
The Neo1973 uses quad-band [[GSM]] (850/900/1800/1900 MHz) so any GSM provider in the world should be compatible. In general, when you are looking for a mobile solution in your region, you would need to be aware of:
* the ''network coverage'' of available providers
* different ''tariffs'' of these providers
and choose the one that is right for you. If you haven't had any experience with GSM coverage in your area, you may want to inquire locally from the available providers and people you know that may already have experienced GSM at your location. You may also want to subscribe to our mailing list. If you have doubts about the coverage for your area, you may want to borrow a GSM phone or buy an inexpensive one so that you can get a feel for how the Neo1973 will work in your area. You can help keep your cost down by using a prepaid card for your testing.

Here is some information on Prepaid GSM cards:
* [http://www.prepaidgsm.net/ PrePaidGSM - worldwide overview about GSM prepaid offers]
Think twice before choosing a tariff with long duration contracts (more than 12 months), because prices for the GPRS data tariffs are ''likely'' to lower in many countries. Also, long duration contracts are mostly combined with hardware (ie: free or steeply discounted phone with a 24 or 36 month contract). It will be worth your while to shop around for competing offers from the different providers in your area.

We chose the GSM network format for the Neo1973 because GSM is in use by more countries than any other mobile phone standard. As a result, you will have better coverage with the Neo1973, and we felt that it was the best choice for our OpenMoko devices. When the Neo1973 is successful, and we believe that it will be, we will be developing new devices that we will be bringing to market. They will be running OpenMoko and supporting additional mobile phone network standards as well. So if GSM is not available in your area (ie: some areas in the USA), OpenMoko will be bringing other options to market in the future.

Below is a list of Neo1973-compatible providers around the world. Please help by filling this out ''alphabetically'':

== Canada ==
* [http://www.fido.ca/ Fido]
* [http://www.icewireless.ca/ IceWireless]
* [http://www.rogers.ca/ Rogers]

== China ==
* China Mobile
* China Unicom (CHINA UNICOM GSM)

== Czech Republic ==

* [http://www.vodafone.cz/ Vodafone]
* [http://www.cz.o2.com/ o2]
* [http://www.t-mobile.cz/ T-mobile]

== Denmark ==
* Sonofon ([http://www.sonofon.dk/english/index.shtml English] - [http://www.sonofon.dk/ Danish])
* TDC A/S ([http://tdc.com English] - [http://privat.tdc.dk/mobil/ Danish])
* Telia DK ([http://telia.dk/privat/produkter/mobil/ Danish])

== Estonia ==

* [http://www.emt.ee/ EMT]
* [http://www.tele2.ee/ Tele2] - Very low rates for GPRS. You can get 3GB of bandwidth for 675EEK(~43€) per month.
* [http://www.elisa.ee/ Elisa] - With M-internet plan you get free access to Elisa wifi hotspots

== Finland ==

* [http://www.cubio.fi Cubio]
* [http://www.dnafinland.fi Dna] - Also a roaming network operator (Network operated under the name Dna Networks Ltd)
* [http://www.elisa.fi Elisa] - Also a roaming network operator.
* [http://www.go.fi Go mobile]
* [http://www.hesburger.fi/heseliittyma/ Hesburger] - Do you want sim card(s) with that?
* [http://www.kolumbus.fi Kolumbus] - Strangely they don't offer their website in English, but they're a part of the Elisa.
* [http://www.teliasonera.com Teliasonera] - Also a roaming network operator.
* [http://www.tele.fi Telefinland] - They haven't got an English site, but they're part of the Teliasonera.
* [http://www.gsm.aland.fi/ Ålands Mobiltelefon] - Only in the Åland Islands in the southwestern Finland. Also a roaming network operator.

== France ==

All:
* [http://www.sfr.fr SFR]
* [http://www.bouyguestelecom.fr/ Bouygues]
* [http://www.orange.fr Orange]

== Germany ==
All:
* [http://www.vodafone.de/ Vodafone]
* [http://www.o2online.de/ o2]
* [http://www.eplus.de/ E-Plus]
* [http://www.t-mobile.de/ T-mobile]
== India ==
All GSM:
* Airtel
* Vodafone
* [http://www.ideacellular.com/ Idea]
* Reliance GSM
* BPL Mobile
* Spice

== Japan ==

According to the [http://www.gsmworld.com/roaming/gsminfo/cou_jp.shtml GSM-Association] there is no GSM in Japan, except for UMTS.

== Latvia ==
* [http://www.lmt.lv/ LMT]
* [http://www.bite.lv/ Bitė]
* [http://www.tele2.lv/ Tele2]

== Lithuania ==
* [http://www.omnitel.lt/ Omnitel]
* [http://www.bite.lt/ Bitė]
* [http://www.tele2.lt/ Tele2]

== Netherlands ==
All.
* [http://www.vodafone.nl/ Vodafone]
* [http://www.telfort.nl/ Telfort]
* [http://www.orange.nl/ Orange]
* [http://www.t-mobile.nl/ T-mobile]
* [http://www.kpn.com/mobiel KPN]
* [http://www.hi.nl/ Hi]
(There are more)

For a breakdown of SIM-only plans, go to [http://www.bellen.com/mobiel_overzicht/default.asp?taal=nl&land=nl&prgr=4 Bellen.com]

== New Zealand ==
* [http://www.vodafone.co.nz/ Vodafone]

== Norway ==
* [http://www.netcom.no/ NetCom] (GSM900/1800 & UMTS)
* [http://www.networknorway.no/ Network Norway] (GSM900)
* [http://www.telenormobil.no/ Telenor] (GSM900/1800 & UMTS)

== Poland ==

* [http://www.eragsm.pl/ Era]
* [http://www.plusgsm.pl/ Plus]
* [http://www.orange.pl/ Orange] - europe wide provider
* [http://www.playmobile.pl/ Play]

== Romania ==

* [http://www.vodafone.ro Vodafone] (226-01; GSM900)
* [http://www.orange.ro Orange] (226-10; GSM900)
* [http://www.cosmote.com Cosmote] (226-06; GSM1800)

* [http://www.zapp.ro/ Zapp] is running CDMA (Qualcomm style) and as such it is incompatible with [[Neo1973]].

== Russia ==
=== global ===
* [http://www.beeline.ru/ Билайн]/BeeLine (GSM900/1800)
* [http://megafon.ru/ МегаФон]/MegaFon (GSM900/1800)
* [http://www.mts.ru МТС]/MTS (GSM900/1800)
=== regional ===
* [http://www.smarts.ru/ СМАРТС]/SMARTS (GSM900/1800)
* [http://wwwtele2.ru TELE2] (GSM900/1800)
* [http://www.u-tel.ru/ Ютел]/Utel (GSM900/1800)
* [http://www2.sibirtelecom.ru/857 Сибирьтелеком]/Sibirtelecom (GSM-900/1800)
* [http://www.ncc.nnov.ru/ НСС]/NSS (GSM900/1800)
* [http://www.bwc.ru/ Байкалвестком]/Baykalvestcom (GSM900/1800)

== Slovak Republic ==
All:
* [http://www.orange.sk/ Orange]
* [http://www.sk.o2.com/ o2]
* [http://www.t-mobile.sk/ T-mobile]

== South Africa ==

* [http://www.vodacom.co.za/ Vodacom]
* [http://www.mtn.co.za/ MTN]
* [http://www.cellc.co.za/ Cell C]

== Sweden ==

Operators with their own physical networks:
* [http://comviq.se/ Comviq/Tele2]
* [http://www.telia.se/ Telia]
* [http://www.tre.se/ 3]
* [http://www.telenor.se Telenor]

Virtual Operators:
* [http://www.tangomini.se TangoMini]
* [http://www.halebop.se Halebop]
* [http://www.djuice.se Djuice]

== Switzerland ==
(all)
* [http://www.swisscom-mobile.ch/ Swisscom Mobile]
* [http://www.sunrise.ch/ Sunrise]
* [http://www.orange.ch/ Orange]

== Taiwan ==

* Chunghwa Telecom
* Far EasTone Telecommunications Co Ltd
* KG Telecom
* MobiTai
* Taiwan Mobile Co.Ltd

== Ukraine ==
* [http://www.umc.ua/ UMC] (including virtual [http://www.jeans.com.ua/ Jeans], [http://www.ekotel.com.ua/ Ecotel])
* [http://www.kyivstar.net/ Kyivstar] (including virtual [http://www.djuice.com.ua/ DJUICE], [http://mobilych.com.ua/ Mobilych])
* [http://www.life.com.ua/ life:)]
* [http://www.beeline.ua/ Beeline]
* [http://gsm.goldentele.com/ Golden Telecom]
* [http://www.privatmobile.com.ua/ PrivatMobile]

== United Kingdom ==
* [http://www.vodafone.co.uk/ Vodafone]
* [http://www.o2.co.uk/ O2]
* [http://www.orange.co.uk/ Orange]
* [http://www.t-mobile.co.uk/ T-mobile]
* [http://www.three.co.uk/ 3]

== United States ==

* [http://cingular.com/ AT&T] - (Was Cingular)
* [http://t-mobile.com/ T-Mobile]
* Other (more local) GSM-network providers can be found at [http://www.gsmworld.com/roaming/gsminfo/cou_us.shtml GSMworld.com]
* [http://www.unicel.com/ UNICEL] - A provider that has GPRS and EDGE in many parts of Northeast / New England. Coverage in ME, VT, NH, MA, NY. It is not listed at GSMworld. 850/1900 bands.
* Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. Only GSM networks are compatible with the Neo1973.
* [http://www.prepaidgsm.net/en/usa.html PrepaidGSM.net information about GSM prepaid cards in the USA]

== Uruguay ==

* [http://www.ancel.com.uy/ Ancel] -

== Venezuela ==

* [http://www.digitel.com.ve/ Digitel] - This works on the 900Mhz band.
* [http://www.movistar.com.ve/ Movistar] - Previously named Telcel. It is moving from CDMA to GSM, but currently all its new phones are GSM. They work on the 850 Mhz band.

== Rest of World (Africa, Asia, Australia, Europe, South America) ==

* almost all use GSM thus they are compatible

(More info available at: [http://www.gsmworld.com/roaming/gsminfo/index.shtml GSMworld.com])
{{Languages|Neo1973_compatible_cellphone_providers}}