Problems when building Angstrom master & 1.3 & 1.4 for Beagleboard Black

DISCUSSION Ulf Samuelsson 3 participants 5 messages Oct 11, 2013 – Oct 14, 2013

lore

Share & tools

lore

Ulf Samuelsson

author

2013-10-11 14:32 UTC #0 lore raw

Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with:

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/nodejs-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

Quoted 1 line

# 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

Koen Kooi

2013-10-11 14:58 UTC #1 lore raw

Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson <[email protected]> het volgende geschreven:

Quoted 1 line

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.

Quoted 68 lines

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/nodejs-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
Quoted 1 line
# 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
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Ulf Samuelsson

author

2013-10-11 15:33 UTC #2 lore raw

Quoted 4 lines · Koen Kooi

Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson <[email protected]> het volgende geschreven:
Quoted 1 line
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...

BR
Ulf

Quoted 66 lines

Quoted 66 lines
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/nodejs-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
Quoted 1 line
# 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
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Khem Raj

2013-10-14 18:31 UTC #3 lore raw

Quoted 14 lines · Ulf Samuelsson

Quoted 4 lines · Koen Kooi
Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson <[email protected]> het volgende geschreven:
Quoted 1 line
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,

Quoted 7 lines

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.

Quoted 77 lines

BR
Ulf
Quoted 26 lines
Quoted 26 lines
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
Quoted 5 lines
Quoted 5 lines
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
Quoted 28 lines
Quoted 28 lines
| 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
Quoted 1 line
# 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?
Quoted 7 lines
Quoted 7 lines
BR
Ulf Samuelsson
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Ulf Samuelsson

author

2013-10-14 19:37 UTC #4 lore raw

Quoted 18 lines · Khem Raj

Quoted 16 lines · Ulf Samuelsson
Quoted 4 lines · Koen Kooi
Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson <[email protected]> het volgende geschreven:
Quoted 1 line
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.

Quoted 7 lines

Quoted 4 lines
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.

bash it is.
BR
Ulf

Quoted 75 lines

Quoted 75 lines
BR
Ulf
Quoted 26 lines
Quoted 26 lines
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
Quoted 5 lines
Quoted 5 lines
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
Quoted 28 lines
Quoted 28 lines
| 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
Quoted 1 line
# 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?
Quoted 7 lines
Quoted 7 lines
BR
Ulf Samuelsson
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core