Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

2014-08-25 Thread Khem Raj
On 14-08-21 17:01:47, Vladimir Redzhepov wrote:
 From f0305398a51435f407e41a8f0eaf83f8bdd13cca Mon Sep 17 00:00:00 2001
 From: Vladimir Redzhepov vladimir_redzhe...@epam.com
 Date: Thu, 21 Aug 2014 19:43:29 +0300
 Subject: [PATCH] update jdk and jre to version 67
 
 Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
 ---
 recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse.inc |  4 ++--
 5 files changed, 22 insertions(+), 22 deletions(-)
 
 diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
 b/recipes-devtools/oracle-java/oracle-jse.inc
 index 3a4e20d..38ceef0 100644
 --- a/recipes-devtools/oracle-java/oracle-jse.inc
 +++ b/recipes-devtools/oracle-java/oracle-jse.inc
 @@ -2,8 +2,8 @@ LICENSE_FLAGS = oracle_java
 LICENSE = Oracle_Binary_Code_License_Agreement
 LIC_FILES_CHKSUM = \

 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/LICENSE;md5=98f46ab6481d87c4d77e0e91a6dbc15f
  \
 -  
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/COPYRIGHT;md5=3a11238025bf13b87f04753183ffeb90
  \
 -
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=c339b34e3da6673d2c5950d0f8808f8c
  \
 + 
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/COPYRIGHT;md5=be9fe5d47a7dcfb78f142f487afb34bb
  \
 +
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=f3a388961d24b8b72d412a079a878cdb
  \


what changed in these files that ensues change in checksums ?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [OE-core] RFC: Improving the developer workflow

2014-08-25 Thread Paul Eggleton
Hi Nicolas,

Apologies for the delayed reply.

On Friday 08 August 2014 10:04:19 Nicolas Dechesne wrote:
 On Thu, Aug 7, 2014 at 11:10 AM, Paul Eggleton
 paul.eggle...@linux.intel.com wrote:
  Example workflow
  
  
  I won't give a workflow for every possible usage, but just to give a basic
  example - let's assume you want to build a new piece of software for
  which you have your own source tree on your machine. The rough set of
  steps required would be something like this (rough, e.g. the command
  names given shouldn't be read as final):
  
  1. Install the SDK
  
  2. Run a setup script to make the SDK tools available
  
  3. Add a new recipe with sdktool add recipename - interactive process.
  The tool records that recipename is being worked on, creates a recipe
  that can be used to build the software using your external source tree,
  and places the recipe where it will be used automatically by other steps.
  
  4. Build the recipe with sdktool build recipename. This probably only
  goes as far as do_install or possibly do_package_qa; in any case the QA
  process would be less stringent than with the standard build system
  however in order to avoid putting too many barriers in the way of testing
  on the target.
  
  5. Fix any failures and repeat from the previous step as necessary.
  
  6. Deploy changes to target with sdktool deploy-target ip address
  assuming SSH is available on the target. Alternatively sdktool
  build-image imagename can be used to regenerate an image with the
  changes in it; sdktool runqemu could do that (if necessary) and then
  run the result within QEMU with the appropriate options set.
 
 coincidentally, i was giving an OE workshop this week, and when I
 explained about the OE SDK, someone immediately brought up that it was
 quite limited because:
 
  1- SDK cannot be used to generate deployable packages, e.g.  using
 the SDK to create ipk/deb/rpm that can be delivered to
 targets/clients, not just for debugging, but also for production when
 production system has package management support.
  2- SDK cannot be used to regenerate updated images. e.g. Company A
 delivers a SDK + board, Company B is making a product using the SDK
 (adding content) and wants to be able to make new images with the new
 content in order to sell/deploy it.

I have included solutions for these two in my proposal. However, I am a bit 
concerned about it being used in the way you describe above. The main aim is 
to provide tools for developers to test their changes on the target easily; if 
people start using it to produce images that they then send to other people 
(particularly customers or other organisations) then the potential end-game is 
an image used in production is one produced from a single developer's machine, 
at which point you may have some reproducibility issues - where's the source 
for package xyz? Erm, not sure, that developer left six months ago...

Of course there's nothing we'll really be able to do to stop people from using 
the tools in this way, so it's mainly going to be an exercise in documenting 
the right way to use them. It's worth thinking about these problems though 
especially if you want to encourage best practices.

  3- SDK itself cannot be upgraded when the 'base image' and SDK are updated
  4- SDK users cannot add content to the SDK. e.g. I am a SDK user I
 create a library and I want that library to be in the SDK now.

We're certainly aiming to take care of these last two - indeed #4 is one of 
the main drivers behind the proposed new SDK.

Cheers,
Paul

-- 

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


Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

2014-08-25 Thread Vladimir Redzhepov
diff -u jre1.7.0_25/COPYRIGHT jre1.7.0_67/COPYRIGHT 
--- jre1.7.0_25/COPYRIGHT   2013-06-06 07:12:23.0 +0300
+++ jre1.7.0_67/COPYRIGHT   2014-07-25 19:07:26.0 +0300
@@ -1,4 +1,4 @@
-Copyright � 1993, 2013, Oracle and/or its affiliates. 
+Copyright � 1993, 2014, Oracle and/or its affiliates. 
 All rights reserved.

diff -u jre1.7.0_25/THIRDPARTYLICENSEREADME.txt 
jre1.7.0_67/THIRDPARTYLICENSEREADME.txt 
--- jre1.7.0_25/THIRDPARTYLICENSEREADME.txt 2013-06-06 07:12:23.0 
+0300
+++ jre1.7.0_67/THIRDPARTYLICENSEREADME.txt 2014-07-25 19:07:26.0 
+0300
@@ -1912,6 +1912,35 @@
 
 ---
 
+%% This notice is provided with respect to Sparkle v.1.5,
+which is included with JRE 7 on Mac OS X.
+
+--- begin of LICENSE ---
+
+Copyright (c) 2012 Sparkle.org and Andy Matuschak
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the Software), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+--- end of LICENSE ---
+
+---
+
 %% Portions licensed from Taligent, Inc.
 
 ---
@@ -3169,12 +3198,12 @@
 %% This notice is provided with respect to the following which is 
 included with JRE 7, JDK 7, and OpenJDK 7, except where noted:
 
-  Apache Derby 10.8.1.2[included with JDK 7 only]
+  Apache Derby 10.8.3.0[included with JDK 7 only]
   Apache Jakarta BCEL 5.2 
   Apache Jakarta Regexp 1.4 
   Apache Santuario XMLSec-Java 1.4.2
   Apache Xalan-Java 2.7.1 
-  Apache Xerces2 Java 2.10.0 
+  Apache Xerces2 Java 2.11.0 
   Apache XML Resolver 1.1

-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: Monday, August 25, 2014 9:41 AM
To: Vladimir Redzhepov
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

On 14-08-21 17:01:47, Vladimir Redzhepov wrote:
 From f0305398a51435f407e41a8f0eaf83f8bdd13cca Mon Sep 17 00:00:00 2001
 From: Vladimir Redzhepov vladimir_redzhe...@epam.com
 Date: Thu, 21 Aug 2014 19:43:29 +0300
 Subject: [PATCH] update jdk and jre to version 67
 
 Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
 ---
 recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse.inc |  4 ++--
 5 files changed, 22 insertions(+), 22 deletions(-)
 
 diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
 b/recipes-devtools/oracle-java/oracle-jse.inc
 index 3a4e20d..38ceef0 100644
 --- a/recipes-devtools/oracle-java/oracle-jse.inc
 +++ b/recipes-devtools/oracle-java/oracle-jse.inc
 @@ -2,8 +2,8 @@ LICENSE_FLAGS = oracle_java
 LICENSE = Oracle_Binary_Code_License_Agreement
 LIC_FILES_CHKSUM = \

 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/LICENSE;md5=98f46ab6481d87c4d77e0e91a6dbc15f
  \
 -  
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/COPYRIGHT;md5=3a11238025bf13b87f04753183ffeb90
  \
 -
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=c339b34e3da6673d2c5950d0f8808f8c
  \
 + 
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/COPYRIGHT;md5=be9fe5d47a7dcfb78f142f487afb34bb
  \
 +
 file://${WORKDIR}/${JDK_JRE}${PV}_${PV_UPDATE}/THIRDPARTYLICENSEREADME.txt;md5=f3a388961d24b8b72d412a079a878cdb
  \


what changed in these files that ensues change in checksums ?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Error:MinGW based toolchain for 64bit windows

2014-08-25 Thread atulkumar singh
Hi All,

Have anyone worked on mingw based toolchain for 64bit windows.
I have build the MinGW toolchain for 64 bit windows.
But while executing a program, i am getting error as as.exe cannot start
or run due to incompatibility with 64-bit version of windows
Please help me on the same.

Thanks and regards,
Atul kumar singh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

2014-08-25 Thread Vladimir Redzhepov


-Original Message-
From: Martin Jansa [mailto:martin.ja...@gmail.com] 
Sent: Thursday, August 21, 2014 8:23 PM
To: Vladimir Redzhepov
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

On Thu, Aug 21, 2014 at 05:01:47PM +, Vladimir Redzhepov wrote:
 From f0305398a51435f407e41a8f0eaf83f8bdd13cca Mon Sep 17 00:00:00 2001
 From: Vladimir Redzhepov vladimir_redzhe...@epam.com
 Date: Thu, 21 Aug 2014 19:43:29 +0300
 Subject: [PATCH] update jdk and jre to version 67
 
 Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
 ---
 recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb   | 10 +-
 recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
 recipes-devtools/oracle-java/oracle-jse.inc |  4 ++--
 5 files changed, 22 insertions(+), 22 deletions(-)
 
 diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb 
 b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
 index 978fbd5..07fa39b 100644
 --- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
 +++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
 @@ -1,9 +1,9 @@
 -PR = r0
 -PV_UPDATE = 25
 +PR = r1
 +PV_UPDATE = 67

Does it need PR update?

I thought that PR should be updated each time we modify recipe. That's why I've 
updated it.

  require oracle-jse-jdk.inc
 -SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
 +SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-i586.tar.gz;

It would be better to use PV_UPDATE variable here and maybe introduce
another one for build number?

Do you mean using PV_UPDATE in SRC_URI like this
SRC_URI = http://download.oracle.com/otn-pub/java/jdk/7u${ PV_UPDATE 
}-b01/jdk-7u${ PV_UPDATE }-linux-i586.tar.gz ?

Of course we can use additional variable for build number, for example 
BUILD_NUM = b01
SRC_URI = http://download.oracle.com/otn-pub/java/jdk/7u${ PV_UPDATE 
}-${BUILD_NUM}/jdk-7u${ PV_UPDATE }-linux-i586.tar.gz

 -SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
 -SRC_URI[sha256sum] = 
 dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
 +SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
 +SRC_URI[sha256sum] = 
 b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
 diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb 
 b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
 index 7979401..8bad119 100644
 --- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
 +++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
 @@ -1,9 +1,9 @@
 -PR = r0
 -PV_UPDATE = 25
 +PR = r1
 +PV_UPDATE = 67
  require oracle-jse-jdk.inc
 -SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
 +SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-x64.tar.gz;
 -SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
 -SRC_URI[sha256sum] = 
 f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
 +SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
 +SRC_URI[sha256sum] = 
 54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
 diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb 
 b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
 index 6125025..4165d74 100644
 --- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
 +++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
 @@ -1,9 +1,9 @@
 -PR = r0
 -PV_UPDATE = 25
 +PR = r1
 +PV_UPDATE = 67
  require oracle-jse-jre.inc
 -SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
 +SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jre-7u67-linux-i586.tar.gz;
 -SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
 -SRC_URI[sha256sum] = 
 4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
 +SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
 +SRC_URI[sha256sum] = 
 eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
 diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb 
 b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
 index 4058d23..a1474a9 100644
 --- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
 +++ b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
 @@ -1,9 +1,9 @@
 -PR = r0
 -PV_UPDATE = 25
 +PR = r1
 +PV_UPDATE = 67
  require oracle-jse-jre.inc
 -SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-x64.tar.gz;
 +SRC_URI = 
 http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jre-7u67-linux-x64.tar.gz;
 -SRC_URI[md5sum] = 743ee0ebf73ce428c912866d84e374e0
 -SRC_URI[sha256sum] = 
 3c4496316fb413d5ab0590e9971676a521b9a600b3ceaac311f04c18c98a98c0
 

Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 67

2014-08-25 Thread Martin Jansa
On Mon, Aug 25, 2014 at 01:00:08PM +, Vladimir Redzhepov wrote:
 
 
 -Original Message-
 From: Martin Jansa [mailto:martin.ja...@gmail.com] 
 Sent: Thursday, August 21, 2014 8:23 PM
 To: Vladimir Redzhepov
 Cc: yocto@yoctoproject.org
 Subject: Re: [yocto] [meta-oracle-java][PATCH] update jdk and jre to version 
 67
 
 On Thu, Aug 21, 2014 at 05:01:47PM +, Vladimir Redzhepov wrote:
  From f0305398a51435f407e41a8f0eaf83f8bdd13cca Mon Sep 17 00:00:00 2001
  From: Vladimir Redzhepov vladimir_redzhe...@epam.com
  Date: Thu, 21 Aug 2014 19:43:29 +0300
  Subject: [PATCH] update jdk and jre to version 67
  
  Signed-off-by: Vladimir Redzhepov vladimir_redzhe...@epam.com
  ---
  recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb   | 10 +-
  recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb | 10 +-
  recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb   | 10 +-
  recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb | 10 +-
  recipes-devtools/oracle-java/oracle-jse.inc |  4 ++--
  5 files changed, 22 insertions(+), 22 deletions(-)
  
  diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb 
  b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
  index 978fbd5..07fa39b 100644
  --- a/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
  +++ b/recipes-devtools/oracle-java/oracle-jse-jdk-i586_1.7.0.bb
  @@ -1,9 +1,9 @@
  -PR = r0
  -PV_UPDATE = 25
  +PR = r1
  +PV_UPDATE = 67
 
 Does it need PR update?
 
 I thought that PR should be updated each time we modify recipe. That's why 
 I've updated it.

We have automated PR service for that
https://wiki.yoctoproject.org/wiki/PR_Service

so please drop PR variable instead.

   require oracle-jse-jdk.inc
  -SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-i586.tar.gz;
  +SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-i586.tar.gz;
 
 It would be better to use PV_UPDATE variable here and maybe introduce
 another one for build number?
 
 Do you mean using PV_UPDATE in SRC_URI like this
 SRC_URI = http://download.oracle.com/otn-pub/java/jdk/7u${ PV_UPDATE 
 }-b01/jdk-7u${ PV_UPDATE }-linux-i586.tar.gz ?
 
 Of course we can use additional variable for build number, for example 
 BUILD_NUM = b01
 SRC_URI = http://download.oracle.com/otn-pub/java/jdk/7u${ PV_UPDATE 
 }-${BUILD_NUM}/jdk-7u${ PV_UPDATE }-linux-i586.tar.gz
 

Yes, that's what I meant (without the spaces around PV_UPDATE), that way
it's easier to see what was changed in recipe when reviewing updates like this.

  -SRC_URI[md5sum] = 23176d0ebf9dedd21e3150b4bb0ee776
  -SRC_URI[sha256sum] = 
  dd89b20afa939992bb7fdc44837fa64f0a98d7ee1e5706fe8a2d9e2247ba6de7
  +SRC_URI[md5sum] = 715b0e8ba2a06bded75f6a92427e2701
  +SRC_URI[sha256sum] = 
  b6231064ad2c9fbbcb099dba17b1dcf12033e922b9c24e4348b9a01e9ebaa85c
  diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb 
  b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
  index 7979401..8bad119 100644
  --- a/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
  +++ b/recipes-devtools/oracle-java/oracle-jse-jdk-x86-64_1.7.0.bb
  @@ -1,9 +1,9 @@
  -PR = r0
  -PV_UPDATE = 25
  +PR = r1
  +PV_UPDATE = 67
   require oracle-jse-jdk.inc
  -SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jdk-7u25-linux-x64.tar.gz;
  +SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-linux-x64.tar.gz;
  -SRC_URI[md5sum] = 83ba05e260813f7a9140b76e3d37ea33
  -SRC_URI[sha256sum] = 
  f80dff0e19ca8d038cf7fe3aaa89538496b80950f4d10ff5f457988ae159b2a6
  +SRC_URI[md5sum] = 81e3e2df33e13781e5fac5756ed90e67
  +SRC_URI[sha256sum] = 
  54dd1e13edf18c64941a55da9c91210b53dc5cf48f1a8f4538c863049e346335
  diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb 
  b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
  index 6125025..4165d74 100644
  --- a/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
  +++ b/recipes-devtools/oracle-java/oracle-jse-jre-i586_1.7.0.bb
  @@ -1,9 +1,9 @@
  -PR = r0
  -PV_UPDATE = 25
  +PR = r1
  +PV_UPDATE = 67
   require oracle-jse-jre.inc
  -SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u25-b15/jre-7u25-linux-i586.tar.gz;
  +SRC_URI = 
  http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jre-7u67-linux-i586.tar.gz;
  -SRC_URI[md5sum] = 0e9ccefe49e937e592dbb605f2e8e7d8
  -SRC_URI[sha256sum] = 
  4016965536d8607743267812ab04e6d428036dda432893748c1df6cb77b09628
  +SRC_URI[md5sum] = 2a256eb2a91f0084e58c612636342c2b
  +SRC_URI[sha256sum] = 
  eadec83a54d3a9d09248a8d16b21c03da9afffc7317e775fb8db962620a0781d
  diff --git a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb 
  b/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
  index 4058d23..a1474a9 100644
  --- a/recipes-devtools/oracle-java/oracle-jse-jre-x86-64_1.7.0.bb
  +++ 

[yocto] Unexpected redirection error in script

2014-08-25 Thread Chris Tapp
I've previously used expressions of the form:

   IFS=. read -r $a $b $c $d  $IP

to split an IP address into its octets.

However, when I try this for generic_pc under daisy I get an Unexpected 
redirection error.

Is this to do with the Busybox version/configuration or something else?

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com




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


Re: [yocto] Unexpected redirection error in script

2014-08-25 Thread Maciej Borzecki
On Monday 25 of August 2014 17:50:00 Chris Tapp wrote:
 I've previously used expressions of the form:
 
IFS=. read -r $a $b $c $d  $IP
try:

echo $IP | IFS=. read -r a b c d

 
 to split an IP address into its octets.
 
 However, when I try this for generic_pc under daisy I get an Unexpected
 redirection error.
 
 Is this to do with the Busybox version/configuration or something else?
Busybox uses ash shell. Bash tricks like this won't work.


-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you. 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Bundling initramfs with uImage

2014-08-25 Thread Crast, Nicholas
Thanks,

This seems like a clean way to do what I want to do. So this means whenever I 
do a build, it will 

1.) Build the kernel
2.) Build the filesystem (initramfs)
3.) Rebuild the kernel with the bundled intramfs

Correct?

-Nick


Nick Crast
Associate Software Engineer
Saab Sensis Corporation
Phone: 315-445-5703
Email: nicholas.cr...@saabsensis.com


-Original Message-
From: Khem Raj [mailto:raj.k...@gmail.com] 
Sent: Monday, August 25, 2014 1:32 AM
To: Crast, Nicholas
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Bundling initramfs with uImage

On 14-08-21 20:18:41, Crast, Nicholas wrote:
 All,
 
 I am currently working in an embedded environment, struggling to get the 
 entire system running in RAM, so that everything is fresh after a reboot. I 
 can currently use the initramfs-live-boot functionality to generate a 
 .cpio.gz file, but I am lost on how to get this to 'bundle' with the uImage. 
 The uImage will be stored on an SD card and we are using u-boot.
 
 I see mentions of the CONFIG_INITRAMFS_SOURCE kernel option, but I am unsure 
 if I need to change this.
 
 Can someone help me? I've been googling all day and haven't gotten much 
 further.

if you add 

INITRAMFS_IMAGE_BUNDLE = 1
INITRAMFS_IMAGE = name of your initramfs-image

in you local.conf that should help it to create uImage with everything in it.

-Khem

-
This message is intended only for the addressee and may contain information 
that is company confidential or privileged.  Any technical data in this message 
may be exported only in accordance with the U.S. International Traffic in Arms 
Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 
CFR Parts 730-774). Unauthorized use is strictly prohibited and may be 
unlawful. If you are not the intended recipient, or the person responsible for 
delivering to the intended recipient, you should not read, copy, disclose or 
otherwise use this message. If you have received this email in error, please 
delete it, and advise the sender immediately. 
-  
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Unexpected redirection error in script

2014-08-25 Thread Chris Tapp

On 25 Aug 2014, at 18:07, Maciej Borzecki maciej.borze...@open-rnd.pl wrote:

 On Monday 25 of August 2014 17:50:00 Chris Tapp wrote:
 I've previously used expressions of the form:
 
   IFS=. read -r $a $b $c $d  $IP
 try:
 
 echo $IP | IFS=. read -r a b c d
 
 
 to split an IP address into its octets.
 
 However, when I try this for generic_pc under daisy I get an Unexpected
 redirection error.
 
 Is this to do with the Busybox version/configuration or something else?
 Busybox uses ash shell. Bash tricks like this won't work.

Thanks - I hadn't spotted that the Cedartrail BSP links /bin/sh to /bin/bash 
and not the Busybox binary.

 -- 
 
 Maciej Borzęcki 
 Senior Software Engineer Open-RnD Sp. z o.o. 
 www.open-rnd.pl, Facebook, Twitter 
 mobile: +48 telefon, fax: +48 42 657 9079 
 
 Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
 poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
 których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
 zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim 
 przypadku 
 uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
 nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 
 
 This message, including any attachments hereto, may contain privileged or 
 confidential information and is sent solely for the attention and use of the 
 intended addressee(s). If you are not an intended addressee, you may neither 
 use this message nor copy or deliver it to anyone. In such case, you should 
 immediately destroy this message and kindly notify the sender by reply email. 
 Thank you.

--

Chris Tapp
opensou...@keylevel.com
www.keylevel.com




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


Re: [yocto] best bet for WiFi Yocto experience?

2014-08-25 Thread Rudolf Streif
Hi Pete,


Please provide a recommendation for a low cost, out of the box WiFi
 (802.11n) experience using Yocto.

 Are you looking for a board that has WiFi on board? The Wandboard (
http://www.wandboard.org/) or the Cubietruck (
http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1)
have that for example.



 AFAIK, Raspberry Pi doesn't come with WiFi built in.

 Correct, but you could use a WiFi/BT USB dongle for a couple of bucks.


 I would like to spend less than $100 but could stretch it.

 Wandboard and Cubietruck are both less than $100.


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


Re: [yocto] New kernel error after syncing

2014-08-25 Thread akuster808

Khem

it was the config option not being set..

seems like a kernel bug to me.. kconfig or otherwise.

thanks for the help.
- Armin

On 08/24/2014 05:14 PM, Bruce Ashfield wrote:

On Sun, Aug 24, 2014 at 7:02 PM, akuster808 akuster...@gmail.com wrote:


Hello,

Is anyone else seeing kernel build issue on 3.14 with the resent updates?


I am getting the following errors on ppc64 (standard/qemuppc). x86-64 built
fine (core-image-minimal). building ppc now.


Hopefully qemuppc is building 32 bit :) .. but outside of that, I was
able to build 3.14
fine on Friday.  But I just started another build to see if something
snuck past in the
recent feature merges.

Bruce



|   LD  init/built-in.o
| mm/built-in.o: In function `.vm_cgroup_css_alloc':
| vm_cgroup.c:(.text+0x7103c): undefined reference to `.res_counter_init'
| vm_cgroup.c:(.text+0x71090): undefined reference to `.res_counter_init'
| mm/built-in.o: In function `.vm_cgroup_read_u64':
| vm_cgroup.c:(.text+0x711c4): undefined reference to
`.res_counter_read_u64'
| mm/built-in.o: In function `.vm_cgroup_charge_memory_mm':
| (.text+0x71348): undefined reference to `.res_counter_charge'
| mm/built-in.o: In function `.vm_cgroup_uncharge_memory_mm':
| (.text+0x713a0): undefined reference to `.res_counter_uncharge'
| mm/built-in.o: In function `.vm_cgroup_charge_shmem':
| (.text+0x71508): undefined reference to `.res_counter_charge'
| mm/built-in.o: In function `.vm_cgroup_uncharge_shmem':
| (.text+0x71560): undefined reference to `.res_counter_uncharge'
| make[2]: *** [vmlinux] Error 1
| make[1]: *** [sub-make] Error 2
| make: *** [all] Error 2

- armin
--
___
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] New kernel error after syncing

2014-08-25 Thread Khem Raj
On 14-08-25 15:56:57, akuster808 wrote:
 Khem
 
 it was the config option not being set..
 
 seems like a kernel bug to me.. kconfig or otherwise.

OK, I was thinking may be it would help if we should somehow review the 
linux-yocto kernel patches may be on this mailing list too may be just a FYI
pointing to a git.yp.org showing the commits that went between the SRCREV 
bumps in metadata, Bruce does a great job of explaining what has changed 
but hey show me the code :). But if they already are then ignore me.

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


Re: [yocto] best bet for WiFi Yocto experience?

2014-08-25 Thread Anooj Gopi
May be this helps:

http://www.wandboard.org/


On Mon, Aug 25, 2014 at 10:53 PM, Rudolf Streif rstr...@linuxfoundation.org
 wrote:

 Hi Pete,


  Please provide a recommendation for a low cost, out of the box WiFi
 (802.11n) experience using Yocto.

 Are you looking for a board that has WiFi on board? The Wandboard (
 http://www.wandboard.org/) or the Cubietruck (
 http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1)
 have that for example.



  AFAIK, Raspberry Pi doesn't come with WiFi built in.

 Correct, but you could use a WiFi/BT USB dongle for a couple of bucks.


  I would like to spend less than $100 but could stretch it.

 Wandboard and Cubietruck are both less than $100.


 Cheers,
 :rjs

 --
 ___
 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] best bet for WiFi Yocto experience?

2014-08-25 Thread Khem Raj
On 14-08-25 13:53:01, Rudolf Streif wrote:
 Hi Pete,
 
 
 Please provide a recommendation for a low cost, out of the box WiFi
  (802.11n) experience using Yocto.
 
  Are you looking for a board that has WiFi on board? The Wandboard (
 http://www.wandboard.org/) or the Cubietruck (
 http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1)
 have that for example.

a bit expensive but well supported in OE/YP universe
https://store.gumstix.com/index.php/products/526/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto