BuildingImage - Revision history

B-flat at 17:30, 21 July 2009

2009-07-21T17:30:02Z

B-flat: /* My Build system */

2009-07-21T12:46:11Z

‎My Build system

B-flat: /* Failing build when building the java development */

2009-07-08T13:17:06Z

‎Failing build when building the java development

B-flat: /* ERROR: Exception: Message:do_split_packages() got an unexpected keyword argument 'allow_links' */

2009-07-08T13:15:56Z

‎ERROR: Exception:<type 'exceptions.TypeError'> Message:do_split_packages() got an unexpected keyword argument 'allow_links'

B-flat at 13:17, 18 June 2009

2009-06-18T13:17:15Z

B-flat: /* Building an Rootfs image and a kernel */

2009-06-18T13:14:24Z

‎Building an Rootfs image and a kernel

B-flat: /* Building an Rootfs image and a kernel */

2009-06-18T13:13:00Z

‎Building an Rootfs image and a kernel

B-flat: /* Building an Rootfs image and a kernel */

2009-06-18T13:11:08Z

‎Building an Rootfs image and a kernel

B-flat: /* My Build system */

2009-06-07T19:47:05Z

‎My Build system

B-flat: /* My Build system */

2009-06-07T18:39:41Z

‎My Build system

@@ Line 8: / Line 8: @@
 The reason for choosing the open-embedded as for Overo is that the Verdex buildsystem has not been updated for approx. a year now and I wanted the latest recipes to get e.g. Open JDK.
 == Building an Rootfs image and a kernel==
@@ Line 17: / Line 15: @@
   ~/overo-oe/
-Then, make sure that the machine selected is gumstix-verdex and copy the gumstix-cumstom-verdex machine def to gumstix-verdex to avoid problems when building some packages.
+Then, make sure that the machine selected is gumstix-custom-verdex. The machine is defined in the file ~/overo-oe/build/conf/auto.conf. Change it to be:
- # cp ~/overo-oe/org.openembedded.dev/conf/machine/gumstix-custom-verdex.conf  ~/overo-oe/org.openembedded.dev/conf/machine/gumstix-verdex.conf
-−
 The machine is defined in the file ~/overo-oe/build/conf/auto.conf. Change it to be:
-  MACHINE = "gumstix-verdex"
+  MACHINE = "gumstix-custom-verdex"
-Then, I copied the Verdex image recipes to the user.collection.
+Then, I copied the Verdex image recipes to the user.collection. First, make the directory.
-  mkdir -p ~/overo-oe/user.collection/images/
+  mkdir -p ~/overo-oe/user.collection/images/linux
-  cp ~/gumstix/gumstix-oe/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/
+ cd ~/overo-oe/user.collection/images/linux/
 Once copied, I ran:
-  bitbake gumstix-basic-image
+  bitbake gumstix-kernel
 Resulting in a failure and Bitbake reporting that nothing provides some package and exited without building anything. I then copied the recipes for those packages and ran bitbake again. At the end I had copied:
@@ Line 38: / Line 35: @@
   www-content
 ===Gumstix-kernel and sumversion.c ===
@@ Line 94: / Line 94: @@
 ==undefined reference to `__aeabi_uldivmod' in utsname_sysctl.c ==
-In Omap kernel the problem has been solved.
+This seems to be related to the gcc version that fails. The following version works for gumstix-oe, so we go for that.
-More info from [http://bugs.openembedded.net/show_bug.cgi?id=4333| here]
+PREFERRED_VERSION_gcc-cross = "4.1.2"
-−
-Copy the patch from
-  # cd ~/overo-oe/org.openembedded.dev/recipes/linux/linux-omap1-2.6.24-omap1
-  # cp timespec_add_ns_avoid_udivdi3.patch ../gumstix-kernel-2.6.21/
-−
-In the gumstix-kernel_2.6.21.bb add to the list of files in SRC_URI the following line:
-−
-       file://timespec_add_ns_avoid_udivdi3.patch;patch=1 \
-−
-In the patch file change change so that the relative paths are OK:
- --- linux-2.6.21.orig/include/linux/time.h      2008-05-28 15:39:46.000000000 -0700
- +++ linux-2.6.21/include/linux/time.h   2008-05-28 15:40:48.000000000 -0700

← Older revision		Revision as of 12:46, 21 July 2009
Line 1:		Line 1:
		+	=NOT YET BUILDING A WORKING KERNEL AND IMAGE THIS WAY=
		+	This page describes efforts so far to build gumstix kernel and X11 image with java support using the the overo-oe repository instead of gumstix-oe. However, this does not yet produce a working kernel and image. You have been warned!
		+
	==My Build system==		==My Build system==
	I am running a VM-ware player image with Gentoo Linux placed on a USB hostpowered disc. This does not give highest possible performance, but it allows for a lot of mobility and portability. Peripherals like a (micro)SD-card reader adapter for USB works fine, but the built-in one in my laptop is not available within the VM-ware player.		I am running a VM-ware player image with Gentoo Linux placed on a USB hostpowered disc. This does not give highest possible performance, but it allows for a lot of mobility and portability. Peripherals like a (micro)SD-card reader adapter for USB works fine, but the built-in one in my laptop is not available within the VM-ware player.

← Older revision		Revision as of 13:17, 8 July 2009
Line 127:		Line 127:
	emerge antlr		emerge antlr

−	Removing the tmp/work dir and then rebuilding fixed the problem. The intention seems to be to have self contained java environment in open embedded but antlr and antrl-native recipes seems to have a cyclic dependancy ~~still~~.	+	Removing the tmp/work dir and then rebuilding fixed the problem. The intention seems to be to have self contained java environment in open embedded but antlr and antrl-native recipes seems to have a cyclic dependancy so bitbaking these results in the same problem.

← Older revision		Revision as of 13:15, 8 July 2009
Line 118:		Line 118:

	Find out another solution here the problem [http://projects.linuxtogo.org/pipermail/openembedded-devel/2009-January/007481.html\| here]		Find out another solution here the problem [http://projects.linuxtogo.org/pipermail/openembedded-devel/2009-January/007481.html\| here]
		+
		+
		+	== Failing build when building the java development ==
		+
		+	Firts make sure you follow the instructions fo Java on the Openembedde wiki. [http://wiki.openembedded.net/index.php/Java Found here]
		+
		+	I used this and still had probles related to native antlr. The simple solution for me was to make sure that Antlr was part of my Gentoo linux by:
		+	emerge antlr
		+
		+	Removing the tmp/work dir and then rebuilding fixed the problem. The intention seems to be to have self contained java environment in open embedded but antlr and antrl-native recipes seems to have a cyclic dependancy still.

@@ Line 15: / Line 15: @@
 Then, make sure that the machine selected is gumstix-verdex and copy the gumstix-cumstom-verdex machine def to gumstix-verdex to avoid problems when building some packages.
-  # cp ~/overo-oe/org.openembedded.oe/conf/machine/gumstix-custom-verdex.conf  ~/overo-oe/org.openembedded.oe/conf/machine/gumstix-verdex.conf
+  # cp ~/overo-oe/org.openembedded.dev/conf/machine/gumstix-custom-verdex.conf  ~/overo-oe/org.openembedded.dev/conf/machine/gumstix-verdex.conf
 The machine is defined in the file ~/overo-oe/build/conf/auto.conf. Change it to be:

@@ Line 23: / Line 23: @@
 Then, I copied the Verdex image recipes to the user.collection.
   mkdir -p ~/overo-oe/user.collection/images/
-  cp ~/gumstix/gumstix-stable/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/
+  cp ~/gumstix/gumstix-oe/com.gumstix.collection/packages/images/* ~/overo-oe/user.collection/images/
 Once copied, I ran:
@@ Line 40: / Line 40: @@
   warning: unused variable 'filelist'
 The problem can be solved by adding '#include <limits.h>' after strings.h in scripts/mod/sumversion.c fixes the issue. The file is found at:
-~/overo-stable/tmp/work/gumstix-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r0/linux-2.6.21/scripts/mod/sumversion.c
+~/overo-oe/tmp/work/gumstix-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r0/linux-2.6.21/scripts/mod/sumversion.c
   #include <netinet/in.h>
@@ Line 60: / Line 60: @@
 Or by copying a patch from
-  # cd ~/overo-stable/org.openembedded.dev/recipes/linux
+  # cd ~/overo-oe/org.openembedded.dev/recipes/linux
   # cp  files/linux-2.6-limits.patch gumstix-kernel-2.6.21/

@@ Line 6: / Line 6: @@
 The reason for choosing the open-embedded as for Overo is that the Verdex buildsystem has not been updated for approx. a year now and I wanted the latest recipes to get e.g. Open JDK.
-Currently I can successfully build the gumstix-kernel, the gumstix-basic-image, but has stuck on creating a java runtime with working AWT support.
+Currently I can successfully build the gumstix-kernel, the gumstix-basic-image, and the gumstix-x11-32mb-image but has stuck on creating a java runtime with working AWT support.
 == Building an Rootfs image and a kernel==

← Older revision		Revision as of 18:39, 7 June 2009
Line 5:		Line 5:

	The reason for choosing the open-embedded as for Overo is that the Verdex buildsystem has not been updated for approx. a year now and I wanted the latest recipes to get e.g. Open JDK.		The reason for choosing the open-embedded as for Overo is that the Verdex buildsystem has not been updated for approx. a year now and I wanted the latest recipes to get e.g. Open JDK.
		+
		+	Currently I can successfully build the gumstix-kernel, the gumstix-basic-image, but has stuck on creating a java runtime with working AWT support.

	== Building an Rootfs image and a kernel==		== Building an Rootfs image and a kernel==