Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol

2015-03-31 Thread Alex J Lennon 


On 30/03/2015 21:27, Burton, Ross wrote:

 On 30 March 2015 at 18:36, Alex J Lennon
 ajlen...@dynamicdevices.co.uk mailto:ajlen...@dynamicdevices.co.uk
 wrote:

 I'm updating to Yocto master and have been seeing that when I
 bitbake -c
 devshell virtual/kernel I go into a work-shared tree now.


 The devshell drops you into whatever ${S} is for that recipe, which
 for the kernel is ${STAGING_KERNEL_DIR} since the kernel
 optimisations.  For the kernel yes, this is sub-optimal.  Maybe the
 kernel should override this using the variable I added (as Bruce
 mentioned).


Thanks Ross, Bruce for the feedback and pointers. I shall work through.

One thought - it might perhaps be helpful to have two command variants
to easily drop into either place from the command line without having to
worry about environment variables?

e.g. bitbake -c devshell-shared and bitbake -c devshell or some such?

Regards, Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] Add makedumpfile utility

2015-03-31 Thread Gaurang Shastri 
PR No : [https://bugzilla.yoctoproject.org/show_bug.cgi?id=7069]

Signed-off-by: Gaurang Shastri gshas...@juniper.net
---
 .../recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb |   19 +++
 1 file changed, 19 insertions(+)
 create mode 100644 
meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb

diff --git a/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb 
b/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb
new file mode 100644
index 000..ce3027e
--- /dev/null
+++ b/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb
@@ -0,0 +1,19 @@
+DESCRIPTION = Make dump file utility
+LICENSE = GPLv2
+
+LIC_FILES_CHKSUM = file://COPYING;md5=751419260aa954499f7abaabaa882bbe
+
+SRC_URI = 
http://sourceforge.net/projects/makedumpfile/files/makedumpfile/1.5.0/makedumpfile-${PV}.tar.gz;name=makedumpfile;
+
+SRC_URI[makedumpfile.md5sum] = e22277d77752c71525a79eab148abf55
+SRC_URI[makedumpfile.sha256sum] = 
8a771a22c6ba79dc505e55727f0cfd357ccb3c97defe21cefd5a67b64452fca7
+
+DEPENDS = zlib elfutils bzip2
+
+EXTRA_OEMAKE = TARGET=${TARGET_ARCH}
+
+do_install() {
+   install -d ${D}${bindir}/
+   install -c -m 755 ${S}/makedumpfile ${D}${bindir}/
+}
+
-- 
1.7.9.5

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [[Patch2]Makedumpfile] Add makedumpfile

2015-03-31 Thread Gaurang Shastri 
PR NO:[https://bugzilla.yoctoproject.org/show_bug.cgi?id=7069]

Signed-off-by: Gaurang Shastri gshas...@juniper.net
---
 .../recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb |3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb 
b/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb
index ce3027e..bd86b64 100644
--- a/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb
+++ b/meta-cgl-common/recipes-cgl/makedumpfile/makedumpfile_1.5.0.bb
@@ -13,7 +13,6 @@ DEPENDS = zlib elfutils bzip2
 EXTRA_OEMAKE = TARGET=${TARGET_ARCH}
 
 do_install() {
-   install -d ${D}${bindir}/
-   install -c -m 755 ${S}/makedumpfile ${D}${bindir}/
+   install -Dm 0755 ${S}/makedumpfile ${D}${bindir}/makedumpfile
 }
 
-- 
1.7.9.5

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [PATCH] LSI AXXIA updates to 3.4 standard/axxia/base

2015-03-31 Thread Cristian Bercaru 

Hello, Bruce!

Sorry for the duplicate mails. I had some trouble with my Internet 
connection and I resent the patch.


I can apply this patch just fine on 'standard/axxia/base' of a freshly 
cloned linux-yocto-3.4:

arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update)

I think you tried to apply another patch that you already applied.
Please check you mailbox again.

 yow-bashfiel-d4 [/home/brucgit-merge] git am -s a.mbox
 Applying: arch/powerpc/kernel: Address IBM PPC476 erratum 47

Thanks,
Cristian

On 03/30/2015 09:39 PM, Bruce Ashfield wrote:

On 2015-03-30 01:10 PM, cristian.berc...@windriver.com wrote:

From: Cristian Bercaru cristian.berc...@windriver.com

Hello! This patch is an update to IBM PPC476 erratum 48 fix and it is
tagged with the latest 3.4 tag: lsi_axxia_linux_7.8.1.43.


This came through multiple times .. is this the right version ? This
patch won't apply to the linux-yocto-3.4 standard/axxxia/base branch:

yow-bashfiel-d4 [/home/brucgit-merge] git am -s a.mbox
Applying: arch/powerpc/kernel: Address IBM PPC476 erratum 47
error: patch failed: arch/powerpc/kernel/head_44x.S:1249
error: arch/powerpc/kernel/head_44x.S: patch does not apply
Patch failed at 0001 arch/powerpc/kernel: Address IBM PPC476 erratum 47
The copy of the patch that failed is found in:

/home/bruce/poky-kernel/linux-yocto-3.4.git-merge/.git/rebase-apply/patch
When you have resolved this problem, run git am --continue.
If you prefer to skip this patch, run git am --skip instead.
To restore the original branch and stop patching, run git am --abort.

Bruce



Sangeetha Rao (1):
   arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update)

  arch/powerpc/kernel/traps.c |6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)





--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] [PATCH] Add makedumpfile utility

2015-03-31 Thread Khem Raj 

 On Mar 31, 2015, at 12:37 AM, Gaurang Shastri gshas...@juniper.net wrote:
 
 +do_install() {
 + install -d ${D}${bindir}/
 + install -c -m 755 ${S}/makedumpfile ${D}${bindir}/
 +}
 +

make it a single line like below
install -Dm 0755 ${S}/makedumpfile ${D}${bindir}/makedumpfile
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto master work-shared, kernel .config seems to have gone awol

2015-03-31 Thread Burton, Ross 
On 31 March 2015 at 07:37, Alex J Lennon ajlen...@dynamicdevices.co.uk
wrote:

 One thought - it might perhaps be helpful to have two command variants to
 easily drop into either place from the command line without having to worry
 about environment variables?

 e.g. bitbake -c devshell-shared and bitbake -c devshell or some such?


Only gcc and the kernel have the concept of shared sources, so I'm not sure
this actually gains much at the cost of more tasks to confuse people.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][yocto-docs] poky.ent: Ubuntu based systems need xlstproc

2015-03-31 Thread Flanagan, Elizabeth 
On 28 March 2015 at 04:23, Paul Eggleton paul.eggle...@linux.intel.com wrote:
 Hi Beth,

 On Friday 27 March 2015 15:03:10 Beth Flanagan wrote:
 xlstproc is needed for doc building. I'm sure others are
 effected as well.

 Signed-off-by: Beth Flanagan elizabeth.flana...@intel.com
 ---
  documentation/poky.ent | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

 diff --git a/documentation/poky.ent b/documentation/poky.ent
 index 5d12fc1..a8fe99f 100644
 --- a/documentation/poky.ent
 +++ b/documentation/poky.ent
 @@ -59,7 +59,7 @@
  !ENTITY OE_INIT_PATH YOCTO_POKY;/oe-init-build-env
  !ENTITY OE_INIT_FILE oe-init-build-env
  !ENTITY UBUNTU_HOST_PACKAGES_ESSENTIAL gawk wget git-core diffstat unzip
 texinfo gcc-multilib \ - build-essential chrpath socat
 + build-essential chrpath socat xsltproc
  !ENTITY FEDORA_HOST_PACKAGES_ESSENTIAL gawk make wget tar bzip2 gzip
 python unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++
 glibc-devel texinfo chrpath \ ccache perl-Data-Dumper perl-Text-ParseWords
 perl-Thread-Queue socat

 Which doc building? Our manuals or docs as part of recipes? Can you give an
 example of a failure?


yocto-docs. On an Ubuntu based system I was having issues building
them because xsltproc wasn't installed during the normal system
install. I'm not sure if other can verify that, but I tried it on two
of my systems with the same results (Mint 17.1 Rebecca).

 Thanks,
 Paul

 --

 Paul Eggleton
 Intel Open Source Technology Centre

-b

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][yocto-docs] poky.ent: Ubuntu based systems need xlstproc

2015-03-31 Thread Flanagan, Elizabeth 
On 31 March 2015 at 12:38, Flanagan, Elizabeth
elizabeth.flana...@intel.com wrote:
 On 28 March 2015 at 04:23, Paul Eggleton paul.eggle...@linux.intel.com 
 wrote:
 Hi Beth,

 On Friday 27 March 2015 15:03:10 Beth Flanagan wrote:
 xlstproc is needed for doc building. I'm sure others are
 effected as well.

 Signed-off-by: Beth Flanagan elizabeth.flana...@intel.com
 ---
  documentation/poky.ent | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

 diff --git a/documentation/poky.ent b/documentation/poky.ent
 index 5d12fc1..a8fe99f 100644
 --- a/documentation/poky.ent
 +++ b/documentation/poky.ent
 @@ -59,7 +59,7 @@
  !ENTITY OE_INIT_PATH YOCTO_POKY;/oe-init-build-env
  !ENTITY OE_INIT_FILE oe-init-build-env
  !ENTITY UBUNTU_HOST_PACKAGES_ESSENTIAL gawk wget git-core diffstat unzip
 texinfo gcc-multilib \ - build-essential chrpath socat
 + build-essential chrpath socat xsltproc
  !ENTITY FEDORA_HOST_PACKAGES_ESSENTIAL gawk make wget tar bzip2 gzip
 python unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++
 glibc-devel texinfo chrpath \ ccache perl-Data-Dumper perl-Text-ParseWords
 perl-Thread-Queue socat

 Which doc building? Our manuals or docs as part of recipes? Can you give an
 example of a failure?


 yocto-docs. On an Ubuntu based system I was having issues building
 them because xsltproc wasn't installed during the normal system
 install. I'm not sure if other can verify that, but I tried it on two
 of my systems with the same results (Mint 17.1 Rebecca).

 Thanks,
 Paul

 --

 Paul Eggleton
 Intel Open Source Technology Centre

 -b

 --
 Elizabeth Flanagan
 Yocto Project
 Build and Release

What I'm seeing:

pidge@fuath:~/yocto-docs/documentation make DOC=yocto-project-qs

 Building yocto-project-qs

cd yocto-project-qs; xsltproc --xinclude -o yocto-project-qs.html
yocto-project-qs-customization.xsl yocto-project-qs.xml; cd ..
/bin/sh: 1: xsltproc: not found

 Building eclipse help of yocto-project-qs

cd yocto-project-qs  \
xsltproc --xinclude \
--stringparam base.dir 'html/yocto-project-qs/' \
-o eclipse/yocto-project-qs.html \
yocto-project-qs-eclipse-customization.xsl
yocto-project-qs.xml  \
mv eclipse/toc.xml eclipse/yocto-project-qs-toc.xml  \
cp -rf figures eclipse/html/yocto-project-qs/  \
cd ..;
/bin/sh: 2: xsltproc: not found
make: *** [eclipse-generate] Error 127

apt-get install xsltproc resolves the issue.


-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][yocto-docs] poky.ent: Ubuntu based systems need xlstproc

2015-03-31 Thread Burton, Ross 
On 31 March 2015 at 12:38, Flanagan, Elizabeth elizabeth.flana...@intel.com
 wrote:

 On 28 March 2015 at 04:23, Paul Eggleton paul.eggle...@linux.intel.com
 wrote:
  Hi Beth,
 
  On Friday 27 March 2015 15:03:10 Beth Flanagan wrote:
  xlstproc is needed for doc building. I'm sure others are
  effected as well.
 
  Signed-off-by: Beth Flanagan elizabeth.flana...@intel.com
  ---
   documentation/poky.ent | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
 
  diff --git a/documentation/poky.ent b/documentation/poky.ent
  index 5d12fc1..a8fe99f 100644
  --- a/documentation/poky.ent
  +++ b/documentation/poky.ent
  @@ -59,7 +59,7 @@
   !ENTITY OE_INIT_PATH YOCTO_POKY;/oe-init-build-env
   !ENTITY OE_INIT_FILE oe-init-build-env
   !ENTITY UBUNTU_HOST_PACKAGES_ESSENTIAL gawk wget git-core diffstat
 unzip
  texinfo gcc-multilib \ - build-essential chrpath socat
  + build-essential chrpath socat xsltproc
   !ENTITY FEDORA_HOST_PACKAGES_ESSENTIAL gawk make wget tar bzip2 gzip
  python unzip perl patch \ diffutils diffstat git cpp gcc gcc-c++
  glibc-devel texinfo chrpath \ ccache perl-Data-Dumper
 perl-Text-ParseWords
  perl-Thread-Queue socat
 
  Which doc building? Our manuals or docs as part of recipes? Can you give
 an
  example of a failure?
 

 yocto-docs. On an Ubuntu based system I was having issues building
 them because xsltproc wasn't installed during the normal system
 install. I'm not sure if other can verify that, but I tried it on two
 of my systems with the same results (Mint 17.1 Rebecca).


Building the documentation from scratch isn't a normal thing for a user to
do, so I wouldn't add xsltproc to the list of build essential packages for
builds.

It should be documented along with the other dependencies in the
instructions for building the documentation of course.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] tip and cu utility

2015-03-31 Thread PRAVEEN KUMAR R 
Is there any existing package that provide tip and cu utility ?


http://man.cx/TIP(1)?
?

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][yocto-docs] poky.ent: Ubuntu based systems need xlstproc

2015-03-31 Thread Paul Eggleton 
On Tuesday 31 March 2015 12:43:33 Burton, Ross wrote:
 On 31 March 2015 at 12:38, Flanagan, Elizabeth elizabeth.flana...@intel.com
 wrote:
  On 28 March 2015 at 04:23, Paul Eggleton paul.eggle...@linux.intel.com
  wrote:
   Which doc building? Our manuals or docs as part of recipes? Can you give
   an example of a failure?
  
  yocto-docs. On an Ubuntu based system I was having issues building
  them because xsltproc wasn't installed during the normal system
  install. I'm not sure if other can verify that, but I tried it on two
  of my systems with the same results (Mint 17.1 Rebecca).
 
 Building the documentation from scratch isn't a normal thing for a user to
 do, so I wouldn't add xsltproc to the list of build essential packages for
 builds.
 
 It should be documented along with the other dependencies in the
 instructions for building the documentation of course.

Right, this is what I was getting at. Packages required for building 
documentation are listed in the ref manual, and xsltproc is already on that 
list for Ubuntu.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Maninder Singh 
Hi Mark,
there is one typo error in this:-
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927
+ src/get.c: Remove extra checkf ro ld-linux.so.3 in strcmp
*** check for *
Thanks
--

Hi Mark,
Sorry for missing ID in Signed-off-by: Maninder Singh 
Signed-off-by: Maninder Singh 

I suggested that change just to remove redundat code.
This looks Ok to me 
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927

Thanks a lot

Maninder Singh

 Hmm, I never saw the original email (or thread).

(I have no record of ever receiving the original email.  How odd...)

 What is the context for this, simply that there are multiple ld-linux.do.3 in
 the same check and remove one or the other is more efficient?
 
 (I suspect it will be optimized out, but I can make the change quickly 
 enough.)

I have merged the change, slightly different format.

See:

http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927

This is in the staging area.

Maninder if this is ok, I'm more then happy to add your signed-off-by line to
the commit before moving it into the cross_prelink branch.

Thanks!
--Mark

 --Mark
 
 On 3/31/15 1:01 PM, Khem Raj wrote:

 On Mar 30, 2015, at 8:14 PM, Maninder Singh   wrote:

 Hi,


 From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001
 From: Maninder Singh 
 Date: Thu, 19 Mar 2015 03:02:59 +0530
 Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp
   
 if (! strcmp (soname, ld-linux.so.2)
   || ! strcmp (soname, ld-linux.so.3)  
   || ! strcmp (soname, ld.so.1)
   || ! strcmp (soname, ld-linux-ia64.so.2)
   || ! strcmp (soname, ld-linux-x86-64.so.2)
   || ! strcmp (soname, ld64.so.1)
   || ! strcmp (soname, ld-linux.so.3) ---
 redundant code
   || ! strcmp (soname, ld-linux-armhf.so.3))

 Signed-off-by: Maninder Singh 


 use First Last 

 ---
 src/get.c |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
 diff --git a/src/get.c b/src/get.c
 index 6a63f02..a34668a 100644
 --- a/src/get.c
 +++ b/src/get.c
 @@ -35,7 +35,6 @@ is_ldso_soname (const char *soname)
|| ! strcmp (soname, ld-linux-ia64.so.2)
|| ! strcmp (soname, ld-linux-x86-64.so.2)
|| ! strcmp (soname, ld64.so.1)
 -  || ! strcmp (soname, ld-linux.so.3)
|| ! strcmp (soname, ld-linux-armhf.so.3))
  return 1;
return 0;
 -- 
 1.7.1


 Thanks and Regards,
 Maninder Singh

 201503310844012_QKNMBDIF.gif

 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org 
 https://lists.yoctoproject.org/listinfo/yocto

 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Maninder Singh 
Hi Mark,
Sorry for missing ID in Signed-off-by: Maninder Singh 
Signed-off-by: Maninder Singh maninder...@samsung.com

I suggested that change just to remove redundat code.
This looks Ok to me 
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927

Thanks a lot

Maninder Singh

 Hmm, I never saw the original email (or thread).

(I have no record of ever receiving the original email.  How odd...)

 What is the context for this, simply that there are multiple ld-linux.do.3 in
 the same check and remove one or the other is more efficient?
 
 (I suspect it will be optimized out, but I can make the change quickly 
 enough.)

I have merged the change, slightly different format.

See:

http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927

This is in the staging area.

Maninder if this is ok, I'm more then happy to add your signed-off-by line to
the commit before moving it into the cross_prelink branch.

Thanks!
--Mark

 --Mark
 
 On 3/31/15 1:01 PM, Khem Raj wrote:

 On Mar 30, 2015, at 8:14 PM, Maninder Singh   wrote:

 Hi,


 From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001
 From: Maninder Singh 
 Date: Thu, 19 Mar 2015 03:02:59 +0530
 Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp
   
 if (! strcmp (soname, ld-linux.so.2)
   || ! strcmp (soname, ld-linux.so.3)  
   || ! strcmp (soname, ld.so.1)
   || ! strcmp (soname, ld-linux-ia64.so.2)
   || ! strcmp (soname, ld-linux-x86-64.so.2)
   || ! strcmp (soname, ld64.so.1)
   || ! strcmp (soname, ld-linux.so.3) ---
 redundant code
   || ! strcmp (soname, ld-linux-armhf.so.3))

 Signed-off-by: Maninder Singh 


 use First Last 

 ---
 src/get.c |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
 diff --git a/src/get.c b/src/get.c
 index 6a63f02..a34668a 100644
 --- a/src/get.c
 +++ b/src/get.c
 @@ -35,7 +35,6 @@ is_ldso_soname (const char *soname)
|| ! strcmp (soname, ld-linux-ia64.so.2)
|| ! strcmp (soname, ld-linux-x86-64.so.2)
|| ! strcmp (soname, ld64.so.1)
 -  || ! strcmp (soname, ld-linux.so.3)
|| ! strcmp (soname, ld-linux-armhf.so.3))
  return 1;
return 0;
 -- 
 1.7.1


 Thanks and Regards,
 Maninder Singh

 201503310844012_QKNMBDIF.gif

 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org 
 https://lists.yoctoproject.org/listinfo/yocto

 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] remove package from sdimg

2015-03-31 Thread Christian Ege 
Hi,
Am 31.03.2015 17:07 schrieb abhishek srivastava abhishek.emb...@gmail.com
:

 hi
 i have created core-image-sato sdimg for my project on raspberrypi.
actually, i want to run few applications that need python. i want to remove
unnecessary packages that were required for smooth compilation of those
applications since I downloaded entire python and gcc packages which had
heavily increased size of my sdimg size.

 how can i find which applications requires what packages for its normal
functionality so that i can further tweak my sdimg or keep exactly those
libraries that are needed for my application and remove rest.
 please help

Have a look at my cheat sheet:
https:// https://github.com/cybertux/cheatsheets/tree/master/bitbake
github.com https://github.com/cybertux/cheatsheets/tree/master/bitbake/
https://github.com/cybertux/cheatsheets/tree/master/bitbakecybertux
https://github.com/cybertux/cheatsheets/tree/master/bitbake/
https://github.com/cybertux/cheatsheets/tree/master/bitbakecheatsheets
https://github.com/cybertux/cheatsheets/tree/master/bitbake/tree/master/
https://github.com/cybertux/cheatsheets/tree/master/bitbakebitbake
https://github.com/cybertux/cheatsheets/tree/master/bitbake
Or in the yocto wiki:

https://wiki.yoctoproject.org/wiki/FAQ#How_can_one_view_the_dependencies_of_packages_and_the_resulting_growth_in_code_size_as_packages_are_added.3F

Regards,
Christian
 regards
 Abhishek

 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] nightly-weston.conf: Run regular build tests for no-X11 case

2015-03-31 Thread Graydon, Tracy 
Just following up on this. What images do we wish to do this for?

Tracy



From: Burton, Ross ross.bur...@intel.commailto:ross.bur...@intel.com
Date: Monday, March 30, 2015 at 2:35 AM
To: Paul Eggleton 
paul.eggle...@linux.intel.commailto:paul.eggle...@linux.intel.com
Cc: Tracy Graydon tracy.gray...@intel.commailto:tracy.gray...@intel.com, 
yocto@yoctoproject.orgmailto:yocto@yoctoproject.org 
yocto@yoctoproject.orgmailto:yocto@yoctoproject.org
Subject: Re: [yocto] [PATCH] nightly-weston.conf: Run regular build tests for 
no-X11 case


On 28 March 2015 at 15:33, Paul Eggleton 
paul.eggle...@linux.intel.commailto:paul.eggle...@linux.intel.com wrote:
When I wrote the bug I was thinking more of systems with no graphics
at all rather than with Weston replacing X11 - not that we shouldn't be
testing Weston though I guess.

I guess there's value in both.  I for one certainly want to see the non-X11 but 
still GL-enabled codepaths exerised for the Mesa/GTK+/GStreamer stacks.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] distro_alias.inc: update/sort alias information.

2015-03-31 Thread Flanagan, Elizabeth 
Actually, if this hasn't been pulled yet, please do not pull it.

I've been finding issues in distrodata.bbclass and distro_check.py
that are reporting inaccurate info. I'm patching them right now, but
as this patch was based on that inaccurate info, I'd like to rebase it
with good data.

-b

On 31 March 2015 at 01:11, Beth Flanagan elizabeth.flana...@intel.com wrote:
 Added new package data, and cleaned up whitespace.

 I've also corrected some packaged data (replacement-tar from
 my reading of the recipe is the tar normally found in distros).

 One issue this patch exposed st I haven't had a chance to track
 down is that when you attempt to get distrodata from
 gcc-crosssdk-initial-x86_64. The produced .csv in tmp/log
 is missing the Distro information. bitbake -e
 shows that DISTRO_PN_ALIAS isn't even getting set in this case.

 My guess here is that something is happening with the _
 along the way, I've just not found it yet.

 Signed-off-by: Beth Flanagan elizabeth.flana...@intel.com
 ---
  meta-yocto/conf/distro/include/distro_alias.inc | 41 
 +
  1 file changed, 35 insertions(+), 6 deletions(-)

 diff --git a/meta-yocto/conf/distro/include/distro_alias.inc 
 b/meta-yocto/conf/distro/include/distro_alias.inc
 index 48c1d92..2c35c28 100644
 --- a/meta-yocto/conf/distro/include/distro_alias.inc
 +++ b/meta-yocto/conf/distro/include/distro_alias.inc
 @@ -1,6 +1,6 @@
  #
  # This is a list for tracking status of package relative to Major
 -# distributions such as Fedora, Ubuntu, Debian, ... The package
 +# distributions such as Fedora, Ubuntu, Debian, ... The package
  # name is the major distribution equivalent to the name used in oe-core
  #
  # The format is as a bitbake variable override for each recipe
 @@ -54,6 +54,7 @@ DISTRO_PN_ALIAS_pn-core-image-base = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-clutter = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-directfb = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-full-cmdline = OE-Core
 +DISTRO_PN_ALIAS_pn-core-image-kernel-dev = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-lsb = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-lsb-dev = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-lsb-qt3 = OE-Core
 @@ -67,14 +68,19 @@ DISTRO_PN_ALIAS_pn-core-image-rt-sdk = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-sato = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-sato-dev = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-sato-sdk = OE-Core
 +DISTRO_PN_ALIAS_pn-core-image-testmaster = OE-Core
 +DISTRO_PN_ALIAS_pn-core-image-testmaster-initramfs = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-weston = OE-Core
  DISTRO_PN_ALIAS_pn-core-image-x11 = OE-Core
  DISTRO_PN_ALIAS_pn-cross-localedef = OSPDT
  DISTRO_PN_ALIAS_pn-cryptodev-linux = OE-Core
 +DISTRO_PN_ALIAS_pn-cryptodev-module = OE-Core
 +DISTRO_PN_ALIAS_pn-cryptodev-tests = OE-Core
  DISTRO_PN_ALIAS_pn-cwautomacros = OSPDT 
 upstream=http://cwautomacros.berlios.de/;
  DISTRO_PN_ALIAS_pn-damageproto = Meego=xorg-x11-proto-damageproto
  DISTRO_PN_ALIAS_pn-db = Debian=db5.1 Ubuntu=db5.1
  DISTRO_PN_ALIAS_pn-dbus-ptest = Fedora=dbus Ubuntu=dbus
 +DISTRO_PN_ALIAS_pn-dbus-test = Fedora=dbus Ubuntu=dbus
  DISTRO_PN_ALIAS_pn-dbus-wait = OpenedHand
  DISTRO_PN_ALIAS_pn-depmodwrapper-cross = OE-Core
  DISTRO_PN_ALIAS_pn-directfb-examples = Debian=directfb Fedora=directfb
 @@ -85,6 +91,8 @@ DISTRO_PN_ALIAS_pn-docbook-dsssl-stylesheets = 
 Fedora=docbook-style-dsssl Ubunt
  DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-3.1 = Fedora=docbook-dtds 
 Mandriva=docbook-dtd31-sgml
  DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-4.1 = Fedora=docbook-dtds 
 Mandriva=docbook-dtd41-sgml
  DISTRO_PN_ALIAS_pn-docbook-sgml-dtd-4.5 = Fedora=docbook-dtds 
 Mandriva=docbook-dtd42-sgml
 +DISTRO_PN_ALIAS_pn-docbook-xml-dtd4 = Ubuntu=docbook-xml 
 Fedora=docbook-dtds
 +DISTRO_PN_ALIAS_pn-docbook-xml-dtd4-native = Ubuntu=docbook-xml 
 Fedora=docbook-dtds
  DISTRO_PN_ALIAS_pn-dri2proto = Meego=xorg-x11-proto-dri2proto
  DISTRO_PN_ALIAS_pn-dropbear = Debian=dropbear Ubuntu=dropbear
  DISTRO_PN_ALIAS_pn-dtc = Fedora=dtc Ubuntu=dtc
 @@ -112,14 +120,21 @@ DISTRO_PN_ALIAS_pn-gail = Fedora=gail 
 Ubuntu=libgail-3-0
  DISTRO_PN_ALIAS_pn-gaku = OpenedHand
  DISTRO_PN_ALIAS_pn-galago-daemon = Debian=galago-daemon 
 Ubuntu=galago-daemon
  DISTRO_PN_ALIAS_pn-gcc-cross-initial = OE-Core
 +DISTRO_PN_ALIAS_pn-gcc-cross-initial-i586 = OE-Core
  DISTRO_PN_ALIAS_pn-gcc-crosssdk-initial = OE-Core
 +DISTRO_PN_ALIAS_pn-gcc-crosssdk-initial-x86_64 = OE-Core
  DISTRO_PN_ALIAS_pn-gccmakedep = Mandriva=gccmakedep Ubuntu=xutils-dev
  DISTRO_PN_ALIAS_pn-gcc-runtime = Ubuntu=gcc Fedora=gcc
 +DISTRO_PN_ALIAS_pn-gcc-sanitizers = Ubuntu=gcc Fedora=gcc
 +DISTRO_PN_ALIAS_pn-gcc-source = Ubuntu=gcc Fedora=gcc
  DISTRO_PN_ALIAS_pn-gconf-dbus = Meego=GConf-dbus
  DISTRO_PN_ALIAS_pn-gdk-pixbuf = Debian=libgdk-pixbuf2.0 Fedora=gdk-pixbuf
  DISTRO_PN_ALIAS_pn-gdk-pixbuf-csource = Debian=libgdk-pixbuf2.0-0 
 Fedora=gdk-pixbuf2
  DISTRO_PN_ALIAS_pn-gettext-minimal = Debian=gettext Fedora=gettext
  DISTRO_PN_ALIAS_pn-glib-2.0 =

Re: [yocto] [PATCH] Gracefully abort if rootfs.img gets to big

2015-03-31 Thread Paul Eggleton 
On Tuesday 31 March 2015 10:16:52 Chris Hallinan wrote:
 On Tue, Mar 31, 2015 at 9:17 AM, Paul Eggleton
 paul.eggle...@linux.intel.com wrote:
  On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
  Great catching up with you last week, and thanks for looking at my
  patch.  I supposed it's a double edged sword.  If we make it a
  variable, it can be set wrong and the build hang again.  OTOH, 128MB
  is probably way more space than we really need to reserve, and I
  supposed if someone were just banging up against the limit, they might
  want to tweak it.  I'll defer to the collective judgement of the
  group, and resubmit if that's the consensus.
  
  Is there any practical way we can measure the actual size of these files?
 
 I gave this some thought after Armin's comment, and yes, maybe there
 is a way to estimate the size available. I'll look further into it.
 
  Oh, and silly me...I figured the mail list daemon would put the
  [Yocto] tag on the patch. Since it seems to tag our posts, that is a
  mystery to me.
  
  The mailing list always prepends the list name to the subject of posted
  messages.
 
 That what I thought, too.  Wonder why it didn't prepend the list name
 to this patch?

It did - see:
https://lists.yoctoproject.org/pipermail/yocto/2015-March/024294.html
 
  A few other notes:
  
  1) This patch should be sent to the
  openembedded-c...@lists.openembedded.org mailing list rather than here.
 
 Ah, wasn't sure about that, thanks!
 
  2) The YP bugzilla reference should be of the format [YOCTO #7541] .
  
  3) The shortlog (first line of the commit message / subject) should be
  prefixed with the area/file the patch is changing i.e. for this one it
  should be bootimg.bbclass: gracefully abort if rootfs.img gets to big.
 
 Thanks for the guidance. As you can see, I'm not experienced at
 sending patches!  I'll investigate and re-send to oe-core@

Great!

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] remove package from sdimg

2015-03-31 Thread abhishek srivastava 
hi
i have created core-image-sato sdimg for my project on raspberrypi.
actually, i want to run few applications that need python. i want to remove
unnecessary packages that were required for smooth compilation of those
applications since I downloaded entire python and gcc packages which had
heavily increased size of my sdimg size.

how can i find which applications requires what packages for its normal
functionality so that i can further tweak my sdimg or keep exactly those
libraries that are needed for my application and remove rest.
please help

regards
Abhishek
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] Gracefully abort if rootfs.img gets to big

2015-03-31 Thread Chris Hallinan 
On Tue, Mar 31, 2015 at 9:17 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
 Hi Chris,

 Great to see you at ELC!

 On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
 Great catching up with you last week, and thanks for looking at my
 patch.  I supposed it's a double edged sword.  If we make it a
 variable, it can be set wrong and the build hang again.  OTOH, 128MB
 is probably way more space than we really need to reserve, and I
 supposed if someone were just banging up against the limit, they might
 want to tweak it.  I'll defer to the collective judgement of the
 group, and resubmit if that's the consensus.

 Is there any practical way we can measure the actual size of these files?

I gave this some thought after Armin's comment, and yes, maybe there
is a way to estimate the size available. I'll look further into it.


 Oh, and silly me...I figured the mail list daemon would put the
 [Yocto] tag on the patch. Since it seems to tag our posts, that is a
 mystery to me.

 The mailing list always prepends the list name to the subject of posted
 messages.

That what I thought, too.  Wonder why it didn't prepend the list name
to this patch?


 A few other notes:

 1) This patch should be sent to the openembedded-c...@lists.openembedded.org
 mailing list rather than here.

Ah, wasn't sure about that, thanks!


 2) The YP bugzilla reference should be of the format [YOCTO #7541] .

 3) The shortlog (first line of the commit message / subject) should be 
 prefixed
 with the area/file the patch is changing i.e. for this one it should be
 bootimg.bbclass: gracefully abort if rootfs.img gets to big.

Thanks for the guidance. As you can see, I'm not experienced at
sending patches!  I'll investigate and re-send to oe-core@

Regards,

Chris
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Missing debug symbols

2015-03-31 Thread Gary Thomas 

I'm trying to debug some problems with avconv.  When I install
the debug packages, I got some errors/warnings:

# opkg install libav-dbg
Installing libav-dbg (9.16-r0.10) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libav-dbg_9.16-r0.10_cortexa9hf-vfp-neon.ipk.
librtmp-dbg: unsatisfied recommendation for libcrypto-dbg
librtmp-dbg: unsatisfied recommendation for libssl-dbg
libav-dbg: unsatisfied recommendation for libbz2-dbg
libav-dbg: unsatisfied recommendation for libavdevice-dbg
libx264-dbg: unsatisfied recommendation for libavutil-dbg
libx264-dbg: unsatisfied recommendation for libswscale-dbg
libav-dbg: unsatisfied recommendation for libavformat-dbg
libav-dbg: unsatisfied recommendation for libavcodec-dbg
libav-dbg: unsatisfied recommendation for libavutil-dbg
libav-dbg: unsatisfied recommendation for libavresample-dbg
libav-dbg: unsatisfied recommendation for libswscale-dbg
libav-dbg: unsatisfied recommendation for libasound-dbg
libav-dbg: unsatisfied recommendation for libavfilter-dbg
Installing librtmp-dbg (git-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/librtmp-dbg_git-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libc6-dbg (2.21-r0.5) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libc6-dbg_2.21-r0.5_cortexa9hf-vfp-neon.ipk.
Installing libz-dbg (1.2.8-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libz-dbg_1.2.8-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libtheora-dbg (1.1.1-r1.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libtheora-dbg_1.1.1-r1.16_cortexa9hf-vfp-neon.ipk.
Installing libogg-dbg (1.3.2-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libogg-dbg_1.3.2-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxext-dbg (1:1.3.3-r0.12) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxext-dbg_1.3.3-r0.12_cortexa9hf-vfp-neon.ipk.
Installing libx11-dbg (1:1.6.2-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libx11-dbg_1.6.2-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxcb-dbg (1.11-r0.12) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxcb-dbg_1.11-r0.12_cortexa9hf-vfp-neon.ipk.
Installing libxdmcp-dbg (1:1.1.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxdmcp-dbg_1.1.1-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxau-dbg (1:1.0.8-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxau-dbg_1.0.8-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libx264-dbg (r2230+git-r1.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libx264-dbg_r2230+git-r1.16_cortexa9hf-vfp-neon.ipk.
Installing libsdl-1.2-dbg (1.2.15-r3.18) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon-mx6qdl/libsdl-1.2-dbg_1.2.15-r3.18_cortexa9hf-vfp-neon-mx6qdl.ipk.
Installing libts-1.0-dbg (1.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libts-1.0-dbg_1.1-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxfixes-dbg (1:5.0.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxfixes-dbg_5.0.1-r0.16_cortexa9hf-vfp-neon.ipk.
Configuring libc6-dbg.
Configuring libz-dbg.
Configuring librtmp-dbg.
Configuring libxdmcp-dbg.
Configuring libogg-dbg.
Configuring libxau-dbg.
Configuring libxcb-dbg.
Configuring libx11-dbg.
Configuring libxfixes-dbg.
Configuring libtheora-dbg.
Configuring libxext-dbg.
Configuring libx264-dbg.
Configuring libts-1.0-dbg.
Configuring libsdl-1.2-dbg.
Configuring libav-dbg.
Configuring libc6-thread-db.
Configuring gdb.

Now, of course the problem I need to look at is in one of
those missing packages:

# gdb avconv
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as arm-amltd-linux-gnueabi.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
(gdb) r -f video4linux2 -channel 1 -pix_fmt yuyv422 -s 720x480 -i /dev/video0 
-frames 10 /home/
root/test-0001.mp4
Starting program: /usr/bin/avconv -f video4linux2 -channel 1 -pix_fmt yuyv422 
-s 720x480 -i /dev/video0 -frames 10 /home/
root/test-0001.mp4
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/libthread_db.so.1.
Cannot access memory

Re: [yocto] Missing debug symbols

2015-03-31 Thread Gary Thomas 

On 2015-03-31 09:58, Gary Thomas wrote:

I'm trying to debug some problems with avconv.  When I install
the debug packages, I got some errors/warnings:

# opkg install libav-dbg
Installing libav-dbg (9.16-r0.10) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libav-dbg_9.16-r0.10_cortexa9hf-vfp-neon.ipk.
librtmp-dbg: unsatisfied recommendation for libcrypto-dbg
librtmp-dbg: unsatisfied recommendation for libssl-dbg
libav-dbg: unsatisfied recommendation for libbz2-dbg
libav-dbg: unsatisfied recommendation for libavdevice-dbg
libx264-dbg: unsatisfied recommendation for libavutil-dbg
libx264-dbg: unsatisfied recommendation for libswscale-dbg
libav-dbg: unsatisfied recommendation for libavformat-dbg
libav-dbg: unsatisfied recommendation for libavcodec-dbg
libav-dbg: unsatisfied recommendation for libavutil-dbg
libav-dbg: unsatisfied recommendation for libavresample-dbg
libav-dbg: unsatisfied recommendation for libswscale-dbg
libav-dbg: unsatisfied recommendation for libasound-dbg
libav-dbg: unsatisfied recommendation for libavfilter-dbg
Installing librtmp-dbg (git-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/librtmp-dbg_git-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libc6-dbg (2.21-r0.5) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libc6-dbg_2.21-r0.5_cortexa9hf-vfp-neon.ipk.
Installing libz-dbg (1.2.8-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libz-dbg_1.2.8-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libtheora-dbg (1.1.1-r1.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libtheora-dbg_1.1.1-r1.16_cortexa9hf-vfp-neon.ipk.
Installing libogg-dbg (1.3.2-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libogg-dbg_1.3.2-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxext-dbg (1:1.3.3-r0.12) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxext-dbg_1.3.3-r0.12_cortexa9hf-vfp-neon.ipk.
Installing libx11-dbg (1:1.6.2-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libx11-dbg_1.6.2-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxcb-dbg (1.11-r0.12) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxcb-dbg_1.11-r0.12_cortexa9hf-vfp-neon.ipk.
Installing libxdmcp-dbg (1:1.1.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxdmcp-dbg_1.1.1-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxau-dbg (1:1.0.8-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxau-dbg_1.0.8-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libx264-dbg (r2230+git-r1.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libx264-dbg_r2230+git-r1.16_cortexa9hf-vfp-neon.ipk.
Installing libsdl-1.2-dbg (1.2.15-r3.18) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon-mx6qdl/libsdl-1.2-dbg_1.2.15-r3.18_cortexa9hf-vfp-neon-mx6qdl.ipk.
Installing libts-1.0-dbg (1.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libts-1.0-dbg_1.1-r0.16_cortexa9hf-vfp-neon.ipk.
Installing libxfixes-dbg (1:5.0.1-r0.16) on root.
Downloading 
http://192.168.1.116/teton-p0382-feeds/cortexa9hf-vfp-neon/libxfixes-dbg_5.0.1-r0.16_cortexa9hf-vfp-neon.ipk.
Configuring libc6-dbg.
Configuring libz-dbg.
Configuring librtmp-dbg.
Configuring libxdmcp-dbg.
Configuring libogg-dbg.
Configuring libxau-dbg.
Configuring libxcb-dbg.
Configuring libx11-dbg.
Configuring libxfixes-dbg.
Configuring libtheora-dbg.
Configuring libxext-dbg.
Configuring libx264-dbg.
Configuring libts-1.0-dbg.
Configuring libsdl-1.2-dbg.
Configuring libav-dbg.
Configuring libc6-thread-db.
Configuring gdb.

Now, of course the problem I need to look at is in one of
those missing packages:

# gdb avconv
GNU gdb (GDB) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as arm-amltd-linux-gnueabi.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
(gdb) r -f video4linux2 -channel 1 -pix_fmt yuyv422 -s 720x480 -i /dev/video0 
-frames 10 /home/
root/test-0001.mp4
Starting program: /usr/bin/avconv -f video4linux2 -channel 1 -pix_fmt yuyv422 
-s 720x480 -i /dev/video0 -frames 10 /home/
root/test-0001.mp4
[Thread debugging using libthread_db enabled]
Using host libthread_db library

Re: [yocto] [RFC] Toaster integration with Jenkins

2015-03-31 Thread Barros Pena, Belen 
Hi Anders,

Thanks for the comments. Some answers inline.

Cheers

Belén

On 31/03/2015 10:39, Anders Darander and...@chargestorm.se wrote:

Hi,

* Barros Pena, Belen belen.barros.p...@intel.com [150330 19:48]:
 We are considering working on integrating Toaster with Jenkins as part
of
 the next Yocto Project release. Our thinking so far is collected in this
 Bugzilla feature:

 https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527

Ah, sounds really interesting. I've recently been thinking about how I
should be able to benefit from toaster, as we're running out automated
builds using Jenkins.

 Any thoughts? Are we missing something? Are we going about it in a
 completely wrong way?

Sounds quite good to me.

If there's some project configuration that needs to be done in Toaster,
I'd appreciate if as much as possible could be retrieved from our
current Jenkins setup (i.e. exported from the Jenkins plugin to
Toaster). (Not least as we're running a couple of scripts to source the
environment and handling some extra configurations needed; thus I'd
assume we couldn't just take the freestyle Jenkins project talked about
in b) of Alexandru 's first comment in #YOCTO-7527.

I will add this to the Bugzilla entry, so that we keep track of all
possible issues. 


I don't know if this is the right thread but a couple of other things
that we really would need in order to fully be able to utilize this.

1) Some way of getting the built git branch shown in toaster. (As we
discussed on YPDD in Düsseldorf together with Axis). We're building
master and release branches for the same machine and image.

If you mean the name of the branch, Toaster currently shows this in
several places. One of them is the configuration information for a
finished build, which displays a list of the layers used, and for each of
them the branch name and the commit used. I've uploaded an screenshot here

http://i.imgur.com/GPDwCh0.png


2) In the proposed bug, would toaser be able to recieve and handle
toaster/build logs from different YP releases?

Yes, but you would need to create a Toaster project for each release.
Currently, for each Toaster project, you must select the YP release you
want to use. A project can only use a single release at any given time.


Normally we've at least
one active release branch, and possibly a master (or master-next) branch
that's going to the next YP release. If possible, I'd like to visualize
all this in the same Toaster instance.

Apart from that, I think this is really interesting!

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Maninder Singh 
Title: Samsung Enterprise Portal mySingle

Hi,
From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001From: Maninder Singh maninder...@samsung.comDate: Thu, 19 Mar 2015 03:02:59 +0530Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmpif (! strcmp (soname, "ld-linux.so.2")|| ! strcmp (soname, "ld-linux.so.3")|| ! strcmp (soname, "ld.so.1")|| ! strcmp (soname, "ld-linux-ia64.so.2")|| ! strcmp (soname, "ld-linux-x86-64.so.2")|| ! strcmp (soname, "ld64.so.1")|| ! strcmp (soname, "ld-linux.so.3") --- redundant code|| ! strcmp (soname, "ld-linux-armhf.so.3"))Signed-off-by: Maninder Singh ---src/get.c |1 -1 files changed, 0 insertions(+), 1 deletions(-)diff --git a/src/get.c b/src/get.cindex 6a63f02..a34668a 100644--- a/src/get.c+++ b/src/get.c@@ -35,7 +35,6 @@ is_ldso_soname (const char *soname) || ! strcmp (soname, "ld-linux-ia64.so.2") || ! strcmp (soname, "ld-linux-x86-64.so.2") || ! strcmp (soname, "ld64.so.1")-|| ! strcmp (soname, "ld-linux.so.3") || ! strcmp (soname, "ld-linux-armhf.so.3")) return 1; return 0;-- 1.7.1Thanks and Regards,Maninder Singh




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto menuconfig not working

2015-03-31 Thread Erik Botö 
Hi,

Does devshell work for any package? If not, try setting an explicit
OE_TERMINAL in local.conf, e.g. OE_TERMINAL = screen.

See 
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-OE_TERMINAL
for details.

Cheers,
Erik

On Wed, Mar 25, 2015 at 11:34 AM, Gerhard de Clercq
gerh...@declercqsystems.com wrote:
 For some reason the menuconfig menu does not come up when I try launching it
 from my Yocto installation. I am using the Toradex Yocto 1.6 system as is
 described here
 http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/openembedded-%28core%29,
 with my board set to apalis-t30. When I run either bitbake virtual/kernal
 -c menuconfig or bitbake linux-toradex -c menuconfig, it executes fine but
 finishes (without erros) before actually showing anything. Running devshell
 also gives the same results.

 If I just use the kernel sources on their own as is described here
 http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/build-u-boot-and-linux-kernel-from-source-code,
 I can get menuconfig open using make nconfig. From the Yocto scripts it
 appears as if though the exact same kernel sources are being used. If I try
 adding adding make nconfig to the do_configure_prepend script in the
 linux-toradex_git.bb file then the commands get stuck stating that the
 process (I assume menuconfig) is running and then provides a PID for it, but
 no window or menu is displayed anywhere and the task does not seem to
 finish.

 PS. I am on Fedora 21 64-bit.

 --
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Mark Hatle 
On 3/31/15 2:01 PM, Mark Hatle wrote:
 Hmm, I never saw the original email (or thread).

(I have no record of ever receiving the original email.  How odd...)

 What is the context for this, simply that there are multiple ld-linux.do.3 in
 the same check and remove one or the other is more efficient?
 
 (I suspect it will be optimized out, but I can make the change quickly 
 enough.)

I have merged the change, slightly different format.

See:

http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink_stagingid=fd99a47124b1f1141f2afe4e87da7cb209cc2927

This is in the staging area.

Maninder if this is ok, I'm more then happy to add your signed-off-by line to
the commit before moving it into the cross_prelink branch.

Thanks!
--Mark

 --Mark
 
 On 3/31/15 1:01 PM, Khem Raj wrote:

 On Mar 30, 2015, at 8:14 PM, Maninder Singh maninder...@samsung.com
 mailto:maninder...@samsung.com wrote:

 Hi,


 From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001
 From: Maninder Singh maninder...@samsung.com 
 mailto:maninder...@samsung.com
 Date: Thu, 19 Mar 2015 03:02:59 +0530
 Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp
   
 if (! strcmp (soname, ld-linux.so.2)
   || ! strcmp (soname, ld-linux.so.3)  
   || ! strcmp (soname, ld.so.1)
   || ! strcmp (soname, ld-linux-ia64.so.2)
   || ! strcmp (soname, ld-linux-x86-64.so.2)
   || ! strcmp (soname, ld64.so.1)
   || ! strcmp (soname, ld-linux.so.3) ---
 redundant code
   || ! strcmp (soname, ld-linux-armhf.so.3))

 Signed-off-by: Maninder Singh 


 use First Last your@email

 ---
 src/get.c |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
 diff --git a/src/get.c b/src/get.c
 index 6a63f02..a34668a 100644
 --- a/src/get.c
 +++ b/src/get.c
 @@ -35,7 +35,6 @@ is_ldso_soname (const char *soname)
|| ! strcmp (soname, ld-linux-ia64.so.2)
|| ! strcmp (soname, ld-linux-x86-64.so.2)
|| ! strcmp (soname, ld64.so.1)
 -  || ! strcmp (soname, ld-linux.so.3)
|| ! strcmp (soname, ld-linux-armhf.so.3))
  return 1;
return 0;
 -- 
 1.7.1


 Thanks and Regards,
 Maninder Singh

 201503310844012_QKNMBDIF.gif

 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org mailto:yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Mark Hatle 
Hmm, I never saw the original email (or thread).

What is the context for this, simply that there are multiple ld-linux.do.3 in
the same check and remove one or the other is more efficient?

(I suspect it will be optimized out, but I can make the change quickly enough.)

--Mark

On 3/31/15 1:01 PM, Khem Raj wrote:
 
 On Mar 30, 2015, at 8:14 PM, Maninder Singh maninder...@samsung.com
 mailto:maninder...@samsung.com wrote:

 Hi,


 From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001
 From: Maninder Singh maninder...@samsung.com 
 mailto:maninder...@samsung.com
 Date: Thu, 19 Mar 2015 03:02:59 +0530
 Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp
   
 if (! strcmp (soname, ld-linux.so.2)
   || ! strcmp (soname, ld-linux.so.3)  
   || ! strcmp (soname, ld.so.1)
   || ! strcmp (soname, ld-linux-ia64.so.2)
   || ! strcmp (soname, ld-linux-x86-64.so.2)
   || ! strcmp (soname, ld64.so.1)
   || ! strcmp (soname, ld-linux.so.3) ---
 redundant code
   || ! strcmp (soname, ld-linux-armhf.so.3))

 Signed-off-by: Maninder Singh 

 
 use First Last your@email
 
 ---
 src/get.c |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
 diff --git a/src/get.c b/src/get.c
 index 6a63f02..a34668a 100644
 --- a/src/get.c
 +++ b/src/get.c
 @@ -35,7 +35,6 @@ is_ldso_soname (const char *soname)
|| ! strcmp (soname, ld-linux-ia64.so.2)
|| ! strcmp (soname, ld-linux-x86-64.so.2)
|| ! strcmp (soname, ld64.so.1)
 -  || ! strcmp (soname, ld-linux.so.3)
|| ! strcmp (soname, ld-linux-armhf.so.3))
  return 1;
return 0;
 -- 
 1.7.1


 Thanks and Regards,
 Maninder Singh

 201503310844012_QKNMBDIF.gif

 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org mailto:yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto
 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] what is the proper way to build with fedora rawhide/gcc-5.0?

2015-03-31 Thread Robert P. J. Day 

  i asked about this a few weeks ago, finally getting back to it ...
for better or worse, i'm running fedora rawhide, updated to the point
where i have gcc-5.0.0:

$ gcc --version
gcc (GCC) 5.0.0 20150208 (Red Hat 5.0.0-0.10)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$

which causes a number of build issues trying to build for something as
simple as qemux86.

  first, there is a linemarkers issue with gcc-5.0 that i got around
by adding to local.conf:

  CPPFLAGS_append=  -P

and there were two native build issues due to gcc-5.0 being far
pickier with warnings that i sidestepped with the cheap hack:

  ASSUME_PROVIDED += elfutils-native
  ASSUME_PROVIDED += binutils-native

at this point, the build was almost complete when i hit another
compile error for udev on the target:

DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common',
'common-linux', 'common-glibc', 'i586-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 8
make: *** No rule to make target '/linux/input.h', needed by
'src/keymap/keys.txt'.  Stop.
ERROR: oe_runmake failed
WARNING:
/home/rpjday/oe/builds/qemux86/tmp/work/i586-poky-linux/udev/182-r9/temp/run.do_compile.30377:1
exit 1 from
  exit 1
ERROR: Function failed: do_compile (log file is located at
/home/rpjday/oe/builds/qemux86/tmp/work/i586-poky-linux/udev/182-r9/temp/log.do_compile.30377)

  in any event, is there a *preferred* way to build using fedora
rawide at this point?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp

2015-03-31 Thread Khem Raj 

 On Mar 30, 2015, at 8:14 PM, Maninder Singh maninder...@samsung.com wrote:
 
 Hi,
 
 From 05ab779af24baef957972aa1d2a9e9d29212cc4c Mon Sep 17 00:00:00 2001
 From: Maninder Singh maninder...@samsung.com 
 mailto:maninder...@samsung.com
 Date: Thu, 19 Mar 2015 03:02:59 +0530
 Subject: [PATCH 1/1] Remove extra check for ld-linux.so.3 in strcmp
   
 if (! strcmp (soname, ld-linux.so.2)
   || ! strcmp (soname, ld-linux.so.3)  
   || ! strcmp (soname, ld.so.1)
   || ! strcmp (soname, ld-linux-ia64.so.2)
   || ! strcmp (soname, ld-linux-x86-64.so.2)
   || ! strcmp (soname, ld64.so.1)
   || ! strcmp (soname, ld-linux.so.3) --- 
 redundant code
   || ! strcmp (soname, ld-linux-armhf.so.3))
 
 Signed-off-by: Maninder Singh 

use First Last your@email

 ---
 src/get.c |1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
 diff --git a/src/get.c b/src/get.c
 index 6a63f02..a34668a 100644
 --- a/src/get.c
 +++ b/src/get.c
 @@ -35,7 +35,6 @@ is_ldso_soname (const char *soname)
|| ! strcmp (soname, ld-linux-ia64.so.2)
|| ! strcmp (soname, ld-linux-x86-64.so.2)
|| ! strcmp (soname, ld64.so.1)
 -  || ! strcmp (soname, ld-linux.so.3)
|| ! strcmp (soname, ld-linux-armhf.so.3))
  return 1;
return 0;
 -- 
 1.7.1
 
 
 Thanks and Regards,
 Maninder Singh
 201503310844012_QKNMBDIF.gif
 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org mailto:yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto 
 https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [oe] tip and cu utility

2015-03-31 Thread Martin Jansa 
On Tue, Mar 31, 2015 at 10:03:07AM +, PRAVEEN KUMAR R wrote:
 Is there any existing package that provide tip and cu utility ?

http://layers.openembedded.org/layerindex/branch/master/recipes/

 
 
 http://man.cx/TIP(1)?
 ?
 
 -- 
 ___
 Openembedded-devel mailing list
 openembedded-de...@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] what is the proper way to build with fedora rawhide/gcc-5.0?

2015-03-31 Thread Burton, Ross 
On 31 March 2015 at 20:54, Robert P. J. Day rpj...@crashcourse.ca wrote:

   in any event, is there a *preferred* way to build using fedora
 rawide at this point?


Blimey, gcc 5 looks like a barrel of laughs.  Is installing gcc 4.x
alongside 5.0 possible, and then set BUILD_CC etc?

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] package update staging

2015-03-31 Thread akuster808 

Morning all,

now that fido is nearing, what is the best method for staging package 
updates meant for oe-core?


regards,
Armin
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] what is the proper way to build with fedora rawhide/gcc-5.0?

2015-03-31 Thread Khem Raj 

 On Mar 31, 2015, at 12:54 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
 
 
  i asked about this a few weeks ago, finally getting back to it ...
 for better or worse, i'm running fedora rawhide, updated to the point
 where i have gcc-5.0.0:
 
 $ gcc --version
 gcc (GCC) 5.0.0 20150208 (Red Hat 5.0.0-0.10)
 Copyright (C) 2015 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.  There is NO
 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 $
 
 which causes a number of build issues trying to build for something as
 simple as qemux86.
 
  first, there is a linemarkers issue with gcc-5.0 that i got around
 by adding to local.conf:
 
  CPPFLAGS_append=  -P”

This should not be required. Can you post the failing package with error details
it should be fixed.

 
 and there were two native build issues due to gcc-5.0 being far
 pickier with warnings that i sidestepped with the cheap hack:
 
  ASSUME_PROVIDED += elfutils-native
  ASSUME_PROVIDED += binutils-native”

There is 2.25 update available on my contrib tree.
http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
should help with binutils.

 
 at this point, the build was almost complete when i hit another
 compile error for udev on the target:
 
 DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common',
 'common-linux', 'common-glibc', 'i586-linux', 'common']
 DEBUG: Executing shell function do_compile
 NOTE: make -j 8
 make: *** No rule to make target '/linux/input.h', needed by
 'src/keymap/keys.txt'.  Stop.

that seems to be unrelated to gcc 5.0 on host. May be you have a different 
issue there.

 ERROR: oe_runmake failed
 WARNING:
 /home/rpjday/oe/builds/qemux86/tmp/work/i586-poky-linux/udev/182-r9/temp/run.do_compile.30377:1
 exit 1 from
  exit 1
 ERROR: Function failed: do_compile (log file is located at
 /home/rpjday/oe/builds/qemux86/tmp/work/i586-poky-linux/udev/182-r9/temp/log.do_compile.30377)
 
  in any event, is there a *preferred* way to build using fedora
 rawide at this point?

I think people will care when fedora 22 comes out later this summer or may be 
when they have beta’s coming out.

 
 rday
 
 -- 
 
 
 Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
 
 Twitter:   http://twitter.com/rpjday
 LinkedIn:   http://ca.linkedin.com/in/rpjday
 
 
 -- 
 ___
 yocto mailing list
 yocto@yoctoproject.org
 https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] Gracefully abort if rootfs.img gets to big

2015-03-31 Thread Paul Eggleton 
Hi Chris,

Great to see you at ELC!

On Monday 30 March 2015 19:17:46 Chris Hallinan wrote:
 Great catching up with you last week, and thanks for looking at my
 patch.  I supposed it's a double edged sword.  If we make it a
 variable, it can be set wrong and the build hang again.  OTOH, 128MB
 is probably way more space than we really need to reserve, and I
 supposed if someone were just banging up against the limit, they might
 want to tweak it.  I'll defer to the collective judgement of the
 group, and resubmit if that's the consensus.

Is there any practical way we can measure the actual size of these files?

 Oh, and silly me...I figured the mail list daemon would put the
 [Yocto] tag on the patch. Since it seems to tag our posts, that is a
 mystery to me.

The mailing list always prepends the list name to the subject of posted 
messages.

A few other notes:

1) This patch should be sent to the openembedded-c...@lists.openembedded.org 
mailing list rather than here. 

2) The YP bugzilla reference should be of the format [YOCTO #7541] .

3) The shortlog (first line of the commit message / subject) should be prefixed 
with the area/file the patch is changing i.e. for this one it should be  
bootimg.bbclass: gracefully abort if rootfs.img gets to big.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [PATCH] LSI AXXIA updates to 3.4 standard/axxia/base

2015-03-31 Thread Bruce Ashfield 

On 03/31/2015 05:04 AM, Cristian Bercaru wrote:

Hello, Bruce!

Sorry for the duplicate mails. I had some trouble with my Internet
connection and I resent the patch.

I can apply this patch just fine on 'standard/axxia/base' of a freshly
cloned linux-yocto-3.4:
arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update)

I think you tried to apply another patch that you already applied.
Please check you mailbox again.


Hmm. It was actually an appended mbox, so I was applying yours and
another!

I've now merged this change.

Bruce



  yow-bashfiel-d4 [/home/brucgit-merge] git am -s a.mbox
  Applying: arch/powerpc/kernel: Address IBM PPC476 erratum 47

Thanks,
Cristian

On 03/30/2015 09:39 PM, Bruce Ashfield wrote:

On 2015-03-30 01:10 PM, cristian.berc...@windriver.com wrote:

From: Cristian Bercaru cristian.berc...@windriver.com

Hello! This patch is an update to IBM PPC476 erratum 48 fix and it is
tagged with the latest 3.4 tag: lsi_axxia_linux_7.8.1.43.


This came through multiple times .. is this the right version ? This
patch won't apply to the linux-yocto-3.4 standard/axxxia/base branch:

yow-bashfiel-d4 [/home/brucgit-merge] git am -s a.mbox
Applying: arch/powerpc/kernel: Address IBM PPC476 erratum 47
error: patch failed: arch/powerpc/kernel/head_44x.S:1249
error: arch/powerpc/kernel/head_44x.S: patch does not apply
Patch failed at 0001 arch/powerpc/kernel: Address IBM PPC476 erratum 47
The copy of the patch that failed is found in:

/home/bruce/poky-kernel/linux-yocto-3.4.git-merge/.git/rebase-apply/patch
When you have resolved this problem, run git am --continue.
If you prefer to skip this patch, run git am --skip instead.
To restore the original branch and stop patching, run git am --abort.

Bruce



Sangeetha Rao (1):
   arch/powerpc/kernel: Address IBM PPC476 erratum 48 (update)

  arch/powerpc/kernel/traps.c |6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)






--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [yocto] what is the proper way to build with fedora rawhide/gcc-5.0?

2015-03-31 Thread Robert P. J. Day 
On Tue, 31 Mar 2015, Khem Raj wrote:

  On Mar 31, 2015, at 12:54 PM, Robert P. J. Day rpj...@crashcourse.ca 
  wrote:
 
 
   i asked about this a few weeks ago, finally getting back to it ...
  for better or worse, i'm running fedora rawhide, updated to the point
  where i have gcc-5.0.0:
 
  $ gcc --version
  gcc (GCC) 5.0.0 20150208 (Red Hat 5.0.0-0.10)
  Copyright (C) 2015 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  $
 
  which causes a number of build issues trying to build for something as
  simple as qemux86.
 
   first, there is a linemarkers issue with gcc-5.0 that i got around
  by adding to local.conf:
 
   CPPFLAGS_append=  -P”

 This should not be required. Can you post the failing package with
 error details it should be fixed.

  for people not sure what i'm talking about, this issue was
identified back in feb at red hat:

https://lists.fedoraproject.org/pipermail/devel/2015-February/207549.html

the package that initially tripped me up was ncurses-native, and
ncurses is indeed mentioned in that lengthy list of packages.

  i can try another build without -P and note the packages that fail
if that's useful, although i assume anyone else can trivially do the
same thing.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] fatal: A branch named 'meta-orig' already exists.

2015-03-31 Thread Robert P. J. Day 

  oh, what fresh hell is this?

... snip ...
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_validate_branches (log file is located at
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
ERROR: Logfile of failure stored in:
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| NOTE: Setting branch meta to
9e70b482d3773abf92c9c5850e134cbca1d5651f
| fatal: A branch named 'meta-orig' already exists.

  this is building core-image-minimal for qemux86, and i'm assuming
this is not fedora rawhide related.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] spitools : Add new package

2015-03-31 Thread Andrei Gherzan 
Hello guys,

On Mon, Mar 30, 2015 at 5:33 PM, Gary Thomas g...@mlbassoc.com wrote:

 On 2015-03-30 00:20, texierp wrote:

 Signed-off-by: texierp ouf_du...@hotmail.com
 ---
   recipes-devtools/spitools/spitools_git.bb | 1 +
   1 file changed, 1 insertion(+)

 diff --git a/recipes-devtools/spitools/spitools_git.bb
 b/recipes-devtools/spitools/spitools_git.bb
 index 287e3eb..128ad7f 100644
 --- a/recipes-devtools/spitools/spitools_git.bb
 +++ b/recipes-devtools/spitools/spitools_git.bb
 @@ -1,5 +1,6 @@
   DESCRIPTION = This package contains some simple command line tools to
 help using Linux spidev devices
   HOMEPAGE = https://github.com/cpb-/spi-tools;
 +AUTHOR = Christophe BLAESS
   LICENSE=GPLv2
   LIC_FILES_CHKSUM = file://LICENSE;md5=8c1ae6c159876a0ba630996143
 81



 The email subject line doesn't match what's happening in the patch.

Also, why put this in meta-raspberrypi?  It probably makes more
 sense to put it in meta-oe since it doesn't seem to be RaspberryPi
 specific.


Gary has a fair point here. First of all this patch seems to fix the AUTHOR
and I would rebase it into the initial one. On the other hand meta-oe
should be the place where to submit it. I'm saying this because I don't see
how is this rpi specific.

Thanks,

-- 
*Andrei Gherzan*
*e: **and...@gherzan.ro and...@gherzan.ro*
*w: *www.gherzan.ro
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] RaspberryPi B+, bitbake make killed, unfinished jobs

2015-03-31 Thread Andrei Gherzan 
Hello Tzy,

On Sun, Mar 29, 2015 at 6:59 AM, Tzy User tzy13...@gmail.com wrote:

 I am trying to build a new kernel for RaspberryPi model B+ with this
 configuration:

 Build Configuration:
 BB_VERSION= 1.24.0
 BUILD_SYS = x86_64-linux
 NATIVELSBSTRING   = Debian-GNU-Linux-7
 TARGET_SYS= arm-poky-linux-gnueabi
 MACHINE   = raspberrypi
 DISTRO= poky
 DISTRO_VERSION= 1.7.1
 TUNE_FEATURES = arm armv6 vfp
 TARGET_FPU= vfp
 meta
 meta-yocto
 meta-yocto-bsp= dizzy-dev:82c843842854c7e2e87bf7762c3f9e83b3e2bf1b
 meta-raspberrypi  = dizzy-dev:efd760d0a2c027fe20ed190c56f416d0a47d7c41


 The make gets killed, then waiting for unfinished jobs...
 .
 /bin/bash
 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/../move-if-change
 tmp-opinit.c insn-opinit.c
 echo timestamp  s-opinit
 build/genautomata

 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/config/arm/
 arm.md
 \
  insn-conditions.md  tmp-automata.c
 /bin/bash: line 1: 16677 Killed  build/genautomata

 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/config/arm/
 arm.md
 insn-conditions.md  tmp-automata.c
 make[1]: *** [s-automata] Error 137
 make[1]: *** Waiting for unfinished jobs
 /bin/bash
 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/../move-if-change
 tmp-attrtab.cinsn-attrtab.c
 /bin/bash
 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/../move-if-change
 tmp-dfatab.c insn-dfatab.c
 /bin/bash
 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/gcc/../move-if-change
 tmp-latencytab.c insn-latencytab.c
 echo timestamp  s-attrtab
 rm gcc.pod
 make[1]: Leaving directory

 `/mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work/x86_64-poky-linux-gnueabi/gcc-cross-arm/4.9.1-r0/gcc-4.9.1/build.x86_64-linux.arm-poky-linux-gnueabi/gcc'
 make: *** [all-gcc] Error 2
 ERROR: oe_runmake failed
 WARNING: exit code 1 from a shell command.
 ERROR: Function failed: do_compile (log file is located at

 /mnt/sdb1/projects/yocto/build/raspberrypi-3.18/tmp/work/x86_64-poky-linux-gnueabi/gcc-cross-arm/4.9.1-r0/temp/log.do_compile.15332)


This is indeed strange. Can you test and see if other kernel providers get
compiled? For example one for a qemuarm machine.

-- 
*Andrei Gherzan*
*e: **and...@gherzan.ro and...@gherzan.ro*
*w: *www.gherzan.ro
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] fatal: A branch named 'meta-orig' already exists.

2015-03-31 Thread Bruce Ashfield 

On 2015-03-31 6:26 PM, Robert P. J. Day wrote:


   oh, what fresh hell is this?

... snip ...
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_validate_branches (log file is located at
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524)
ERROR: Logfile of failure stored in:
/home/rpjday/oe/builds/qemux86/tmp/work/qemux86-poky-linux/linux-yocto/3.19.2+gitAUTOINC+9e70b482d3_31b35da6a5-r0/temp/log.do_validate_branches.17524
Log data follows:
| DEBUG: Executing shell function do_validate_branches
| NOTE: Setting branch meta to
9e70b482d3773abf92c9c5850e134cbca1d5651f
| fatal: A branch named 'meta-orig' already exists.

   this is building core-image-minimal for qemux86, and i'm assuming
this is not fedora rawhide related.


You've got a borked tree sitting in work-shared. If you clean-all
and start again, does it show up ?

If it repeats, then it very well could be the version of git in
rawhide that is causing the issue.

Bruce



rday



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto