[OE-core] Problems when building Angstrom master & 1.3 & 1.4 for Beagleboard Black

Khem Raj raj.khem at gmail.com
Mon Oct 14 18:31:55 UTC 2013


On Oct 11, 2013, at 8:33 AM, Ulf Samuelsson <angstrom-dev at emagii.com> wrote:

> On 2013-10-11 16:58, Koen Kooi wrote:
>> Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson <angstrom-dev at emagii.com> het volgende geschreven:
>> 
>>> Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with:
>> I strongly recommend ditching ubuntu and installing linux instead. I don't know what causes it, but switching to debian, arch, gentoo, fedora, opensuse or anything else not ubuntu based gets rid off all problems with builds not working, not booting, etc.
> 
> OK,  after installing 12.04LTS I have to
> 
> 1. left-click (hold)
> 2. alt (hold)
> 3. right click
> 
> just to add an item to the panel,
> 
> I guess they are trying to prove that Ubuntu One is superior to gnome,
> by making gnome successively worse.
> 
> so I am quite pissed of with Ubuntu
> 
> Getting a dual Xeon 6-core next week, so I'll wait until then,
> but that is not going to be exposed to Ubuntu ever…


What is your default shell ? I would recomment to use bash.

> 
> BR
> Ulf
> 
>>> PARALLEL_MAKE     = "-j8"
>>> BB_NUMBER_THREADS = "8"
>>> 
>>> I bitbake "cloud9-gnome-image"
>>> 
>>> RESULTS:
>>> * remotes/origin/angstrom-v2013.06-yocto1.4    commit 246357a1cc4977683ada564d38218e837ac615e3
>>> 
>>>    image builds but does not boot.
>>> 
>>> * remotes/origin/angstrom-v2012.12-yocto1.3    commit 01984cc460acfe5e7d5bab4feeb0888d5c6fe77f
>>> 
>>>    image builds but does not boot.
>>> 
>>> * origin/master commit 7a3b004f7bfa24ea54b0da78bd80e4dd7839321d
>>> 
>>>    Build fails on two issues.
>>> 
>>>    1.    libxklavier compile fails.
>>>            | xklavier.c: In function 'xkl_engine_class_init':
>>>            | xklavier.c:846:8: error: 'XKL_TYPE_ENGINE_FEATURES' undeclared (first use in this function)
>>>            ...
>>>            Summary: 1 task failed:
>>> /home/ulf/projects/ICU/Angstrom/setup-scripts/sources/meta-openembedded/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.0.bb,
>>>            do_compile
>>> 
>>>            Did "bitbake -c cleansstate libxklavier" and restarted, and then it continued without problem,
>>>            so there seem to be a dependency problem.
>>> 
>>>    2.    nodejs compiles fails with error:
>>>           |   arm-angstrom-linux-gnueabi-gcc  -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DL_ENDIAN' '-DOPENSSL_THREADS' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_DTLS1' '-DOPENSSL_NO_SOCK' '-DOPENSSL_NO_DGRAM' '-DOPENSSL_NO_GOST' '-DOPENSSL_NO_HW_PADLOCK' '-DOPENSSL_NO_ASM' '-DENGINESDIR="/dev/null"' '-DOPENSSLDIR="/etc/ssl"' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include -I../deps/openssl/config/android -Wall -pthread -O2 -fno-strict-aliasing -fno-tree-vrp  -MMD -MF /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/node
> js-0.8.22-r0/node-v0.8.22/out/Release/.deps//home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c
>>> | make[1]: execvp: printf: Argument list too long
>>> 
>>>    I get the second problem when I run from: "/home/ulf/projects/ICU/Angstrom/setup-scripts/"
>>>    When I install Angstrom in "/home/icu/v2012.12" I do not see the problem.
>>> 
>>> ---------------------------
>>>    Have tried recompiling my kernel changing include/linux/binfmts.h
>>> 
>>> <# define MAX_ARG_PAGES    32
>>>> # define MAX_ARG_PAGES    64
>>>    based on something I found on Internet, to no avail.
>>> 
>>> Checking a little bit more, I see it looks like:
>>> #ifdef CONFIG_MMU
>>>    ...
>>> #else
>>> # define MAX_ARG_PAGES    64
>>>    struct page *page[MAX_ARG_PAGES];
>>> #endif
>>>    CONFIG_MMU is set,  so the change is in part of the code which is not used
>>> 
>>>    Maybe there should be some kind of warning about how deep in the directory structure Angstrom can be.
>>> 
>>> ---------------------------
>>>    The resulting kernel/filesystem will run on the Beagleboard Black.
>>> 
>>>    Anyone knows what to change to increase the argument area on linux-3.2.x?
>>> 
>>> BR
>>> Ulf Samuelsson
>>> 
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core at lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core




More information about the Openembedded-core mailing list