Angstrom systemd-gnome-image build failure (please help)

GoogleGroups
1

I’m trying to compile a recent kernel (which I will need to modify for my own camera hardware) and obtain a compatible gnome filesystem.

I followed the instructions at http://www.angstrom-distribution.org/building-angstrom and was able to build the kernel and a the console image with no problems.
(console image was built as a test after the first attempt at gnome failed).

When I try to build the systemd-gnome-image I run into a number of problems:

sources/meta-openembedded/meta-oe/recipes-graphics/xorg-app/xrdb_1.0.9.bb

I get a missing md5sum error. I “fixed” this by replacing the lines:

SRC_URI[md5sum] = “ed2e48cf33584455d74615ad4bbe4246”
SRC_URI[sha256sum] = “642401e12996efe3e5e5307a245e24c282b94a44c1f147e177c8484b862aeab7”

although the original lines in xrdb_1.0.9.bb look the same?

sources/meta-openembedded/meta-gnome/gdm/gdm_2.32.2.bb

Another missing md5sum error. “Fixed” by adding

SRC_URI[archive.md5sum] = “dbe5187a2e17881cc454e313e0ae8d1e”
SRC_URI[archive.sha256sum] = “034d23af0ea18d86e5543e707212d9297ec7d83f221808968af266dbebc0e703”

to gdm_2.32.2.bb

Finally I get the following, and I have no idea what to do:

Logfile of failure stored in: /home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/connman-gnome-0.5-r7/temp/log.do_unpack.20106

Logfile is:

DEBUG: Running export HOME="/home/nick"; export SSH_AGENT_PID=“8363”; export SSH_AUTH_SOCK="/tmp/keyring-fvMB0v/ssh"; export GIT_CONFIG="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/etc/gitconfig"; export PATH="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/bin/crossscripts:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux//bin:/home/nick/setup-scripts/sources/openembedded-core/scripts:/home/nick/setup-scripts/sources/bitbake/bin:/home/nick/setup-scripts/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/armv7a/bin:/home/nick/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/nick/setup-scripts/sources/openembedded-core/scripts"; git clone -s -n /home/nick/setup-scripts/sources/downloads/git2/git.kernel.org.pub.scm.network.connman.connman-gnome.git /home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/connman-gnome-0.5-r7/git/
DEBUG: Running export HOME="/home/nick"; export SSH_AGENT_PID=“8363”; export SSH_AUTH_SOCK="/tmp/keyring-fvMB0v/ssh"; export GIT_CONFIG="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/etc/gitconfig"; export PATH="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/bin/crossscripts:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux//bin:/home/nick/setup-scripts/sources/openembedded-core/scripts:/home/nick/setup-scripts/sources/bitbake/bin:/home/nick/setup-scripts/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/armv7a/bin:/home/nick/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/nick/setup-scripts/sources/openembedded-core/scripts"; git checkout 78d3c39db6f3f7977b466305110faa8ca5f74ec8
ERROR: Function 'Fetcher failure for URL: ‘None’. Fetch command export HOME="/home/nick"; export SSH_AGENT_PID=“8363”; export SSH_AUTH_SOCK="/tmp/keyring-fvMB0v/ssh"; export GIT_CONFIG="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/etc/gitconfig"; export PATH="/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beagleboard/usr/bin/crossscripts:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/sbin:/home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux//bin:/home/nick/setup-scripts/sources/openembedded-core/scripts:/home/nick/setup-scripts/sources/bitbake/bin:/home/nick/setup-scripts/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/armv7a/bin:/home/nick/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/nick/setup-scripts/sources/openembedded-core/scripts"; git checkout 78d3c39db6f3f7977b466305110faa8ca5f74ec8 failed with signal 128, output:
fatal: reference is not a tree: 78d3c39db6f3f7977b466305110faa8ca5f74ec8
’ failed
Cloning into /home/nick/setup-scripts/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/connman-gnome-0.5-r7/git…
warning: You appear to have cloned an empty repository.
done.
fatal: reference is not a tree: 78d3c39db6f3f7977b466305110faa8ca5f74ec8

I assumed the problem was on my side and deleted ~/system-scripts and started from scratch and ran into exactly the same errors.

The kernel is 3.0.12 so as I understand it, I need a compatible file system for Angstrom Gnome. Is there somewhere I can download this from, Narcissus seems give kernels 2.6.27 and 39?
Is it straight forward to add the components to the console image?

Thanks, Nick

log.do_unpack.20106 (4.15 KB)

2

So this is essentially a file not found message! (More precisely is a failure due to an empty git).

http://patchwork.openembedded.org/patch/16389/

btw
sources/meta-openembedded/meta-gnome/recipes-gnome/epiphany/epiphany_2.30.6.bb is also missing the checksum

OK fixed the above but now I get:

Collected errors:

  • satisfy_dependencies_for: Cannot satisfy the following dependencies for task-gnome:
  • connman-plugin-ntpd *
  • opkg_install_cmd: Cannot install package task-gnome.
    NOTE: package systemd-gnome-image-1.0-r0: task do_rootfs: Failed

This seems to be something that’s changed in the last few days:
http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/12096

but again I have don’t know what to do to continue.
Any clues would be greatly appreciated.

Nick

3

So I removed connman-plugin-ntpd from angstrom-task-gnome.bb and was able to finally generate a filesystem. I see that Koen Kooi has now updated oe with the same modification:
http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/msg05302.html

This image now boots but to a command prompt and not to Gnome as my previous builds did.
I can adduser and gdm manually to launch Gnome but it doesn’t seem stable.

  • I get a black background which I can’t change (change background app opens then closes immediatly)

  • Web browser Epiphany doesn’t launch

  • I can’t logout

Why does this stuff have to be so frustrating (and if not where am I going wrong?).

Nick

4

Any progress on this Nick? I got the same, the image i built boots to a console, then when i try startx, gnome doesn’t start.

5

Hi Fernando, Sorry, no I gave up on linux and bb as a solution to my non-standard camera interface as there was just too much to learn to talk to the h/w through linux. It turned out to be much easier(faster learning curve) to work with an fpga.
Good Luck, Nick

6

Hi Nick, thanks for the answer. Just for curiosity, wich interface are you working on? I’m also starting to work on a project that i need to plug a bt.656 camera to beagleboard.

7

I’m working with a monochrome version of the Aptina mt9p031 chip. There were drivers for the color version which seemed OK in version 2.?? but I could never get version 3.?? to work for me. I was also running into lost frames due to my short frame blanking times because the driver was single buffered. To work out the monochrome and buffering issues was beyond my capabilities withing my time frame and I decided it would be quicker to start from scratch with the fpga.

8

unsubscribe