[oe] [meta-handheld][PATCH 2/2] initramfs-mininit-klibc-image: initial commit

2014-05-22 Thread YourName 
From: Andrea Adami 

This cpio does the job of finding and loop-mounting the rootfs file.
See https://github.com/pcercuei/mininit

Signed-off-by: Andrea Adami 
---
 .../images/initramfs-mininit-klibc-image.bb| 22 ++
 1 file changed, 22 insertions(+)
 create mode 100644 recipes-bsp/images/initramfs-mininit-klibc-image.bb

diff --git a/recipes-bsp/images/initramfs-mininit-klibc-image.bb 
b/recipes-bsp/images/initramfs-mininit-klibc-image.bb
new file mode 100644
index 000..18aad75
--- /dev/null
+++ b/recipes-bsp/images/initramfs-mininit-klibc-image.bb
@@ -0,0 +1,22 @@
+SUMMARY = "Initramfs image for mininit kernel"
+DESCRIPTION = "This image provides mininit (helper for booting loop images)."
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+
+IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
+
+# avoid circular dependencies
+EXTRA_IMAGEDEPENDS = ""
+
+# We really need just kexecboot, kexec and ubiattach
+IMAGE_INSTALL = "mininit-klibc"
+
+# Do not pollute the initrd image with rootfs features
+IMAGE_FEATURES = ""
+
+IMAGE_LINGUAS = ""
+
+FEED_DEPLOYDIR_BASE_URI = ""
+LDCONFIGDEPEND = ""
+
+inherit image
-- 
1.9.1

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-handheld][PATCH 1/2] mininit: initial commit of v. 1.1.0

2014-05-22 Thread YourName 
From: Andrea Adami 

See https://github.com/pcercuei/mininit

Signed-off-by: Andrea Adami 
---
 recipes-bsp/mininit/mininit_git.bb | 36 
 1 file changed, 36 insertions(+)
 create mode 100644 recipes-bsp/mininit/mininit_git.bb

diff --git a/recipes-bsp/mininit/mininit_git.bb 
b/recipes-bsp/mininit/mininit_git.bb
new file mode 100644
index 000..a0439ae
--- /dev/null
+++ b/recipes-bsp/mininit/mininit_git.bb
@@ -0,0 +1,36 @@
+SUMMARY = "mininit for romfs/squashfs loop images"
+DESCRIPTION = "mininit is a linux-as-bootloader implementation based on 
losetup."
+HOMEPAGE = "https://github.com/pcercuei/mininit";
+LICENSE = "PD"
+LIC_FILES_CHKSUM = "file://init.c;md5=305bd83abb9a5aac95d48b5efbc11d58"
+SRCREV = "51eaefcaea52a5dbc1addd21ba93154aa9c97d66"
+PV = "1.1.0"
+
+SRC_URI = "git://github.com/pcercuei/mininit.git"
+SRC_URI[md5sum] = "62509644735a4e599e3ed0229f283faa"
+SRC_URI[sha256sum] = 
"4d747b16c33ac64a7923a179947d5581b4e309b73a3c89824056e9c4f0749f18"
+
+S = "${WORKDIR}/git"
+
+do_compile () {
+oe_runmake mininit
+}
+do_install () {
+install -d ${D}${bindir}/
+install -m 0755 mininit ${D}${bindir}/
+install -d ${D}/dev
+install -d ${D}/boot
+install -d ${D}/root
+install -d ${D}/proc
+install -d ${D}/sys
+}
+
+FILES_${PN} += " ${bindir}/mininit /init /dev /boot /root /proc /sys"
+
+pkg_postinst_${PN} () {
+ln -sf ${bindir}/mininit $D/init
+}
+
+BBCLASSEXTEND = "klibc"
+
+COMPATIBLE_MACHINE = 
"(akita|c7x0|collie|gcw0|h1940|h3600|hx4700|poodle|spitz|tosa)"
-- 
1.9.1

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] how to create a new layer

2014-05-22 Thread Richard Cagley 
> One other thing to note - if there are overrides for the previous machine
> (e.g. in bbappends you may see _zedboard-zynq7) you should change
> these to _me so that they still apply.
>

What is the threshold for making a new machine? That is, if I just
have a .bbappend file I want, that should just involve creating a new
layer and putting the bbappend file in the correct location. I
shouldn't have to change anything else correct?

For instance, if I just want to change the kernel configuration with a
frag file I can put linux-xlnx_3.8.bbappedn in
meta-me/recipes-kernel/linux and that's all I need?

I guess I'm just confused at what point I actually need a new machine.
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-ruby] [PATCH] ruby overwrites configuration files in ruby-native

2014-05-22 Thread Amy Fong 
>From 11b1e17a6dfdd84b3969c17b1b85b3b9bb934d11 Mon Sep 17 00:00:00 2001
From: Amy Fong 
Date: Thu, 22 May 2014 16:43:40 -0400
Subject: [PATCH] ruby overwrites configuration files in ruby-native

ruby's install rule is calling install-cross, this overwrites files installed
by ruby-native causing build failures with ruby apps, specifically where gems
are involved, especially on hosts where there is no host ruby:

(from sysroot-native's gem)
gem env
 RubyGems Environment:
   - RUBYGEMS VERSION: 1.8.23
   - RUBY VERSION: 1.9.3 (2012-04-20 patchlevel 194) [x86_64-linux]
   - INSTALLATION DIRECTORY: /usr/lib64/ruby/gems/1.9.1
   - RUBY EXECUTABLE: /usr/bin/ruby
   - EXECUTABLE DIRECTORY: /usr/bin
   - RUBYGEMS PLATFORMS:
 - ruby
 - x86_64-linux
   - GEM PATHS:
  - /usr/lib64/ruby/gems/1.9.1
  - /folk/afong/.gem/ruby/1.9.1
   - GEM CONFIGURATION:
  - :update_sources => true
  - :verbose => true
  - :benchmark => false
  - :backtrace => false
  - :bulk_threshold => 1000
   - REMOTE SOURCES:
  - http://rubygems.org/

Files affected - fake.rb, rbconfig.rb, config.h, win32.h and ruby libraries.
We should be using the versions from ruby-native.

Signed-off-by: Amy Fong 
---
 meta-ruby/recipes-devtools/ruby/ruby_1.9.3-p429.bb | 6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/meta-ruby/recipes-devtools/ruby/ruby_1.9.3-p429.bb 
b/meta-ruby/recipes-devtools/ruby/ruby_1.9.3-p429.bb
index 883bb98..bb4bab8 100644
--- a/meta-ruby/recipes-devtools/ruby/ruby_1.9.3-p429.bb
+++ b/meta-ruby/recipes-devtools/ruby/ruby_1.9.3-p429.bb
@@ -28,11 +28,7 @@ EXTRA_OEMAKE = " \
 "
 
 do_install() {
-if [ ${PN} = "ruby" ]; then
-oe_runmake 'DESTDIR=${D}' install install-cross
-else
-oe_runmake 'DESTDIR=${D}' install
-fi
+oe_runmake 'DESTDIR=${D}' install
 }
 
 FILES_${PN} += "${datadir}/rubygems \
-- 
2.0.0.rc0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-oe][PATCH] zeroc-ice : Add recipe.

2014-05-22 Thread Philip Balister 
On 05/13/2014 03:14 AM, Martin Jansa wrote:
> On Mon, May 12, 2014 at 08:21:38AM -0400, Philip Balister wrote:
>> Oh the pain.
>>
>> Tested for ARM. Can build GNU Radio and an sdk that builds GNU Radio.
> 
> Fails to build in world builds:

Thanks Martin. I traced the problem to a patch that isn't applied for
python-native (but is for python) in oe-core. I've submitted a patch to
oe-core. When it goes through, I'll submit a v2.

Philip

> 
> | make[3]: Nothing to be done for `all'.
> | make[3]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/cpp/include/IceXML'
> | make[2]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/cpp/include'
> | make[1]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/cpp'
> | make: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1'
> | NOTE: make -j 8 -e MAKEFLAGS= -C 
> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1
>  py
> | make: Entering directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1'
> | echo "making all in py";
> | making all in py
> | ( cd py && make all ) || exit 1;
> | make[1]: Entering directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py'
> | ../config/Make.common.rules:131: Found slice2py in both ICE_HOME/bin and 
> ./../cpp/bin, ICE_HOME/bin/slice2py will be used!
> | making all in modules
> | make[2]: Entering directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py/modules'
> | ../../config/Make.common.rules:131: Found slice2py in both ICE_HOME/bin and 
> ../../cpp/bin, ICE_HOME/bin/slice2py will be used!
> | making all in IcePy
> | make[3]: Entering directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py/modules/IcePy'
> | ../../../config/Make.common.rules:131: Found slice2py in both ICE_HOME/bin 
> and ../../../cpp/bin, ICE_HOME/bin/slice2py will be used!
> | g++  -c -I.  
> -I/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/cpp/include
>  -I/usr/include/python2.7  -Wall -Werror -pthread -fPIC -g  Communicator.cpp
> | In file included from ./Communicator.h:13:0,
> |  from Communicator.cpp:14:
> | ./Config.h:28:20: fatal error: Python.h: No such file or directory
> | compilation terminated.
> | make[3]: *** [Communicator.o] Error 1
> | make[3]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py/modules/IcePy'
> | make[2]: *** [all] Error 1
> | make[2]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py/modules'
> | make[1]: *** [all] Error 1
> | make[1]: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1/py'
> | make: *** [py] Error 1
> | make: Leaving directory 
> `/home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/Ice-3.5.1'
> | ERROR: oe_runmake failed
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at 
> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/x86_64-linux/zeroc-ice-native/3.5.1-r0/temp/log.do_compile.31585)
> NOTE: recipe zeroc-ice-native-3.5.1-r0: task do_compile: Failed
> ERROR: Task 23367 
> (virtual:native:/home/jenkins/oe/shr-core-branches/shr-core/meta-openembedded/meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice_3.5.1.bb,
>  do_compile) failed with exit code '1'
> 
> 
>>
>> Signed-off-by: Philip Balister 
>> ---
>>  .../0002-Modify-Makefile-for-cross-compile.patch   | 287 
>> +
>>  .../zeroc-ice/zeroc-ice_3.5.1.bb   |  75 ++
>>  2 files changed, 362 insertions(+)
>>  create mode 100644 
>> meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice-3.5.1/0002-Modify-Makefile-for-cross-compile.patch
>>  create mode 100644 meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice_3.5.1.bb
>>
>> diff --git 
>> a/meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice-3.5.1/0002-Modify-Makefile-for-cross-compile.patch
>>  
>> b/meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice-3.5.1/0002-Modify-Makefile-for-cross-compile.patch
>> new file mode 100644
>> index 000..93fb5bf
>> --- /dev/null
>> +++ 
>> b/meta-oe/recipes-connectivity/zeroc-ice/zeroc-ice-3.5.1/0002-Modify-Makefile-for-cross-compile.patch
>> @@ -0,0 +1,287 @@
>> +From bc622

[oe] [meta-networking][PATCH v2] net-snmp: install net-snmp-config script to STAGING_BINDIR_CROSS

2014-05-22 Thread Alexandre Fournier 
This recipe was installing net-snmp-config script to STAGING_BINDIR
instead of STAGING_BINDIR_CROSS, during the do_install. It is not
recommended and must be done after staging.

Changes:
* Remove STAGING_BINDIR manipulations from do_install_append
* Add net_snmp_sysroot_preprocess function instead
* Append net_snmp_sysroot_preprocess to SYSROOT_PREPROCESS_FUNCS

Signed-off-by: Alexandre Fournier 
---
 .../recipes-protocols/net-snmp/net-snmp_5.7.2.bb| 13 ++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb 
b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
index eb50d0f..f1e3a5d 100644
--- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
+++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
@@ -49,19 +49,26 @@ do_install_append() {
 install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/snmpd
 install -m 644 ${WORKDIR}/snmpd.conf ${D}${sysconfdir}/snmp/
 install -m 644 ${WORKDIR}/snmptrapd.conf ${D}${sysconfdir}/snmp/
-install -d ${STAGING_BINDIR}
-install -m 0755 ${D}${bindir}/net-snmp-config ${STAGING_BINDIR}/
 sed -e "s@-I/usr/include@@g" \
 -e "s@^prefix=.*@prefix=${STAGING_DIR_HOST}@g" \
 -e "s@^exec_prefix=.*@exec_prefix=${STAGING_DIR_HOST}@g" \
 -e "s@^includedir=.*@includedir=${STAGING_INCDIR}@g" \
 -e "s@^libdir=.*@libdir=${STAGING_LIBDIR}@g" \
--i ${STAGING_BINDIR}/net-snmp-config
+-i ${D}${bindir}/net-snmp-config
 install -d ${D}${systemd_unitdir}/system
 install -m 0644 ${WORKDIR}/snmpd.service ${D}${systemd_unitdir}/system
 install -m 0644 ${WORKDIR}/snmptrapd.service ${D}${systemd_unitdir}/system
 }
 
+SYSROOT_PREPROCESS_FUNCS += "net_snmp_sysroot_preprocess"
+
+net_snmp_sysroot_preprocess () {
+if [ -e ${D}${bindir}/net-snmp-config ]; then
+install -d ${SYSROOT_DESTDIR}${bindir_crossscripts}/
+install -m 755 ${D}${bindir}/net-snmp-config 
${SYSROOT_DESTDIR}${bindir_crossscripts}/
+fi
+}
+
 PACKAGES = "${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static 
${PN}-libs \
 ${PN}-mibs ${PN}-server ${PN}-client ${PN}-server-snmpd 
${PN}-server-snmptrapd"
 
-- 
1.8.5.5

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-oe][PATCH v2] faac: fix S!=B failure

2014-05-22 Thread Paul Eggleton 
On Wednesday 21 May 2014 18:36:29 Andreas Oberritter wrote:
> Hello Matthieu,
> 
> On 21.05.2014 09:30, Matthieu Crapet wrote:
> > Also use ${BP} and ${BPN}.
> 
> What problem does this solve?
> 
> > Signed-off-by: Matthieu Crapet 
> > ---
> > 
> >  meta-multimedia/recipes-multimedia/faac/faac_1.28.bb | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/meta-multimedia/recipes-multimedia/faac/faac_1.28.bb
> > b/meta-multimedia/recipes-multimedia/faac/faac_1.28.bb index
> > c7dcdb9..d96c1a4 100644
> > --- a/meta-multimedia/recipes-multimedia/faac/faac_1.28.bb
> > +++ b/meta-multimedia/recipes-multimedia/faac/faac_1.28.bb
> > @@ -4,15 +4,15 @@ LICENSE = "LGPLv2+"
> > 
> >  LIC_FILES_CHKSUM = "file://COPYING;md5=3bf50002aefd002f49e7bb854063f7e7 \
> >  
> >  file://libfaac/coder.h;beginline=5;endline=17;md5=fa1
> >  fd6a5fa8cdc877d63a12530d273e0"> 
> > -inherit autotools
> > +inherit autotools-brokensep
> > 
> > -SRC_URI = "${SOURCEFORGE_MIRROR}/faac/${BPN}-${PV}.tar.gz \
> > +SRC_URI = "${SOURCEFORGE_MIRROR}/faac/${BP}.tar.gz \
> > 
> > file://build-fix.patch"
> >  
> >  SRC_URI[md5sum] = "80763728d392c7d789cde25614c878f6"
> >  SRC_URI[sha256sum] =
> >  "c5141199f4cfb17d749c36ba8cfe4b25f838da67c22f0fec40228b6b9c3d19df"> 
> > -PACKAGES =+ "lib${PN} lib${PN}-dev"
> > +PACKAGES =+ "lib${BPN} lib${BPN}-dev"
> > 
> >  FILES_${PN} = " ${bindir}/faac "
> >  FILES_lib${PN} = " ${libdir}/libfaac.so.*"
> 
>   ^
> This differs from PACKAGES now.

Also, BPN should not generally be used in PACKAGES, or nativesdk packages will 
clash with target ones.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] how to create a new layer

2014-05-22 Thread Paul Eggleton 
On Wednesday 21 May 2014 13:58:07 Richard Cagley wrote:
> On Wed, May 21, 2014 at 1:31 PM, Philip Balister 
> wrote:
> > On 05/21/2014 04:05 PM, Richard Cagley wrote:
> >> On Wed, May 21, 2014 at 12:26 PM, Robert Calhoun
> >>  wrote:
> >>> On 5/21/14 2:26 PM, "Richard Cagley"  wrote:
> >> 2.) Do I need to change the machine name? If so, how to I inherit
> >> zedboard-zynq7?
> > 
> > Make a conf/machine/me.conf.
> > 
> > You can use one of the zynq machines as a starting point.
> > 
> > You'll need a conf/layer.conf also.
> 
> 1.) copied meta-xilinx/conf/machine/zedboard-zynq7.conf to
> meta-me/conf/machine/me.conf
> 2.) changed MACHINE in my build/conf/local.conf to "me"
> 3.) copied meta-xilinx/conf/layer.conf to meta-me/conf/layer.conf
> 
> Now:
> 1.) in layer.conf should I change "xilinx" to "me"?

Yes

> 2.) What about the new machine file me.conf? Do I need to edit it or
> by not editing it does it just inherit everything from the other meta
> layer?

Since you copied an existing configuration file, all that was in it
previously will still apply. You can change it if you want some values to
be different, of course (I would assume that you would want to edit
it since there wouldn't be much point in going through this exercise if you
didn't.)

One other thing to note - if there are overrides for the previous machine
(e.g. in bbappends you may see _zedboard-zynq7) you should change
these to _me so that they still apply.

You may also find this useful:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#understanding-and-creating-layers
 

Cheers

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel