Re: [Angstrom-devel] Angstrom v2013-06 with -mfloat-abi=softfp

2013-10-14 Thread Khem Raj

On Oct 14, 2013, at 12:55 PM, Diego Sueiro  wrote:

> Thanks Khem,
> 
> Using softfloat, Am I able to install the packages from Angstrom feeds?

If you do not tweak the defaults then yes. Otherwise, no. soft-fp feeds are not 
compatible with hardfp

> 
> Abraços,
> 
> --
> *dS
> Diego Sueiro
> 
> Administrador do Embarcados
> www.embarcados.com.br
> 
> Engenheiro de Controle e Automação
> UNIVERSIDADE FEDERAL DE ITAJUBÀ
> 
> /*long live rock 'n roll*/
> 
> 
> 2013/10/14 Khem Raj 
> 
>> 
>> On Oct 14, 2013, at 11:38 AM, Diego Sueiro  wrote:
>> 
>>> Folks,
>>> 
>>> I want to generate an Angstrom distribution with soft and hard float
>> point
>>> compatible ABI.
>>> 
>>> Reading the page below I believe that I must compile the packages with
>>> "-mfloat-abi=softfp" option. Is it correct?
>>> https://wiki.debian.org/ArmHardFloatPort
>>> 
>>> To achieve this, I think I have to change the
>>> file meta-angstrom/conf/distro/include/arm-defaults.inc to:
>>> 
>>> DEFAULTTUNE_beaglebone = "cortexa8hf-vfp"
>>> 
>>> or
>>> DEFAULTTUNE_beaglebone = "cortexa8hf-vfp-neon"
>>> 
>> 
>> 
>> Place it right. change is wrong.
>> Defaults are to build for hardfloat, in angstrom now as you see
>> if you want to change it to use softfloat then you would change it to
>> 
>> DEFAULTTUNE_beaglebone = "cortexa8-neon"
>> 
>> 
>> ___
>> 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] [OE-core] Problems when building Angstrom master & 1.3 & 1.4 for Beagleboard Black

2013-10-14 Thread Ulf Samuelsson

On 2013-10-14 20:31, Khem Raj wrote:

On Oct 11, 2013, at 8:33 AM, Ulf Samuelsson  wrote:


On 2013-10-11 16:58, Koen Kooi wrote:

Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson  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.



bash it is.
BR
Ulf




BR
Ulf


PARALLEL_MAKE = "-j8"
BB_NUMBER_THREADS = "8"

I bitbake "cloud9-gnome-image"

RESULTS:
* remotes/origin/angstrom-v2013.06-yocto1.4commit 
246357a1cc4977683ada564d38218e837ac615e3

image builds but does not boot.

* remotes/origin/angstrom-v2012.12-yocto1.3commit 
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_PAGES32

# define MAX_ARG_PAGES64

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_PAGES64
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-c...@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


___
Openembedded-core mailing list

Re: [Angstrom-devel] Angstrom v2013-06 with -mfloat-abi=softfp

2013-10-14 Thread Diego Sueiro
Thanks Khem,

Using softfloat, Am I able to install the packages from Angstrom feeds?

Abraços,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


2013/10/14 Khem Raj 

>
> On Oct 14, 2013, at 11:38 AM, Diego Sueiro  wrote:
>
> > Folks,
> >
> > I want to generate an Angstrom distribution with soft and hard float
> point
> > compatible ABI.
> >
> > Reading the page below I believe that I must compile the packages with
> > "-mfloat-abi=softfp" option. Is it correct?
> > https://wiki.debian.org/ArmHardFloatPort
> >
> > To achieve this, I think I have to change the
> > file meta-angstrom/conf/distro/include/arm-defaults.inc to:
> >
> > DEFAULTTUNE_beaglebone = "cortexa8hf-vfp"
> >
> > or
> > DEFAULTTUNE_beaglebone = "cortexa8hf-vfp-neon"
> >
>
>
> Place it right. change is wrong.
> Defaults are to build for hardfloat, in angstrom now as you see
> if you want to change it to use softfloat then you would change it to
>
> DEFAULTTUNE_beaglebone = "cortexa8-neon"
>
>
> ___
> 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] Angstrom v2013-06 with -mfloat-abi=softfp

2013-10-14 Thread Khem Raj

On Oct 14, 2013, at 11:38 AM, Diego Sueiro  wrote:

> Folks,
> 
> I want to generate an Angstrom distribution with soft and hard float point
> compatible ABI.
> 
> Reading the page below I believe that I must compile the packages with
> "-mfloat-abi=softfp" option. Is it correct?
> https://wiki.debian.org/ArmHardFloatPort
> 
> To achieve this, I think I have to change the
> file meta-angstrom/conf/distro/include/arm-defaults.inc to:
> 
> DEFAULTTUNE_beaglebone = "cortexa8hf-vfp"
> 
> or
> DEFAULTTUNE_beaglebone = "cortexa8hf-vfp-neon"
> 


Place it right. change is wrong.
Defaults are to build for hardfloat, in angstrom now as you see
if you want to change it to use softfloat then you would change it to

DEFAULTTUNE_beaglebone = "cortexa8-neon"


___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


[Angstrom-devel] Angstrom v2013-06 with -mfloat-abi=softfp

2013-10-14 Thread Diego Sueiro
Folks,

I want to generate an Angstrom distribution with soft and hard float point
compatible ABI.

Reading the page below I believe that I must compile the packages with
"-mfloat-abi=softfp" option. Is it correct?
https://wiki.debian.org/ArmHardFloatPort

To achieve this, I think I have to change the
file meta-angstrom/conf/distro/include/arm-defaults.inc to:

DEFAULTTUNE_beaglebone = "cortexa8hf-vfp"

or
DEFAULTTUNE_beaglebone = "cortexa8hf-vfp-neon"


Before I get my environment messed up I want to make sure which is the
right option I need to configure.


Kind regards,

--
*dS
Diego Sueiro

/*long live rock 'n roll*/
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


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

2013-10-14 Thread Khem Raj

On Oct 11, 2013, at 8:33 AM, Ulf Samuelsson  wrote:

> On 2013-10-11 16:58, Koen Kooi wrote:
>> Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson  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.4commit 
>>> 246357a1cc4977683ada564d38218e837ac615e3
>>> 
>>>image builds but does not boot.
>>> 
>>> * remotes/origin/angstrom-v2012.12-yocto1.3commit 
>>> 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_PAGES32
 # define MAX_ARG_PAGES64
>>>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_PAGES64
>>>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 

[Angstrom-devel] OE Changelog since 2013-10-06 until 2013-10-13

2013-10-14 Thread cliff . brake
Changelog since 2013-10-06 until 2013-10-13.  Projects included in this report:

bitbake: git://git.openembedded.org/bitbake
openembedded-core: git://git.openembedded.org/openembedded-core
meta-openembedded: git://git.openembedded.org/meta-openembedded
meta-angstrom: git://github.com/Angstrom-distribution/meta-angstrom.git
meta-arago: git://arago-project.org/git/meta-arago.git
meta-beagleboard: git://github.com/beagleboard/meta-beagleboard.git
meta-browser: git://github.com/OSSystems/meta-browser.git
meta-bug: git://github.com/buglabs/meta-bug.git
meta-chicken: git://github.com/OSSystems/meta-chicken
meta-efikamx: git://github.com/kraj/meta-efikamx.git
meta-ettus: http://github.com/koenkooi/meta-ettus.git
meta-fsl-arm: git://git.yoctoproject.org/meta-fsl-arm
meta-fsl-arm-extra: git://github.com/Freescale/meta-fsl-arm-extra.git
meta-fsl-ppc: git://git.yoctoproject.org/meta-fsl-ppc
meta-guacamayo: git://github.com/Guacamayo/meta-guacamayo.git
meta-gumstix: git://github.com/gumstix/meta-gumstix.git
meta-gumstix-community: 
git://gitorious.org/schnitzeltony-oe-meta/meta-gumstix-community.git
meta-handheld: git://git.openembedded.org/meta-handheld
meta-igep: http://github.com/ebutera/meta-igep.git
meta-intel: git://git.yoctoproject.org/meta-intel
meta-ivi: git://git.yoctoproject.org/meta-ivi
meta-java: git://github.com/woglinde/meta-java
meta-kde: git://gitorious.org/openembedded-core-layers/meta-kde.git
meta-micro: git://git.openembedded.org/meta-micro
meta-mono: git://git.yoctoproject.org/meta-mono.git
meta-netbookpro: git://github.com/tworaz/meta-netbookpro
meta-nslu2: git://github.com/kraj/meta-nslu2
meta-opie: git://git.openembedded.org/meta-opie
meta-qt3: git://git.yoctoproject.org/meta-qt3
meta-qt5: git://github.com/meta-qt5/meta-qt5.git
meta-slugos: git://github.com/kraj/meta-slugos
meta-systemd: git://git.yoctoproject.org/meta-systemd
meta-raspberrypi: git://github.com/djwillis/meta-raspberrypi.git
meta-smartphone: http://git.shr-project.org/repo/meta-smartphone.git
meta-ti: git://git.yoctoproject.org/meta-ti
meta-webos: git://github.com/openwebos/meta-webos.git
meta-xilinx: git://git.yoctoproject.org/meta-xilinx
meta-yocto: git://git.yoctoproject.org/meta-yocto
openembedded: git://git.openembedded.org/openembedded


Changelog for bitbake:

Cristiana Voicu (2):
  bitbake: replace comment added in conf files
  hob: change tooltip for live images


Changelog for openembedded-core:

Richard Purdie (3):
  build-appliance: Update SRCREV for release
  toolchain-scripts: Fix TARGET_SYS reference
  build-appliance: Update SRCREV for release


Changelog for meta-openembedded:

Andrea Adami (5):
  kexecboot.inc: merge back in the main recipe
  kexecboot_cfg: process with oe-stylize.py
  kexecboot: update to v0.6 and restylize
  kexecboot_0.6: fix LIC_FILES_CHKSUM for kexecboot-klibc
  klibc.bbclass: add a note about default of building -static

Joe MacDonald (1):
  openflow: import and tweak

Ting Liu (1):
  netperf: set _FILE_OFFSET_BITS to 64 to support large files


Changelog for meta-angstrom:


Changelog for meta-arago:

Denys Dmytriyenko (12):
  arago.conf: bump distro version
  matrix-gui-browser: replace ${S} with ${B} in do_install()
  icu: overlay the latest version from oe-core/master
  icu: disable LDFLAGSICUDT that prevents loading libicudata.so
  qtbase: configure and patch Qt5 qtbase for use with SGX in Arago
  qtwebkit: add WebGL on eglfs patches
  webkit-examples: enable building and packaging of examples
  qt5.bbclass: add new class similar to existing qt4e for configuring recipes
  qt-provider.bbclass: class to allow seamless switching between Qt4 and Qt5
  arago-prefs: load up Qt5 preferred versions
  matrix-gui-browser: update recipe to be Qt4 and Qt5 compatible
  arago-qt5-test-image: add test minimal image for testing Qt5 migration

Roger Monk (2):
  ti-connectivity/wlconf_r8.a6.01: Fix missing line continuation in install me
  ti-connectivity/compat_wl18xx_r8.a6.01: Update SRC_URI


Changelog for meta-beagleboard:


Changelog for meta-browser:


Changelog for meta-bug:


Changelog for meta-chicken:


Changelog for meta-efikamx:


Changelog for meta-ettus:


Changelog for meta-fsl-arm:

Eric BENARD (1):
  qtbase: update mx5 & mx6 support

Lauren Post (1):
  imx-kobs: Add version 3.5.7-1.0.0

Mario Domenech Goulart (1):
  imx28evk: add NAND support

Otavio Salvador (4):
  gst-pl