gmane.linux.distributions.angstrom.devel

Kernel 3.1.14 usb mount issue on BeagleBone

Mattias Millbro — 2012-05-25T14:39:00

Hi all,

I'm glad that my previous email to this list lead to a fix of the 
missing hashes in python-crypt. Unfortunately I'm experiencing a new issue.

I'm using my BeagleBone for logging serial data, using the usbserial and 
ftdi-sio kernel modules. Installing them with opkg will update the 
kernel to 3.1.14, which is fine, apart from the fact that the serial 
data is to be saved on a usb-drive. As you probably know, usb-drives is 
not mountable in 3.1.14 as they do not show up as a mountable device in 
/dev/ (as discussed here: 
https://groups.google.com/forum/?fromgroups#!topic/beagleboard/IwzUbg3JY3c 
).

Im working against a very tight deadline, so I have the following question:

- Where can I find older versions of the packages 
kernel-module-usbserial and kernel-module-ftdi-sio that has a lower 
kernel version dependency? I've spent hours in the feed browser without 
sucess.

- Do you know what is causing the usb-drive issue?

Grateful for any kind of feedback and keep up the good work!
/Mattias

problem with 'init'

Gyorgy Kovesdi — 2012-05-23T13:46:07

Hi,

I have a Beagleboard C4

I tried to build systemd-gnome-image by Narcissus and on my machine too. Some other
packages are tried as well with the same result, but i would like to use this one.
Using the latest version i have problem with 'init'. I found that no init scripts are executed (at lest
for levels 3 and 5) and therefore e.g. the X is not started after boot.
Executing 'init 5' or 'init 3' does nothing. However, 'init 0' and 'init 6' are work as expected.
I have the file '/etc/inittab' , but its content is also ignored.
I can start the X by executing '/etc/init.d/gdm start'. However, its link in /etc/rc5.d/ is also ignored
by init.

How can i build working init?

Thanx in advance
Gyorgy Kovesdi

Problem with usbhid kernel module

Gyorgy Kovesdi — 2012-05-23T08:16:22

Hi,

I have a Beagleboard C4, using it with USB keyboard and mouse.
Building the current version of Angstrom results a non-functional keyboard and mouse at the first boot.
After some digging, i found that the kernel module "usbhid" is not compiled in. It is built as a module (m), but
is not loaded during startup. Some weeks ago, it was compiled in (y) in the default kernel config of Beagle.

This way the only possibility to get it working is to log in using the serial port, and set up manually.
I think it is related to other Beagle boards (e.g. xM), however, other people reported that it is working. Do they
use it other way, or do i made something wrong?

Regards
Gyorgy Kovesdi

Information about angstrom version to use withopenembedded

2012-05-22T12:04:27

Hi all,
I hope this is the right place to ask. I've checked the FAQ and
searched on the internet but I didn't find an answer.
I've downloaded a rootfs image from narcissus for "beagleboard" based
on 2011.03 release. SDK is named "Angstrom-2012.05...". In
Openembedded/bitbake "build/conf/local.conf", which version named
"angstrom-20yy.m" I have to use? I have tried both of them but bitbake
fails to build every package.
Thanks

compiling a kernel module

chrbruno — 2012-05-22T10:56:49

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 followed the procedure on 
http://www.angstrom-distribution.org/building-angstrom
It generates correctly the kernel and rootfs

To keep the sources, i have removed the line INHERIT += "rm_work" from 
my conf/local.conf

The problem is that I cannot find a way to recompile this kernel module

I used :
bitbake virtual/kernel -c compile -f
... but i cannot find the module on disk, or it is not recompiled
( I work on 
setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/beagleboard-angstrom-linux-gnueabi/linux-mainline-3.2.16-r120d/git/drivers/media/video/em28xx/em28xx.ko 
)

I am missing something ?
Your help would be greatly appreciated

Best Regards,

Chris

maintenance-2011.03 compilation problem

Vidal, Edward Jr. — 2012-05-20T23:39:51

All,
I followed the posting of Kövesdi György

git clone git://github.com/Angstrom-distribution/setup-scripts.git
I get a different error.
ERROR: '/home/vidal/angstrom/setup-scripts/sources/openembedded/recipes/module-init-tools/module-init-tools-cross_3.12.bb' failed
I did bitbake -k x11-image & bitbake -k and they both fail 
ERROR: '/home/vidal/angstrom/setup-scripts/sources/openembedded/recipes/module-init-tools/module-init-tools-cross_3.12.bb' failed

Is the sysroot just what needs to go to the linux partition since I did not get a bz2 file.

Thanks

maintenance-2011.03 compilation problem

Vidal, Edward Jr. — 2012-05-20T14:40:54

All,
I followed the posting of Kövesdi György 

git clone git://github.com/Angstrom-distribution/setup-scripts.git
I get a different error.
ERROR: '/home/vidal/angstrom/setup-scripts/sources/openembedded/recipes/module-init-tools/module-init-tools-cross_3.12.bb' failed

I still did not get a kernel.
In the following folder I get the following.
/home/vidal/angstrom/setup-scripts/build/tmp-angstrom_2008_1/work/beagleboard-angstrom-linux-gnueabi/linux-omap-psp-2.6.32-r100g+gitr5fc29e7b2a76a64a739f857858ef0b98294aa155/temp
run.base_do_setscene.26463    run.packagestage_scenefunc.26463
run.base_scenefunction.26463  run.staging_helper.26463
With the current version all I get is run.do_fetch

Is my problem my internet connection? I get speeds between 200 & 300 kbips 

Thanks

maintenance-2011.03 compilation problem

Kövesdi György — 2012-05-20T07:53:31

Hi,

Unfortunately i have no success with the current version, so i tried to compile
an older one, which was successful some time ago:

git clone git://github.com/Angstrom-distribution/setup-scripts.git
git checkout -b local maintenance-2011.03
MACHINE=beagleboard ./oebb.sh config beagleboard
. ~/.oe/environment-2008
bitbake virtual/kernel
....
| gcc  -isystem/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -O2 -g -Wunused -Wall -static -L/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath-link,/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-rpath,/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib -Wl,-O1 -o insmod.static insmod.o libmodtools.a
| /usr/lib/gcc/i586-suse-linux/4.6/../../../../i586-suse-linux/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

Really, there is no libc in the directory build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib
What can be wrong? Is it a dependency problem?

There are a lot of '2008' entries in the configs. Is it set correctly? Do i checkout it properly?

Thanx in advance
Gyorgy Kovesdi

Recipes

matti kaasinen — 2012-05-20T06:58:39

Hi!
I would like to share couple of my recipes with you. Some of them have
more functionality than I have needed, so those parts are not tested.
Some are not tested at all, just tested to bitbake without complaints.
Recipes:
1) kernel module for isl 12026 rtc.
I rewrote buglabs driver so that there is none of the buglabs
architecture dependent parts.
All the functionality of original code is maintained, in fact ioctl
functionality was disabled in the original code. Now it's enabled.
Doubts:
a) Interrupt line is not connected. Therefore, I wrote the code so,
that interrupt code can be cut off by bitbake variable. Anyhow,
interrupt related code is not tested.
b) chip internal eeprom. I have not tried to read/write to isl 2026
eeprom - code is there, though.
c) Basic communication with chrony (ntp) works fine. However, if
enable hwclock tuning, chrony hangs. This may be related with that
interrupt communication that is not enabled in my set-up.

2) chrony
Version available in Ångstöm (chrony_git.bb) does not install all the
necessary, like chrony daemon and client binaries. I fixed those and
added some start-up scripts.
I also upgraded chrony to newer version.
Doubts:
a) Hwclock tuning hangs chrony - it can be related to missing
interrupt functionality in my rtc set-up (see above).
b) If-up trigger does not work quite well with dhcp. Dhcp connection
seems not to be quite 'UP' when if-up trigger is taking place. Chrony
seems to stay in offline quite frequently in this situation. There
should be better triggers to switch chrony online when connection has
been really established.

3) sakis3g (http://www.sakis3g.org/)
Bitbakes, but I have not even tried it yet. One problem with the
recipe is that sakis3g provides only the latest sources - not other
revisions. Therefore my recipe provides the copy of sakis sources.

4) usb-modeswitch
Latest version of usb-modeswitch (1.2.3).
Bitbake runs without complaints both with and without tcl (install and
install-static switches)
I inserted bitbake variable to select this installation flavor
(default is install-static).
I have not tried this, yet. In fact, testing sakis3g and this are kind
of tied together.

So, this is the list to share with anyone interested. Unfortunately
testing is not 100% proof - far from that. Anyhow, first steps have
been taken as recipes are written.

BR,
Matti

linux-mainline and beagleboard

Kövesdi György — 2012-05-19T16:20:54

Hi,

The current version compiles the linux-mainline 3.2.16 for Beagleboard. I found that it
completely unusabe: any X image do not even recognize the USB keyboard and mouse, while
older kernels do (3.0.28, 2.6.39). Starting init level 5 from console do not do anything.
However, all necessary kernel modules seem to be selected by default (AFAIK).

Any help would be appreciated
Gyorgy Kovesdi

kernel beagleboard/beaglebone

Vidal, Edward Jr. — 2012-05-19T13:14:07

all,


I am having problems with bitbake virtual/kernel when configured for beagleboard but MACHIME=beaglebone bitbake virtual/kernel works okay.
Checking meta-ti/conf/machine/beagleboard.conf &  meta-ti/conf/machine/beaglebone.conf I see the following:
PREFERRED_PROVIDER_virtual/kernel = "linux-mainline" for the beagleboard
PREFERRED_PROVIDER_virtual/kernel = "linux-ti33x-psp" for the beaglebone

Is it possible to use "linux-ti33x-psp" for the beagleboard?
Thanks

applying patch Angstrom and OE

Jérôme OLIVIER — 2012-05-19T04:05:30

Hello everyone,

I'm trying to get the SPI working on ; BeagleBoard-xM rev.C by rebuilding the Kernel with OE.

Let's see the steps I'm following : http://www.facebook.com/note.php?note_id=10150130372674362

I'm stuck at theses steps : 
                 * Patch the Linux Kernel 2.6.32 BeagleBoard board specific 
arch/arm/mach-omap2/board-omap3beagle.c so that the SPI pins get 
configured correctly and the SPIDEV driver is made aware of the SPI 
devices on the board.
                  *Once the kernel was patched I used the Angstrom distribution OpenEmbedded build environment to re-build the kernel.

For now I have followed this page : http://www.angstrom-distribution.org/building-angstrom
but before building : MACHINE=beagleboard ./oebb.sh bitbake virtual/kernel, I'd like to apply this patch :
http://elinux.org/BeagleBoard/SPI/Patch-2.6.37

I have been searching a lot on the internet and each source give different way but never just following : http://www.angstrom-distribution.org/building-angstrom

http://elinux.org/BeagleBoardLinuxKernel#OE says that I should change recipes or changes fils arm/arch/...
or other sources build out of the OE tree.
The problem is that I cannot find in the setup-script folder any of these file and I don't understand how to apply this patch in OE.

I hope I was enough clear
Waiting for some help,
Jerome

reproduce Narcissus build locally usingsetup-scripts for Beagleboard xM

Kevin — 2012-05-19T00:21:23

From Narcissus webpage (http://www.angstrom-distribution.org/builder/):

1. I selected BeagleBoard for my BeagleBoard-xM;
2. I selected simple; and console only.
3. In the “Platform Specific Packages” check “Texas Instruments OMAP3x/AM3x
family:-->Bootloader Files (x-load/u-boot/scripts)”.
4. Click the “build me!” button on the bottom of the page and wait for the
“builder” to generate the “*.tar.gz” file.  Download the “*.tar.gz” file
into my local working directory.
5. deploy the MLO/uImage/u-boot.bin/uEnv.txt and rootfs.tar.gz to uSD card

I am glad that this prebuilt image boots up my BBxM board. Now I am
wondering how to reproduce above steps and build such a .tar.gz file
locally.

I guess the start point could be your setup-scripts.

What I did is:

   - MACHINE=beagleboard ./oebb.sh config beagleboard
   - MACHINE=beagleboard ./oebb.sh update
   - MACHINE=beagleboard ./oebb.sh bitbake virtual/bootloader
   - MACHINE=beagleboard ./oebb.sh bitbake console-image

My question are:

After doing above steps, where are the MLO/uImage/u-boot.bin/uEnv.txt and
rootfs.tar.gz I can use to put into uSD card? Are those 4 steps enough to
generate all files? Can anybody give me some guidance?


Thanks a lot!

Kevin

[next][PATCH] setup-scripts: Add meta-linaro toEXTRALAYERS

Khem Raj — 2012-05-15T22:10:11

Signed-off-by: Khem Raj <raj.khem-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
---
 conf/bblayers.conf |    4 +++-
 sources/layers.txt |    1 +
 2 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/conf/bblayers.conf b/conf/bblayers.conf
index 3fdcf03..6d64dd5 100644
--- a/conf/bblayers.conf
+++ b/conf/bblayers.conf
< at >< at > -45,7 +45,9 < at >< at > BSPLAYERS ?= " \
 
 # Add your overlay location to EXTRALAYERS
 # Make sure to have a conf/layers.conf in there
-EXTRALAYERS ?= ""
+EXTRALAYERS ?= " \
+  ${TOPDIR}/sources/meta-linaro \
+"
 
 BBLAYERS = " \
   ${TOPDIR}/sources/meta-angstrom \
diff --git a/sources/layers.txt b/sources/layers.txt
index a7414fe..1d2d696 100644
--- a/sources/layers.txt
+++ b/sources/layers.txt
< at >< at > -17,4 +17,5 < at >< at > meta-mozilla,git://github.com/OSSystems/meta-mozilla.git,master,HEAD
 meta-chromium,git://github.com/eukrea/meta-chromium.git,master,HEAD
 meta-mono,git://github.com/KokoFitClub/meta-mono.git,master,HEAD
 meta-kde,git://gitorious.org/openembedded-core-layers/meta-kde.git,master,HEAD
+meta-linaro,git://git.linaro.org/people/kwerner/meta-linaro.git,master,HEAD
 openembedded-core,git://github.com/openembedded/oe-core.git,master,HEAD

Time based version numbering of packages?

Bryan Evenson — 2012-05-15T14:33:36

All,

Before starting with the Angstrom toolchain, we had a general version numbering scheme setup with the intent of ensuring that if the version number of our application on two machines were the same, you truly were running the same build. We're having issues figuring out to modify our development processes to fit in with the Angstrom development workflow. I'm looking for suggestion on how other groups tackle this issue. Every place I've looked through theOpenEmbedded/Bitbake/Angstrom manuals have a big "TODO" in any section related to this topic.

What I would like to do is have a suffix on the version number that relates to the build time. So when you do 'opkg info foo' on the development system, instead of reporting a version number of "1.0.3-r0.9" it would look something like "1.0.3+20120515080010-r0.9" to indicate that it was built on May 15, 2012 at 8:00:10 AM. The problem is that I can't figure out where to have bitbake insert the build time and then properly create the package. I believe I'd need to have the version number ${PV} modified with a do_compile_prepend() action in my bitbake recipe. However, I haven't found a good way to do this without breaking the packaging process.

Does anyone out there have a setup that creates a unique build number and works with bitbake? I'm not married to the idea of using the date; I just want to ensure that if I see two boards that have the same version number, that they are really running the same binary. Any suggestions are welcome.

Thanks,
Bryan

manual fetch

Vidal, Edward Jr. — 2012-05-10T14:00:48

Request help on fetching kernel
fresh build 5/9
config for beagleboard
bitbake virtual/kernel hangs fetching the kernel linux-mainline-3.2.16-r120a
MACHINE=beaglebone bitbake virtual/kernel works okay this uses a different kernel.
bitbake systemd-gnome-image hangs fetching the kernel linux-mainline-3.2.16-r120a
MACHINE=beaglebone bitbake systemd-gnome-image this works okay and creates.

In the file angstrom/setup-scripts/sources/meta-ti/recipes-kernel/linux/linux_3.0.bb I found 
SRC_URI += "git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.0.y
I executed the git clone command below
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;branch=linux-3.0.y
This downloads the kernel to linux-stable/
What is the procedure to transfer the manually fetched kernel to the angstrom tree.
angstrom/setup-scripts/sources/downloads/git2 fore bitbake to build a systemd-gnome-image for a beagleboard.
Thanks

[meta-angstrom][PATCH] angstrom-next: Pin gcc to4.7% and uclibc to 0.9.33

Khem Raj — 2012-05-08T02:05:03

Signed-off-by: Khem Raj <raj.khem-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>
---
 conf/distro/angstrom-v2012.x.conf |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/conf/distro/angstrom-v2012.x.conf b/conf/distro/angstrom-v2012.x.conf
index 8cd8ba5..16a4e3b 100644
--- a/conf/distro/angstrom-v2012.x.conf
+++ b/conf/distro/angstrom-v2012.x.conf
< at >< at > -61,7 +61,7 < at >< at > PREFERRED_VERSION_linux-libc-headers-nativesdk = "${LINUX_LIBC_HEADERS_VERSION}"
 
 ANGSTROM_EGLIBC_VERSION                 ?= "2.15"
 ANGSTROM_GLIBC_VERSION                  ?= "2.10.1"
-ANGSTROM_UCLIBC_VERSION                 ?= "0.9.32"
+ANGSTROM_UCLIBC_VERSION                 ?= "0.9.33"
 
 #Prefer glibc 2.6 and uclibc 0.9.30, these have had the most testing.
 PREFERRED_VERSION_glibc ?= "${ANGSTROM_GLIBC_VERSION}"
< at >< at > -88,7 +88,7 < at >< at > ANGSTROM_GCC_VERSION_bfin= "4.1.2"
 ANGSTROM_GCC_VERSION_avr32         ?= "4.2.2"
 
 #Everybody else can just use this: 
-ANGSTROM_GCC_VERSION                             ?= "4.7"
+ANGSTROM_GCC_VERSION                             ?= "4.7%"
 
 ANGSTROM_BINUTILS_VERSION                        ?= "2.22"

quilt-native do_configure bombs due to unrecognizwd options (--disable-silent-rules, --disable-dependency-tracking)

Ulf Samuelsson — 2012-05-04T22:41:40

Downloaded a fresh version of the Angstrom setup scripts today, and
it fails already when building pseudo.

quilt-native.configure bombs with the following error message.
  configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-dependency-tracking

Past mifhnight, so I wont investigate further today.
Full log.

NOTE: package quilt-native-0.51-r0: task do_configure: Started
NOTE: package m4-native-1.4.16-r2: task do_fetch: Started
ERROR: Function failed: do_configure (see 
/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 
for further information)
ERROR: Logfile of failure stored in: 
/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636
Log data follows:
| ERROR: Function failed: do_configure (see 
/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/temp/log.do_configure.7636 
for further information)
| NOTE: Running 
/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51/configure  
--build=x86_64-linux           --host=x86_64-linux           
--target=x86_64-linux           
--prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr 
           
--exec_prefix=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr 
           
--bindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin 
           
--sbindir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/sbin 
           
--libexecdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/libexec 
           
--datadir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share 
           
--sysconfdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/etc 
           
--sharedstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/com 
           
--localstatedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/var 
           
--libdir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/lib 
           
--includedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include 
           
--oldincludedir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/include 
           
--infodir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/info 
           
--mandir=/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/share/man 
           --disable-silent-rules           
--disable-dependency-tracking            --disable-nls
| configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-dependency-tracking
| checking for x86_64-linux-gcc... ccache gcc
| checking for C compiler default output file name...
| configure: error: in 
`/home/ulf/projects/Angstrom-Distribution/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/x86_64-linux/quilt-native-0.51-r0/quilt-0.51':
| configure: error: C compiler cannot create executables
| See `config.log' for more details.
| ERROR: oe_runconf failed
NOTE: package quilt-native-0.51-r0: task do_configure: Failed
ERROR: Task 12 
(/home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, 
do_configure) failed with exit code '1'
Waiting for 1 running tasks to finish:
0: m4-native-1.4.16-r2 do_fetch (pid 7637)
NOTE: package m4-native-1.4.16-r2: task do_fetch: Succeeded
NOTE: Tasks Summary: Attempted 7 tasks of which 5 didn't need to be 
rerun and 1 failed.

Summary: 1 task failed:
   
/home/ulf/projects/Angstrom-Distribution/setup-scripts/sources/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.51.bb, 
do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Questions about angstrom

Vidal, Edward Jr. — 2012-05-04T19:31:59

Hello All,

Questions:
How do you do a fetch manually if one fails?
Is there a way to merge download sources with a new build ( git clone git://github.com/Angstrom-distribution/setup-scripts.git)?
With a cpu (AMD Phenom(tm) II X6 1090T Processor) and  8GB of memory what would be the expected build time of bitbake virtual/kernel & bitbake systemd-gnome-image?
Is angstromv2012.05 the bleeding edge?  I see the online is using 2011.03 and stable.
What version is currently considered stable?
The command ". /usr/local/angstrom/arm/environment" was done when using "angstrom-2011.03-x86_64-linux-armv7a-linux-gnueabi-toolchain-qte-4.6.3.tar" pre-built tool chain.
export SDK_PATH=/usr/local/angstrom/arm
export TARGET_SYS=arm-angstrom-linux-gnueabi
export PATH=$SDK_PATH/bin:$PATH
export CPATH=$SDK_PATH/$TARGET_SYS/usr/include:$CPATH
export LIBTOOL_SYSROOT_PATH=$SDK_PATH/$TARGET_SYS
export PKG_CONFIG_SYSROOT_DIR=$SDK_PATH/$TARGET_SYS
export PKG_CONFIG_PATH=$SDK_PATH/$TARGET_SYS/usr/lib/pkgconfig
export CONFIG_SITE=$SDK_PATH/site-config
alias opkg="LD_LIBRARY_PATH=$SDK_PATH/lib $SDK_PATH/bin/opkg-cl -f $SDK_PATH//etc/opkg-sdk.conf -o $SDK_PATH"
alias opkg-target="LD_LIBRARY_PATH=$SDK_PATH/lib $SDK_PATH/bin/opkg-cl -f $SDK_PATH/$TARGET_SYS/etc/opkg.conf -o $SDK_PATH/$TARGET_SYS"
export OE_QMAKE_CC=arm-angstrom-linux-gnueabi-gcc
export OE_QMAKE_CXX=arm-angstrom-linux-gnueabi-g++
export OE_QMAKE_LINK=arm-angstrom-linux-gnueabi-g++
export OE_QMAKE_AR=arm-angstrom-linux-gnueabi-ar
export OE_QMAKE_LIBDIR_QT=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi//usr/lib
export OE_QMAKE_INCDIR_QT=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi//usr/include/qtopia
export OE_QMAKE_MOC=/usr/local/angstrom/arm/bin/moc4
export OE_QMAKE_UIC=/usr/local/angstrom/arm/bin/uic4
export OE_QMAKE_UIC3=/usr/local/angstrom/arm/bin/uic34
export OE_QMAKE_RCC=/usr/local/angstrom/arm/bin/rcc4
export OE_QMAKE_QDBUSCPP2XML=/usr/local/angstrom/arm/bin/qdbuscpp2xml4
export OE_QMAKE_QDBUSXML2CPP=/usr/local/angstrom/arm/bin/qdbusxml2cpp4
export OE_QMAKE_QT_CONFIG=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi//usr/share/qtopia/mkspecs/qconfig.pri
export QMAKESPEC=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi//usr/share/qtopia/mkspecs/linux-g++
Should the variables be set "/home/vidal/angstrom/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi" or is there a script like ". /usr/local/angstrom/arm/environment"?

Thanks,

X beagleboard

Vidal, Edward Jr. — 2012-05-04T16:02:03

All,
This was done after a fresh build angstrom/setup-scripts 5/3/12
Both bitbake systemd-gnome-image and bitbake virtual/kernel hang up at task 871 meta-ti/recipes-kernel/linux/linux_3.0.bb do_fetch.
Thanks

do you support Beagleboard-xM

Kevin Dong — 2012-05-04T15:55:07

Hi,

I try to build a rootfs for my Beagleboard-xM from your site:
http://narcissus.angstrom-distribution.org/

But I can only find beagleboard and beaglebone options. Can I use either of
them or what I should modify to support my beagleboard-xM?

Thanks!

Regards,
Kevin