date:20130531

[yocto] Differnt build result of same u-boot source with differnet binutils

2013-05-31 Thread Luo Zhenhua-B19537

When the u-boot(HEAD of master in git://git.freescale.com/ppc/sdk/u-boot.git) 
of p1022ds is built with different binutils in Yocto, the result is different. 

With binutils-2.23.1(last version in Yocto), u-boot can be built correctly. 
With binutils-2.23.2(current version in Yocto), the build failed as following:
| release.S: Assembler messages:
| release.S:236: Error: value of 4294963524 too large for field of 2 bytes at 
170
| release.S:237: Error: operand out of range (0xf144 is not between 
0x and 0x)
| release.S:237: Error: value of 4294963524 too large for field of 2 bytes at 
174
| release.S:365: Error: value of 4294963524 too large for field of 2 bytes at 
206
| release.S:366: Error: operand out of range (0xf144 is not between 
0x and 0x)
| release.S:366: Error: value of 4294963524 too large for field of 2 bytes at 
210
| release.S:390: Error: value of 4294963520 too large for field of 2 bytes at 
278
| release.S:391: Error: operand out of range (0xf140 is not between 
0x and 0x)
| release.S:391: Error: value of 4294963520 too large for field of 2 bytes at 
282

Below is the failed code section:
[..snip..]
233 #define toreset(x) (x - __secondary_start_page + 0xf000)
234 
235 /* get our PIR to figure out our table entry */
236 lis r3,toreset(__spin_table_addr)@h
237 ori r3,r3,toreset(__spin_table_addr)@l
238 lwz r3,0(r3)
[..snip..]

Seems like the build error is related to binutils, can somebody shed some light 
on the issue? Thanks in advance. 


Best Regards,

Zhenhua

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

[yocto] [QA] Discussion tag

2013-05-31 Thread Georgescu, Alexandru C

Hello,

As agreed in the last Yocto Project Technical meetings, to make sure we can 
filter better the QA related discussions, all the e-mails must have the [QA] 
tag in the subject. If there will be sufficient traffic on the mailing list 
regarding QA, a separate list will be created.

Regards,
--
Alexandru Georgescu
Yocto QA Engineer
SSG/SSD Open Source Technology Center Romania

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

Re: [yocto] [meta-ivi][RFC] packagegroups: restructure the yocto-ivi PGs

2013-05-31 Thread Ahsan, Noor

Hello Holger and Florin,

Do you have any comments on the following?

Thanks.

Noor

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Usman, Fahad
Sent: Tuesday, May 28, 2013 12:58 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] [meta-ivi][RFC] packagegroups: restructure the yocto-ivi 
PGs

Hi all,
Kindly review the following change.

Thanks,
Fahad

On Wed, May 22, 2013 at 1:00 PM, Fahad Usman 
mailto:fahad_us...@mentor.com>> wrote:
with the current implementation of packagegroups, it's not clear how a
particular recipe map to the GENIVI baseline document.

this scheme remove confusion about which packagegroup a certain recipe belong
to. And provide guidance to the customers about modifying the image. For
instance customers should be careful about replacing specific-p1 components if
they wish to maintain GENIVI compliance.

Signed-off-by: Fahad Usman 
mailto:fahad_us...@mentor.com>>
---
 recipes-yocto-ivi/images/foton-image.bb |  
8 +++-
 
.../packagegroup-foton-abstract-component-p1.bb
 | 21 +
 ... => 
packagegroup-foton-abstract-component-p2.bb}
 | 14 ++
 
.../packagegroup-foton-placeholder-component-p1.bb
  | 20 
 ... => 
packagegroup-foton-specific-component-p1.bb}
 | 21 +++--
 
.../packagegroup-foton-specific-component-p2.bb
 | 19 +++
 6 files changed, 80 insertions(+), 23 deletions(-)
 create mode 100644 
recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p1.bb
 rename 
recipes-yocto-ivi/packagegroups/{packagegroup-core-p2.bb
 => 
packagegroup-foton-abstract-component-p2.bb}
 (61%)
 create mode 100644 
recipes-yocto-ivi/packagegroups/packagegroup-foton-placeholder-component-p1.bb
 rename 
recipes-yocto-ivi/packagegroups/{packagegroup-core-p1.bb
 => 
packagegroup-foton-specific-component-p1.bb}
 (67%)
 create mode 100644 
recipes-yocto-ivi/packagegroups/packagegroup-foton-specific-component-p2.bb

diff --git a/recipes-yocto-ivi/images/foton-image.bb 
b/recipes-yocto-ivi/images/foton-image.bb
index 6532519..f83aaf9 100644
--- a/recipes-yocto-ivi/images/foton-image.bb
+++ b/recipes-yocto-ivi/images/foton-image.bb
@@ -4,6 +4,12 @@ include recipes-yocto-ivi/images/ivi-image.inc
 PV = "4.0.0"
 #PR = "r1"

-IMAGE_INSTALL_append = " packagegroup-core-p1 packagegroup-core-p2"
+IMAGE_INSTALL_append = " \
+packagegroup-foton-abstract-component-p1 \
+packagegroup-foton-placeholder-component-p1 \
+packagegroup-foton-specific-component-p2 \
+packagegroup-foton-abstract-component-p2 \
+packagegroup-foton-specific-component-p1 \
+"

 # Add image specific packages
diff --git 
a/recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p1.bb
 
b/recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p1.bb
new file mode 100644
index 000..9ff02b2
--- /dev/null
+++ 
b/recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p1.bb
@@ -0,0 +1,21 @@
+DESCRIPTION = "GENIVI 4.0 (Foton) P1 Abstract components (AC)"
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = 
"file://${IVI_COREBASE}/meta-ivi/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PR = "r0"
+
+inherit packagegroup
+
+PACKAGES = "\
+packagegroup-foton-abstract-component-p1 \
+"
+
+ALLOW_EMPTY = "1"
+
+RDEPENDS_${PN} += "\
+bluez4 \
+bluez4-systemd \
+eglibc \
+layer-management \
+obex-client \
+obexd \
+"
diff --git 
a/recipes-yocto-ivi/packagegroups/packagegroup-core-p2.bb
 
b/recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p2.bb
similarity index 61%
rename from 
recipes-yocto-ivi/packagegroups/packagegroup-core-p2.bb
rename to 
recipes-yocto-ivi/packagegroups/packagegroup-foton-abstract-component-p2.bb
index e9b7b86..ac6af13 100644
--- 
a/recipes-yocto-ivi/packagegroups/packagegroup-core-p2.bb
+++ 
b/recipes-yocto-ivi/packagegroups/packagegrou

[yocto] [PATCH] Fix Thread Access exception for systemtap Dialogs

2013-05-31 Thread Ioana Grigoropol

- when displaying MessageDialogs an error occurs due to illegal thread 
accessing GUI classes
- in order to fix this, a new DialogRunnable is used, that will use 
invoke synchronous to display the message dialog

[Yocto #4585]
Signed-off-by: Ioana Grigoropol 
---
 .../src/org/yocto/remote/utils/DialogRunnable.java |   26 
 .../src/org/yocto/remote/utils/ShellSession.java   |   13 ++
 2 files changed, 34 insertions(+), 5 deletions(-)
 create mode 100644 
plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/DialogRunnable.java

diff --git 
a/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/DialogRunnable.java 
b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/DialogRunnable.java
new file mode 100644
index 000..5fbab76
--- /dev/null
+++ 
b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/DialogRunnable.java
@@ -0,0 +1,26 @@
+package org.yocto.remote.utils;
+
+import org.eclipse.jface.dialogs.MessageDialog;
+
+public class DialogRunnable implements Runnable{
+   int type = 0;
+   boolean result;
+   public static final int QUESTION = 1;
+   public static final int ERROR = 2;
+   String title;
+   String message;
+
+   DialogRunnable(String title, String message, int type){
+   this.title = title;
+   this.message = message;
+   this.type = type;
+   }
+   @Override
+   public void run() {
+   if (type == QUESTION) {
+   result = MessageDialog.openQuestion(null, title, 
message);
+   } else if (type == ERROR) {
+   MessageDialog.openError(null, title, message);
+   }
+   }
+}
\ No newline at end of file
diff --git 
a/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java 
b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
index 0f4097b..4ac8001 100644
--- 
a/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
+++ 
b/plugins/org.yocto.remote.utils/src/org/yocto/remote/utils/ShellSession.java
@@ -22,7 +22,7 @@ import java.lang.reflect.InvocationTargetException;
 import java.util.regex.Matcher;
 import java.util.regex.Pattern;
 
-import org.eclipse.jface.dialogs.MessageDialog;
+import org.eclipse.swt.widgets.Display;
 
 public class ShellSession {
/**
@@ -242,7 +242,9 @@ public class ShellSession {
int keys = new 
Integer(m.group(1));
if (keys == 0) {
proc.destroy();
-   accepted = 
MessageDialog.openQuestion(null, "Host authenticity", "The authenticity of host 
'" + host + "(" + host + ")' can't be established.\nAre you sure you want to 
continue connecting ?");
+   DialogRunnable 
runnable = new DialogRunnable("Host authenticity", "The authenticity of host '" 
+ host + "(" + host + ")' can't be established.\nAre you sure you want to 
continue connecting ?", DialogRunnable.QUESTION);
+   
Display.getDefault().syncExec(runnable);
+   accepted = 
runnable.result;
if (accepted){
proc = 
Runtime.getRuntime().exec("ssh -o StrictHostKeyChecking=no " + user + "@" + 
host);//add host key to known_hosts
try {
@@ -252,7 +254,7 @@ public class ShellSession {
}

proc.destroy();
} else {
-   
MessageDialog.openError(null, "Host authenticity", "Host key verification 
failed.");
+   
Display.getDefault().syncExec( new DialogRunnable("Host authenticity", "Host 
key verification failed.", DialogRunnable.ERROR));
}
} else {
String errorMsg 
= "";
@@ -280,8 +282,9 @@ public class ShellSession {

buffer.delete(0, buffer.length());
}
}
-

Re: [yocto] External-Sourcery-Toolchain Related Issue

2013-05-31 Thread Rohit2 Jindal

Thanks for your reply.

Can you give me pointers how to setup my toolchain from scratch in yocto .
Which RECIPES I have to refer to setup my own toolchain recipes .

Thanks in advance

Regards,
Rohit Jindal

From: Rohit2 Jindal
Sent: Thursday, May 23, 2013 1:09 PM
To: 'yocto@yoctoproject.org'; 'yocto-ow...@yoctoproject.org'
Subject: External-Sourcery-Toolchain Related Issue


Hi,



I want to install my existing Toolchain to Yocto Sysroot bypassing default 
yocto toolchain functionality.



My requirements are



1I will download toolchain from my git source ie tar file.

2I just want to install this toolchain to tmp/sysroot folder in build directory 
skipping compilation step.





Steps implemented



1 SRC_URI = "file:///home/toolchains_bin.tar"

2 TCMODE="external-csl"

3 EXTERNAL_TOOLCHAIN = 
"/home/yocto/poky/build/tmp/work/mips64-poky-linux/external-sourcery-toolchain/GCC-r8/toolchains_bin/mipscross/linux"

4CSL_TARGET_SYS_mips64 = "${TARGET_ARCH}${TARGET_TC_VENDOR}-${TCTYPE}"

5CSL_TARGET_SYS = "${TARGET_ARCH}${TARGET_TC_VENDOR}-${TCTYPE}"

6 TARGET_PREFIX = "${CSL_TARGET_SYS_mips64}-"



But when I tried to run

Build> bitbake linux (linux is recipe in my layer)



It gives me error :



ERROR: Failed to obtain CodeSourcery toolchain version: Execution of 
'/home/yocto/poky/build/tmp/work/mips64-poky-linux/external-sourcery-toolchain/GCC-r8/toolchains_bin/mipscross/linux/bin/mips64-nlm-linux-gcc
 -v' failed: command not found

ERROR: Failed to obtain CodeSourcery toolchain version: Execution of 
'/home/yocto/poky/build/tmp/work/mips64-poky-linux/external-sourcery-toolchain/GCC-r8/toolchains_bin/mipscross/linux/bin/mips64-nlm-linux-gcc
 -v' failed: command not found



and continue with the tasks executions like unpacking toolchains_bin.tar to 
$WORKDIR/mips64-poky-linux/.. and other linux do configure etc





Again run this recipe:

@Build>bitbake linux

NOTE. Once unpacked the toolchain to the location specified if I  again run the 
above recipe then this error does not come.





Please suggest me the way around to skip this error coming at the first time 
when I build my recipe until my toolchain is not unpacked.





Thanks in advance!





Regards,

Rohit Jindal
































===
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-docs][PATCH] dev-manual: correct location of license data

2013-05-31 Thread Trevor Woerner

After a build, the license data is found in ${TMPDIR}/deploy/licenses not
${TMPDIR}/deploy/images/licenses.

Signed-off-by: Trevor Woerner 
---
 documentation/dev-manual/dev-manual-newbie.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/dev-manual/dev-manual-newbie.xml 
b/documentation/dev-manual/dev-manual-newbie.xml
index 779d06d..e5d6f32 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -782,7 +782,7 @@
 Once the build completes, the list of all licenses found and used 
during that build are
 kept in the
 Build Directory at
-tmp/deploy/images/licenses.
+tmp/deploy/licenses.
 
 
 
-- 
1.8.3.rc1.44.gb387c77

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

[yocto] Differnt build result of same u-boot source with differnet binutils

[yocto] [QA] Discussion tag

Re: [yocto] [meta-ivi][RFC] packagegroups: restructure the yocto-ivi PGs

[yocto] [PATCH] Fix Thread Access exception for systemtap Dialogs

Re: [yocto] External-Sourcery-Toolchain Related Issue

[yocto] [yocto-docs][PATCH] dev-manual: correct location of license data

6 matches

Site Navigation

Mail list logo

Footer information