[Angstrom-devel] Building Angstrom with a different kernel
I want to build a BeagleBoard (OMAP) Angstrom with a 2.6.31 kernel. I followed the instructions on the "building-angstrom", bitbake base-image, and successfully built Angstrom with the 2.6.32 kernel. I then executed... bitbake -f -c build linux-omap_2.6.31 It looks like the 2.6.31 kernel built, but I received a message from bitbake stating that two recipes were executed that generate virtual/kernel. For some reason bitbake chose to also execute linux-omap-psp_2.6.32.bb. The message goes on to state that one recipe probably provides something that the other should provide. The are no PROVIDES statements in either linux-omap_2.6.31.bb or linux-omap-psp_2.6.32.bb. Why would building the linux-omap_2.6.31 target require something from the 2.6.32 recipe? How can I determine what this missing provided thing is in 2.6.31? Regards, Bob Feretich ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Problem building beagleboard demo image, pyorbit-2.24.0-r1 fails.
Koen's right gcc vectorization is terrible. You don't need to build the Angstrom image with the Neon enabled to use Neon instructions in your programs. Build Angstrom with the standard gcc compiler options. Then, when you compile your programs for the Neon, reference the Angstrom compiler, but add the -mfpu=neon -mfloat-abi=softfp flags to the compiler. I recommend staying with -mfloat-abi=softfp. This flag controls how floating point data is passed to subroutines, so it won't effect performance except on the entrance/exit of these routines. I have seen multiple inquires made on the CodeSourcery-Arm alias dealing with the -mfloat-abi=hard option. It doesn't work in CodeSourcery-Lite, which is basically GNU gcc. They talk about special premium libraries being needed to make it functional. To use the Neon effectively, programs need to be structured specifically for the Neon. I recommend either using the Neon Intrinsics or inserting Neon assembler instructions into the gcc program. The intrinsics sometimes generate extra vmov instructions and have a have difficulty updating in-place (e.g. matrix transpose without using additional work variables). To program effectively in gcc assembly you will need to use some undocumented gcc constraints (see http://hardwarebug.org/2010/07/06/arm-inline-asm-secrets/). Regards, Bob Feretich On 2/20/2011 3:00 AM, angstrom-distro-devel-requ...@linuxtogo.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 20-02-11 17:05, Jonathan Wilson wrote: >/ On Sun, 2011-02-20 at 09:14 +0100, Koen Kooi wrote: />>/ -BEGIN PGP SIGNED MESSAGE- />>/ Hash: SHA1 />>/ />>/ On 19-02-11 20:28, Jonathan Wilson wrote: />>>/ Bitbake bombs out with:- />>>/ />>>/ ERROR: Build />>>/ of /home/wilsonjonathan/oebeagle/angstrom-setup-scripts/sources/openembedded/recipes/gnome/pyorbit_2.24.0.bb do_configure failed />>>/ ERROR: Task 8977 />>>/ (/home/wilsonjonathan/oebeagle/angstrom-setup-scripts/sources/openembedded/recipes/gnome/pyorbit_2.24.0.bb, do_configure) failed with exit code 1 />>>/ />>>/ Changes manually made to files before compilation. />>>/ />>>/ local.conf />>>/ BB_NUMBER_THREADS = "2" />>>/ />>>/ DISTRO = "angstrom-2010.x" />>>/ MACHINE ?= "beagleboard" />>>/ />>>/ # Set TMPDIR instead of defaulting it to /tmp />>>/ TMPDIR = />>>/ "/home/wilsonjonathan/oebeagle/angstrom-setup-scripts/build/tmp-angstrom_2010.x" />>>/ />>>/ tune-cortexa8.inc />>>/ ARM_FP_MODE ?= "hardfp" />>/ />>/ Why are you changing that there? You are supposed to set that in local.conf />/ />/ Total lack of understanding of the language used in .bb files. Re: "?=" />/ which I'm guessing does mean if variable is not set then set it. />/ />/ I'm not a pc programmer, AS/400's application programmer by trade, but />/ rather a hobbyist playing around with arm linux since getting some />/ rather cool NAT's to store my photo library. />/ />>/ />>>/ To produce hard float, -funsafe... was added due to a note on the TI />>>/ website. />>/ />>/ It works well without that flag, which website told you to add it? />/ />/ As per the gcc website : />/ http://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html />/ />/ If the selected floating-point hardware includes the NEON />/ extension (e.g. -mfpu=`neon'), note that floating-point />/ operations will not be used by GCC's auto-vectorization pass />/ unless -funsafe-math-optimizations is also specified. This is />/ because NEON hardware does not fully implement the IEEE 754 />/ standard for floating-point arithmetic (in particular denormal />/ values are treated as zero), so the use of NEON instructions may />/ lead to a loss of precision. />/ />/ Which as I read it means that it wont vectorise causing a possible />/ performance hit, although its debatable how much of difference in />/ performance there would be in practise. / The vectorizer in gcc sucks, so in the rare cases when it vectorizes, it generally is a lot slower than plain old vfp. The default sets in angstrom are basically as fast as you can safely get :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFNYUCJMkyGM64RGpERAkqXAJ4x5a0zkiiesfXMAYalM5uXeTX8RwCeNVJS BIwEqDc0njaSITdlI/9IhXk= =jvOi -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Getting the SDK for the stable release
I want to develop packages specifically for the "stable" version of angstrom (currently using the 2.6.32 kernel). However, in Narcissus, when I select "advanced" so that I can generated a sdk , I am not able to select the stable branch. How can I build a development environment with a C compiler and libraries that are compatible with the stable version of angstrom? Regards, Bob Feretich ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Building Angstrom base-image fails
Is base-image still a supported Angstrom image for the BeagleBoard? I have just migrated from a two year old version of OE/Angstrom and was able to build nano, but building base-image (the image I previously used) failed. [Bob@beagleboard setup-scripts]$ MACHINE=beagleboard ./oebb.sh update ; MACHINE=beagleboard ./oebb.sh bitbake nano > ~/L110226BuildNano1.txt The above bitbake worked successfully. Then I tried... [Bob@beagleboard setup-scripts]$ source ~/.oe/environment [Bob@beagleboard setup-scripts]$ bitbake base-image > ~/L110226BuildBase2.txt ... Build Configuration: BB_VERSION= "1.12.0" METADATA_BRANCH = "org.openembedded.dev" METADATA_REVISION = "50e7d72" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beagleboard" DISTRO= "angstrom" DISTRO_VERSION= "2010.7-test-20110227" TARGET_FPU= "hard" ... | mv -f .deps/modinfo.Tpo .deps/modinfo.Po | gcc -isystem/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -O2 -g -Wunused -Wall -L/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath-link,/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath,/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-O1 -o modinfo modinfo.o zlibsupport.o libmodtools.a | gcc -isystem/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -O2 -g -Wunused -Wall -static -L/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath-link,/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath,/media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-O1 -o insmod.static insmod.o libmodtools.a | /usr/bin/ld: cannot find -lc | collect2: ld returned 1 exit status | make: *** [insmod.static] Error 1 | + die 'oe_runmake failed' | + oefatal 'oe_runmake failed' | + echo FATAL: 'oe_runmake failed' | FATAL: oe_runmake failed | + exit 1 NOTE: package module-init-tools-cross-3.12-r6: task do_compile: Failed ERROR: Function 'do_compile' failed (see /media/LINUX/AngstromDist7/setup-scripts/build/tmp-angstrom_2008_1/work/armv7a-angstrom-linux-gnueabi/module-init-tools-cross-3.12-r6/temp/log.do_compile.19546 for further information) ERROR: Task 1540 (/media/LINUX/AngstromDist7/setup-scripts/sources/openembedded/recipes/module-init-tools/module-init-tools-cross_3.12.bb, do_compile) failed with exit code '1' ... .. 69% 162K 2m49s Any idea what is wrong? Regards, Bob Feretich ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Trouble building a single kernel driver module for Angstrom
Previously, I used the below recipe to build a kernel module (.ko) for a
driver that I wrote for the BeagleBoard.
Since I upgraded to the new OE/Angstrom tree it has stopped working and
is showing the most confusing symptoms. There must have been some
fundamental change in the way OE builds these modules, but my google
searches have not provided any clues on what changed.
Recipe:
DESCRIPTION = "Kernel driver to control digital servomotors."
HOMEPAGE = "http://www.rafresearch.com";
SECTION = "kernel/modules"
PRIORITY = "optional"
LICENSE = "none"
#added by Bob 20100805
KERNEL_VERSION="2.6.33"
#RDEPENDS = "kernel (${KERNEL_VERSION})"
RDEPENDS = "kernel (2.6.33)"
DEPENDS = "virtual/kernel"
PR = "r0"
SRC_URI = " \
file://rtservo-driver_1.0.0/rtservo-driver.c \
file://rtservo-driver_1.0.0/rtservo-driver.h \
file://rtservo-driver_1.0.0/servo-interface.h \
file://rtservo-driver_1.0.0/Makefile \
"
WORKDIR =
"${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules"
S = "${WORKDIR}/rtservo-driver_1.0.0"
inherit module
do_compile () {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS CC LD CPP
env
oe_runmake
'MODPATH="${D}${base_libdir}/modules/2.6.33/kernel/drivers/test"' \
'KERNEL_SOURCE="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KDIR="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KERNEL_VERSION="2.6.33"' \
'CC="${KERNEL_CC}"' \
'LD="${KERNEL_LD}"'
}
do_install () {
install -d ${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
install -m 0644 ${S}/rtservo-driver*${KERNEL_OBJECT_SUFFIX}
${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
}
Current results:
[Bob@beagleboard setup-scripts]$ bitbake -c compile -b
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb
Build Configuration:
BB_VERSION= "1.12.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "50e7d72"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO= "angstrom"
DISTRO_VERSION= "2010.7-test-20110228"
TARGET_FPU= "hard"
NOTE: Preparing runqueue
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 7 (ID: 3,
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb,
do_setscene)
NOTE: package rtservo-driver-1.0.0-r100: task do_setscene: Started
ERROR: Error executing a python function in
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb:
IOError: [Errno 2] No such file or directory:
'${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules/temp/run.staging_helper.30029'
It is creating the directory build/${OE_BASE} to operate in instead of
substituting the contents of the OE_BASE variable.
Even if I bypass that using a relative location, the same error appears.
(run.staging_helper.xxx not found. There is no run.staging_helper file
in the tmp directory, although the other run. files and log. files are
there.)
Does anyone have a current working recipe to build a single kernel
driver module? How does it differ?
Regards,
Bob Feretich
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Trouble building a single kernel driver module for Angstrom
I am overriding WORKDIR and do_compile because that is what the example
on the BeagleBoard forum provided (3 years ago). It just stopped working
when I upgraded.
I assume there is a better way to build this type of module with the
current tool chain, but I have not found a new example.
Do you have a link to a currently working recipe for building a single
kernel driver module?
Regards,
Bob
On 2/28/2011 12:11 AM, angstrom-distro-devel-requ...@linuxtogo.org wrote:
Date: Mon, 28 Feb 2011 09:08:21 +0100
From: Koen Kooi
Subject: Re: [Angstrom-devel] Trouble building a single kernel driver
module for Angstrom
To: angstrom-distro-devel@linuxtogo.org
Message-ID:
Content-Type: text/plain; charset=UTF-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why are you overriding WORKDIR and do_compile?
On 28-02-11 07:57, Bob Feretich wrote:
Previously, I used the below recipe to build a kernel module (.ko) for a
driver that I wrote for the BeagleBoard.
Since I upgraded to the new OE/Angstrom tree it has stopped working and
is showing the most confusing symptoms. There must have been some
fundamental change in the way OE builds these modules, but my google
searches have not provided any clues on what changed.
Recipe:
DESCRIPTION = "Kernel driver to control digital servomotors."
HOMEPAGE = "http://www.rafresearch.com";
SECTION = "kernel/modules"
PRIORITY = "optional"
LICENSE = "none"
#added by Bob 20100805
KERNEL_VERSION="2.6.33"
#RDEPENDS = "kernel (${KERNEL_VERSION})"
RDEPENDS = "kernel (2.6.33)"
DEPENDS = "virtual/kernel"
PR = "r0"
SRC_URI = " \
file://rtservo-driver_1.0.0/rtservo-driver.c \
file://rtservo-driver_1.0.0/rtservo-driver.h \
file://rtservo-driver_1.0.0/servo-interface.h \
file://rtservo-driver_1.0.0/Makefile \
"
WORKDIR =
"${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules"
S = "${WORKDIR}/rtservo-driver_1.0.0"
inherit module
do_compile () {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS CC LD CPP
env
oe_runmake
'MODPATH="${D}${base_libdir}/modules/2.6.33/kernel/drivers/test"' \
'KERNEL_SOURCE="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KDIR="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KERNEL_VERSION="2.6.33"' \
'CC="${KERNEL_CC}"' \
'LD="${KERNEL_LD}"'
}
do_install () {
install -d ${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
install -m 0644 ${S}/rtservo-driver*${KERNEL_OBJECT_SUFFIX}
${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
}
Current results:
[Bob@beagleboard setup-scripts]$ bitbake -c compile -b
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb
Build Configuration:
BB_VERSION= "1.12.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "50e7d72"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO= "angstrom"
DISTRO_VERSION= "2010.7-test-20110228"
TARGET_FPU= "hard"
NOTE: Preparing runqueue
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 7 (ID: 3,
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb,
do_setscene)
NOTE: package rtservo-driver-1.0.0-r100: task do_setscene: Started
ERROR: Error executing a python function in
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb:
IOError: [Errno 2] No such file or directory:
'${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules/temp/run.staging_helper.30029'
It is creating the directory build/${OE_BASE} to operate in instead of
substituting the contents of the OE_BASE variable.
Even if I bypass that using a relative location, the same error appears.
(run.staging_helper.xxx not found. There is no run.staging_helper file
in the tmp directory, although the other run. files and log. files are
there.)
Does anyone have a current working recipe to build a single kernel
driver module? How does it differ?
Regards,
Bob Feretich
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNa1f1MkyGM64RGpERAu1YAKCvUGzi0snCqaX5Agf42YbPW0s3KACgrvJk
HdEr+uZFhlJ1YJx/NLun9XE=
=giX4
-END PGP SIGNATURE-
--
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
End of Angstrom-distro-devel Digest, Vol 53, Issue 16
*
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building Angstrom base-image fails (solved)
Installing glibc-static fixed the problem. base-image built sucessfully. Thank you. Regards, Bob Feretich Date: Mon, 28 Feb 2011 09:06:00 +0100 From: Koen Kooi Subject: Re: [Angstrom-devel] Building Angstrom base-image fails To: angstrom-distro-devel@linuxtogo.org Message-ID: Content-Type: text/plain; charset=UTF-8 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28-02-11 02:46, Bob Feretich wrote: > Is base-image still a supported Angstrom image for the BeagleBoard? > > I have just migrated from a two year old version of OE/Angstrom and was > able to build nano, but building base-image (the image I previously > used) failed. > > [Bob@beagleboard setup-scripts]$ MACHINE=beagleboard ./oebb.sh update ; > MACHINE=beagleboard ./oebb.sh bitbake nano > ~/L110226BuildNano1.txt > > The above bitbake worked successfully. Then I tried... > > [Bob@beagleboard setup-scripts]$ source ~/.oe/environment > [Bob@beagleboard setup-scripts]$ bitbake base-image > > ~/L110226BuildBase2.txt > | /usr/bin/ld: cannot find -lc You're missing the 'glibc-static' package on your host. It should be a yum install away :) regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Trouble building a single kernel driver module for Angstrom [Solved]
I needed to add MACHINE=beagleboard and DISTRO=xxx to the local.conf
file in my local overlay.
It's curious how not having these variables set can stop substitution
from occurring for other environment variables.
It builds the module .ko file successfully now.
Thanks.
Regards,
Bob Feretich
essage: 7
Date: Mon, 28 Feb 2011 09:08:21 +0100
From: Koen Kooi
Subject: Re: [Angstrom-devel] Trouble building a single kernel driver
module for Angstrom
To: angstrom-distro-devel@linuxtogo.org
Message-ID:
Content-Type: text/plain; charset=UTF-8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why are you overriding WORKDIR and do_compile?
On 28-02-11 07:57, Bob Feretich wrote:
Previously, I used the below recipe to build a kernel module (.ko) for a
driver that I wrote for the BeagleBoard.
Since I upgraded to the new OE/Angstrom tree it has stopped working and
is showing the most confusing symptoms. There must have been some
fundamental change in the way OE builds these modules, but my google
searches have not provided any clues on what changed.
Recipe:
DESCRIPTION = "Kernel driver to control digital servomotors."
HOMEPAGE = "http://www.rafresearch.com";
SECTION = "kernel/modules"
PRIORITY = "optional"
LICENSE = "none"
#added by Bob 20100805
KERNEL_VERSION="2.6.33"
#RDEPENDS = "kernel (${KERNEL_VERSION})"
RDEPENDS = "kernel (2.6.33)"
DEPENDS = "virtual/kernel"
PR = "r0"
SRC_URI = " \
file://rtservo-driver_1.0.0/rtservo-driver.c \
file://rtservo-driver_1.0.0/rtservo-driver.h \
file://rtservo-driver_1.0.0/servo-interface.h \
file://rtservo-driver_1.0.0/Makefile \
"
WORKDIR =
"${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules"
S = "${WORKDIR}/rtservo-driver_1.0.0"
inherit module
do_compile () {
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS CC LD CPP
env
oe_runmake
'MODPATH="${D}${base_libdir}/modules/2.6.33/kernel/drivers/test"' \
'KERNEL_SOURCE="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KDIR="${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-2.6.33-r100/git"'
\
'KERNEL_VERSION="2.6.33"' \
'CC="${KERNEL_CC}"' \
'LD="${KERNEL_LD}"'
}
do_install () {
install -d ${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
install -m 0644 ${S}/rtservo-driver*${KERNEL_OBJECT_SUFFIX}
${D}${base_libdir}/modules/2.6.33/kernel/drivers/test
}
Current results:
[Bob@beagleboard setup-scripts]$ bitbake -c compile -b
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb
Build Configuration:
BB_VERSION= "1.12.0"
METADATA_BRANCH = "org.openembedded.dev"
METADATA_REVISION = "50e7d72"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO= "angstrom"
DISTRO_VERSION= "2010.7-test-20110228"
TARGET_FPU= "hard"
NOTE: Preparing runqueue
NOTE: Executing RunQueue Tasks
NOTE: Running task 1 of 7 (ID: 3,
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb,
do_setscene)
NOTE: package rtservo-driver-1.0.0-r100: task do_setscene: Started
ERROR: Error executing a python function in
/media/LINUX/AngstromDist7/setup-scripts/local/recipes/MyModules/rtservo-driver_1.0.0.bb:
IOError: [Errno 2] No such file or directory:
'${OE_BASE}/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/MyModules/temp/run.staging_helper.30029'
It is creating the directory build/${OE_BASE} to operate in instead of
substituting the contents of the OE_BASE variable.
Even if I bypass that using a relative location, the same error appears.
(run.staging_helper.xxx not found. There is no run.staging_helper file
in the tmp directory, although the other run. files and log. files are
there.)
Does anyone have a current working recipe to build a single kernel
driver module? How does it differ?
Regards,
Bob Feretich
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNa1f1MkyGM64RGpERAu1YAKCvUGzi0snCqaX5Agf42YbPW0s3KACgrvJk
HdEr+uZFhlJ1YJx/NLun9XE=
=giX4
-END PGP SIGNATURE-
--
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
End of Angstrom-distro-devel Digest, Vol 53, Issue 16
*
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] compiling a kernel module
I generally do my kernel builds in 3 steps (steps 3-5). (5 steps for the first time) The kernel is built when Angstrom builds, but sources are deleted. I like the source available for examination and want to be able to easily reconfigure the kernel. 1. bitbake -c clean virtual/kernel // ready OE to rebuild the kernel 2. bitbake -f -c compile virtual/kernel // execute the OE build up to the compile step 3. cd ../git make menuconfig // edit the kernel configuration 4. bitbake -f -c compile virtual/kernel // force re-do of the compile step with the new config settings 5. bitbake -c build virtual/kernel // execute the OE steps after the compile, but don't erase // intermediate results (kernel sources) With the intermediate results left intact, I can easily build driver modules independently for testing. bitbake -c build -b (Generates a .ko file that I can load with insmod.) Regards, Bob F. On 5/22/2012 10:49 AM, Don deJuan wrote: On 05/22/2012 10:41 AM, chrbruno wrote: Thanks for your reply, in fact, I use the virtual/kernel as a target I don't know what name to provide for "YourModule" The module I work on is driver/media/video/em28xx but "em28xx" is not recognized as a target by bitbake when I run a bitbake -c clean virtual/kernel, it removes all the kernel and module sources (the source code I want to modify) I think I will dig into the OE documentation ! or another approach would be to get the .config/patches from angstrom tree, and compile a pure kernel using the classical "linux" method Best Regards, Chris Le 22/05/2012 18:10, Don deJuan a écrit : On 05/22/2012 06:08 AM, Gyorgy Kovesdi wrote: On 2012 May 22 12:56:49 chrbruno wrote: Hello (I'm new to angstrom), I'm working on a kernel module on Beagleboard / Angstrom but I can't find a way to modify and recompile it I had similar problem: if you compile something like this: $> bitbake your-module then executing $> bitbake your-module -c clean theoretically would be enough for recompile it next time. But i found this is not enough in some cases (e.g. for kernel modules), i don't know why. Try to clean the state cache this way: $> rm build/sstate-cache/*your-module* Hope this helps K. Gy. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel I could be wrong here but I believe if you use bitbake -c cleansstate YourModule Is the better way to clean the package. I was having issues just using clean and no long do when I do the cleansstate. HTH ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel When you are done modifying your code could you not just run bitbake -f -c compile virtual/kernel ? I have not messed with kernel modules other than changing the config. By doing the -f -c compile , if I am correct should only force a compile of virtual/kernel again leaving the modifications in place. Hopefully a bitbake/OE master will chime in the actual proper commands to do exactly what you wish. HTH ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Link to mailing list archives broken
The link at http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel to the archives... http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/ seems to be broken. Regards, Bob Feretich ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Current Angstrom build for BeagleBone fails. -- Config.pm', needed by `perl.mak'
The current BeagleBone Angstrom build is failing. *** No rule to make target `/usr/lib/perl/5.14.3/Config.pm', needed by `perl.mak'. Stop. I saw some e-mail from Koen regarding an OE-core patch to prevent a parallel make for /dev-tools/git recipe. The downloaded version of the recipe had the patch except for the below... +# The perl portion fails with -j16 +PARALLEL_MAKEINST = "" + So I added these statements to the recipe... No joy. the build continues to fail the same way. Regards, Bob Feretich | ./check_bindir "z$bindir" "z$execdir" "$bindir/git-add" | NOTE: make NO_PYTHON=1 RUNTIME_PREFIX=1 NO_GETTEXT=1 install DESTDIR=/home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/image bindir=/usr/bin | make[1]: Entering directory `/home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/git-1.9.0/perl' | make[1]: *** No rule to make target `/usr/lib/perl/5.14.3/Config.pm', needed by `perl.mak'. Stop. | make[1]: Leaving directory `/home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/git-1.9.0/perl' | make: *** [install] Error 2 | ERROR: oe_runmake failed | WARNING: /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/run.do_install.29988:1 exit 1 from | exit 1 | ERROR: Function failed: do_install (log file is located at /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/log.do_install.29988) ERROR: Task 708 (/home/Bob/AngstromBBB1/setup-scripts/sources/openembedded-core/meta/recipes-devtools/git/git_1.9.0.bb, do_install) failed with exit code '1' ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Current Angstrom build for BeagleBone fails. -- Config.pm', needed by `perl.mak'
On 5/2/2014 6:58 AM, Koen Kooi wrote: Op 2 mei 2014, om 08:13 heeft Koen Kooi het volgende geschreven: Op 1 mei 2014, om 20:55 heeft Bob Feretich het volgende geschreven: The current BeagleBone Angstrom build is failing. *** No rule to make target `/usr/lib/perl/5.14.3/Config.pm', needed by `perl.mak'. Stop. I saw some e-mail from Koen regarding an OE-core patch to prevent a parallel make for /dev-tools/git recipe. The downloaded version of the recipe had the patch except for the below... +# The perl portion fails with -j16 +PARALLEL_MAKEINST = "" + I'm still looking at this. Do you have the git perl tools installed on your host? The basic perl-Git package was installed on my host. However I did not have a /usr/lib/perl/ directory. This should be fixed now I tried... MACHINE=beaglebone ./oebb.sh update bitbake cloud9-gnome-image -c clean bitbake cloud9-gnome-image ... and the same error occurred. I notice that meta-perl = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" Could this be preventing me from seeing your fix? Or, do I need to erase the entire setup-scripts directory and start over? If so, it will be about 48 hrs before I find out if the problem is fixed. Build Configuration: BB_VERSION= "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-20" TARGET_SYS= "arm-angstrom-linux-gnueabi" MACHINE = "beaglebone" DISTRO= "angstrom" DISTRO_VERSION= "v2013.12" TUNE_FEATURES = "armv7a vfp thumb neon callconvention-hard" TARGET_FPU= "vfp-neon" meta-angstrom = "angstrom-v2013.12-yocto1.5:dab3707b49b38112a9768a4c11b6d19266d9dadb" meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs toolchain-layer meta-multimedia meta-networking meta-webserver meta-ruby meta-filesystems meta-perl = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" meta-kde = "master:f45abfd4d87b0132a2565499392d2d49f465d847" meta-opie = "master:b241408b31c2ffd941b8b38bd385136ef675a703" meta-java = "dora:d86d17c9d13d1117b484cb36f884709ce585a3e0" meta-browser = "master:fc3969f63bda343c38c40a23f746c560c4735f3e" meta-mono = "master:ac286b1682e6bcc486ceb30ef90a936949bbfeab" meta-qt5 = "dora:5b5616b63bdf163ea3eb2ca8857c56a393435fe3" meta-systemd = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" meta-ros = "master:64c8b5edb221263e7fac7c03629c730ade422dff" meta-beagleboard-extras common-bsp= "dora:0e46a24b5f299f84e8043b4438f8fbc117a2627d" meta-ti = "angstrom-staging-yocto1.5:a05532600ea769c0349e526e024304f50c1fdf8c" meta-fsl-arm = "angstrom-staging-yocto1.5:48b91b77e9e37eea88637fe403d0a6b0f35dbee9" meta-fsl-arm-extra = "dora:251c07f9d868e0100ccf74fd1706269c8d6911fb" meta-nslu2= "master:bdcb4297ddb22f4eecddd4d8436cf9b6c6111922" meta-htc meta-nokia meta-openmoko meta-palm = "master:537d0c2ab41284012e1ba79716b085a861a6812a" meta-handheld = "master:5b5e68a93aae1016f5ac1d057a721b2dbf30b8d8" meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fri2 meta-jasperforest meta-n450 = "dora:569d49422d529be58b09ab71401b799c5b8f674e" meta-sunxi= "master:dc663bd5d8bd873012c90da8a9f6afc49e8a0ca6" meta-raspberrypi = "dora:1c696a95f16337e4168a045479a386194d32e18f" meta-minnow = "dora:9aa60d0eaf03fe30670acf581eaf7e57c76b5f99" meta-dominion = "master:6731c0401fe4f29daf698e36f96e1fedb981a2ad" meta-linaro meta-linaro-toolchain = "dora:95421121ccf1277cdbcb00828ac2be6ba7dde18b" meta-beagleboard-extras = "dora:0e46a24b5f299f84e8043b4438f8fbc117a2627d" meta = "angstrom-staging-yocto1.5:7c838993654b80b8e1ca076b7d91b6cd1cc18b0e" NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_install (log file is located at /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/log.do_install.12937) ERROR: Logfile of failure stored in: /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/log.do_install.12937 Log data follows: | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] | DEBUG: Executing shell function do_install | NOTE: make NO_PYTHON=1 RUNTIME_PREFIX=1 NO_GETTEXT=1 install DESTDIR=/home/B
Re: [Angstrom-devel] Current Angstrom build for BeagleBone fails. -- Config.pm', needed by `perl.mak'
That seems to have worked! The bitbake has progressed beyond git. Thanks, Bob On 5/2/2014 11:24 PM, Koen Kooi wrote: Op 2 mei 2014, om 23:44 heeft Bob Feretich het volgende geschreven: On 5/2/2014 6:58 AM, Koen Kooi wrote: Op 2 mei 2014, om 08:13 heeft Koen Kooi het volgende geschreven: Op 1 mei 2014, om 20:55 heeft Bob Feretich het volgende geschreven: The current BeagleBone Angstrom build is failing. *** No rule to make target `/usr/lib/perl/5.14.3/Config.pm', needed by `perl.mak'. Stop. I saw some e-mail from Koen regarding an OE-core patch to prevent a parallel make for /dev-tools/git recipe. The downloaded version of the recipe had the patch except for the below... +# The perl portion fails with -j16 +PARALLEL_MAKEINST = "" + I'm still looking at this. Do you have the git perl tools installed on your host? The basic perl-Git package was installed on my host. However I did not have a /usr/lib/perl/ directory. This should be fixed now I tried... MACHINE=beaglebone ./oebb.sh update bitbake cloud9-gnome-image -c clean bitbake cloud9-gnome-image ... and the same error occurred. I notice that meta-perl = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" Could this be preventing me from seeing your fix? Or, do I need to erase the entire setup-scripts directory and start over? If so, it will be about 48 hrs before I find out if the problem is fixed. Build Configuration: BB_VERSION= "1.20.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-20" TARGET_SYS= "arm-angstrom-linux-gnueabi" MACHINE = "beaglebone" DISTRO= "angstrom" DISTRO_VERSION= "v2013.12" TUNE_FEATURES = "armv7a vfp thumb neon callconvention-hard" TARGET_FPU= "vfp-neon" meta-angstrom = "angstrom-v2013.12-yocto1.5:dab3707b49b38112a9768a4c11b6d19266d9dadb" meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs toolchain-layer meta-multimedia meta-networking meta-webserver meta-ruby meta-filesystems meta-perl = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" meta-kde = "master:f45abfd4d87b0132a2565499392d2d49f465d847" meta-opie = "master:b241408b31c2ffd941b8b38bd385136ef675a703" meta-java = "dora:d86d17c9d13d1117b484cb36f884709ce585a3e0" meta-browser = "master:fc3969f63bda343c38c40a23f746c560c4735f3e" meta-mono = "master:ac286b1682e6bcc486ceb30ef90a936949bbfeab" meta-qt5 = "dora:5b5616b63bdf163ea3eb2ca8857c56a393435fe3" meta-systemd = "angstrom-staging-yocto1.5:b7edb9540426c281f479a8cdc8a69f0e2812ee74" meta-ros = "master:64c8b5edb221263e7fac7c03629c730ade422dff" meta-beagleboard-extras common-bsp= "dora:0e46a24b5f299f84e8043b4438f8fbc117a2627d" meta-ti = "angstrom-staging-yocto1.5:a05532600ea769c0349e526e024304f50c1fdf8c" meta-fsl-arm = "angstrom-staging-yocto1.5:48b91b77e9e37eea88637fe403d0a6b0f35dbee9" meta-fsl-arm-extra = "dora:251c07f9d868e0100ccf74fd1706269c8d6911fb" meta-nslu2= "master:bdcb4297ddb22f4eecddd4d8436cf9b6c6111922" meta-htc meta-nokia meta-openmoko meta-palm = "master:537d0c2ab41284012e1ba79716b085a861a6812a" meta-handheld = "master:5b5e68a93aae1016f5ac1d057a721b2dbf30b8d8" meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fri2 meta-jasperforest meta-n450 = "dora:569d49422d529be58b09ab71401b799c5b8f674e" meta-sunxi= "master:dc663bd5d8bd873012c90da8a9f6afc49e8a0ca6" meta-raspberrypi = "dora:1c696a95f16337e4168a045479a386194d32e18f" meta-minnow = "dora:9aa60d0eaf03fe30670acf581eaf7e57c76b5f99" meta-dominion = "master:6731c0401fe4f29daf698e36f96e1fedb981a2ad" meta-linaro meta-linaro-toolchain = "dora:95421121ccf1277cdbcb00828ac2be6ba7dde18b" meta-beagleboard-extras = "dora:0e46a24b5f299f84e8043b4438f8fbc117a2627d" meta = "angstrom-staging-yocto1.5:7c838993654b80b8e1ca076b7d91b6cd1cc18b0e" NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_install (log file is located at /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/log.do_install.12937) ERROR: Logfile of failure stored in: /home/Bob/AngstromBBB1/setup-scripts/build/tmp-angstrom_v2013_12-eglibc/work/armv7ahf-vfp-neon-angstrom-linux-gnueabi/git/1.9.0-r0/temp/log.do_install.12937 Log data follows: | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'common-linux', 'common-glibc', 'arm-linux'
[Angstrom-devel] Current Angstrom build for BeagleBone - 3.8 kernel fetch fails
I am trying to build the Angstrom system that ships with the BeagleBone Black from source. bitbake cloud9-gnome-image ... ERROR: Function failed: Fetcher failure for URL: 'git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y'. Unable to fetch URL from any source. It uses the EOLed 3.8 kernel, which seems to be no longer available at kernel.org. However, this kernel seems to be supported at... https://github.com/beagleboard/kernel/ Is this the right place from which to fetch the kernel? If so, which patches should I use, the ones provided with the linux-mainline_3.8.bb recipe or the ones at github.com? Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Current Angstrom build for BeagleBone - 3.8 kernel fetch fails
On 5/4/2014 7:09 AM, Koen Kooi wrote: Op 4 mei 2014, om 11:07 heeft Bob Feretich het volgende geschreven: I am trying to build the Angstrom system that ships with the BeagleBone Black from source. bitbake cloud9-gnome-image ... ERROR: Function failed: Fetcher failure for URL: 'git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y'. Unable to fetch URL from any source. It uses the EOLed 3.8 kernel, which seems to be no longer available at kernel.org. It's still available: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.8.y maybe kernel.org had a small hickup in their server? When I bitbake, the do_fetch starts for the kernel... there is very little network traffic, then the fetch times out. After repeating this several times over a couple days (thinking that kernel.org had a server problem) and receiving your response that the kernel EOLed 3.8 kernel was still available, I manually did the kernel git. I can manually git clone or git fetch the kernel successfully. bitbake -c cleanall virtual/kernel ...does not fix the condition. Attempts to fetch the kernel via bitbake still fail. The problems seems to be the state that OE has the current build is in. Is there a way to reset this condition without starting he whole build over? Regards, Bob However, this kernel seems to be supported at... https://github.com/beagleboard/kernel/ Is this the right place from which to fetch the kernel? If so, which patches should I use, the ones provided with the linux-mainline_3.8.bb recipe or the ones at github.com? Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Current Angstrom build for BeagleBone - 3.8 kernel fetch fails
On 5/4/2014 11:10 PM, Koen Kooi wrote: Op 5 mei 2014, om 00:04 heeft Bob Feretich het volgende geschreven: On 5/4/2014 7:09 AM, Koen Kooi wrote: Op 4 mei 2014, om 11:07 heeft Bob Feretich het volgende geschreven: I am trying to build the Angstrom system that ships with the BeagleBone Black from source. bitbake cloud9-gnome-image ... ERROR: Function failed: Fetcher failure for URL: 'git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.8.y'. Unable to fetch URL from any source. It uses the EOLed 3.8 kernel, which seems to be no longer available at kernel.org. It's still available: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.8.y maybe kernel.org had a small hickup in their server? When I bitbake, the do_fetch starts for the kernel... there is very little network traffic, then the fetch times out. After repeating this several times over a couple days (thinking that kernel.org had a server problem) and receiving your response that the kernel EOLed 3.8 kernel was still available, I manually did the kernel git. I can manually git clone or git fetch the kernel successfully. bitbake -c cleanall virtual/kernel ...does not fix the condition. Attempts to fetch the kernel via bitbake still fail. The problems seems to be the state that OE has the current build is in. Is there a way to reset this condition without starting he whole build over? In the sources/downloads dir remove the dirs with 'kernel.org' in them in the git2/ subdir (sources/downloads/git2/*kernel.org*). Now I'm very confused. I deleted everything (files and directories) at /git2 referencing kernel.org. Performed a: bitbake -c cleanall virtual/kernel and restarted... bitbake cloud9-gnome-image 20 minutes after the kernel fetch started there was still very very little network traffic. (Even though parallel make was set to 8, the kernel mainline fetch was the only task scheduled. I guess all other steps were now dependent on it.) So I interrupted the bitbake, and repeated the above rm and cleanall commands. I then changed the kernel recipe to access Google's kernel mirror rather than the main kernel.org repository. I got the same results... very very little network traffic. So I created a fresh Angstrom directory (starting with cloning the Angstrom setup scripts) and performed... bitbake virtual/kernel Everything worked fine until the kernel mainline fetch started, eventually it became the only task running. Still there was very very little network traffic. The fetch eventually timed out "unable to fetch url from any source". I tried a manual git clone of the kernel (copying the src repository url from the recipe) and the kernel clone progresses smoothly. I don't know why fetching the kernel during bitbake doesn't work and cloning it manually does. But, I have been stuck on this problem too long and since I plan to do some kernel driver development, I should have a local kernel repository anyway, I will proceed to modify the kernel recipe to access the manually cloned kernel repository. One thing that would help in the future would be to better document the steps "do_fetch" goes through and provide a debug or trace option to find out what it's doing when it appears to be hung. the -v and -DDD flags produced no additional information once the "do_fetch" task started. Internet searches produced many instances of bitbake "do_fetch" of known working recipes hanging, but the only solution seemed to be try again or create a local repository. Regards, Bob regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Definition of Angstrom tasks
Is there a document that provides a detailed definition of what each these tasks do? Yocto, OE, and bitbake manuals tell us how to command a specific task to be run, but not what they do. The task name provides a good hint sometimes, but often that is not enough. Users shouldn't have to read the python code for this information. These descriptions should be a part of the yocto manual. Sections 5.3.4 to 5.3.11 of the Yocto mega-manual provide a good overview of some of these tasks in the context of a workflow, but doesn't mention most of these tasks and doesn't go into enough detail on the tasks it discusses. It wouldn't be appropriate to add more detail at that point in the manual, but it would be appropriate to include details regarding all of the tasks in an appendix. Examples... The manual states that do_fetch fetches source, but doesn't state that when git is used whether it performs a pull, fetch, or clone. What are the common failure conditions of do_fetch? And what should the user do to fix the problem? do_build is mentioned a few times, but there is no reference to it being the default task or what tasks are invoked by do_build and which are omitted. do_rm_work and do_wm_work_all are not mentioned at all. Result of listtasks: do_fetchall do_build do_devshell do_package_write_ipk do_cleansstate do_savedefconfig do_uboot_mkimage do_sizecheck do_strip do_packagedata_setscene do_configure do_clean do_deploy_setscene do_cleanall do_populate_lic do_populate_sysroot do_devicetree_image do_deploy do_menuconfig do_patch do_bundle_initramfs do_packagedata do_listtasks do_compile do_package_setscene do_populate_lic_setscene do_fetch do_checkuri do_compile_kernelmodules do_package_write_ipk_setscene do_package_write do_rm_work do_package do_unpack do_install do_checkuriall do_populate_sysroot_setscene do_rm_work_all I don't have the knowledge to create such an appendix, but I volunteer to be a proofreader. Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] What target do I build to bitbake the BeagleBone Black eMMC image from source?
I am trying to build the exact image that ships with the current BeagleBone Black from source. I have built the cloud9-gnome-image successfully, but... * it results in a zImage rather than a uImage. The eMMC contains a uImage. (This is the first hint that something is wrong.) I converted the zImage to uImage, then... * Angstrom boots (visible from the serial console), but the HDMI Gnome GUI doesn't work. (The screen is totally black.) Several keyboard and crt errors are printed in the Linux boot console log. The kernel seems to be mis-configured. I replaced the bitbaked kernel image with the one from the eMMC, then... Angstrom boots, the HDMI monitor displays a desktop, the keyboard and mouse are functional, but... * the desktop background does not match the one used by the eMMC. The built background one has an eye-burning neon green graphic. * the top and bottom lines of the screen are missing (there are Gnome buttons or clock), therefore no Gnome applications can be run from the GUI. It seems that both the built kernel and root file system are broken. Am I building the wrong target? Is the results of a build sensitive to the build sequence? My build sequence was... bitbake virtual/kernel bitbake console-image bitbake cloud9-gnome-image I did not perform any "clean" steps between them. Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] The mail archives are been offline (404-not found)
The mailing list archives have been offline for several days, What's happening? Catastrophic server failure? Regards, Bob ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
