Date   

Re: [PATCH] Fix incompatibility with jre1.6 support for typed HashMap

Grigoropol, IoanaX <ioanax.grigoropol@...>
 

Hi Jessica,

I double checked and everything applies correctly on jzhang/windows-build.
The option --keep-cr expects to receive a patch who's line terminator is carriage return, maybe in the process of saving & applying the patches these line terminators get removed somehow?
I can send you the patches on email as an attachment and you can download them as such and apply them onto windows-build branch in order to prevent any alterations to the files.

Thanks,
Ioana

-----Original Message-----
From: Zhang, Jessica
Sent: Saturday, December 08, 2012 1:01 AM
To: Grigoropol, IoanaX; yocto@yoctoproject.org
Subject: RE: [yocto] [PATCH] Fix incompatibility with jre1.6 support for typed HashMap

Hi Ioana,

Seems the patch won't apply even with the --keep-cr flag. This is against jzhang/windows-build branch.

Can you double check?

Thanks,
Jessica

git am --keep-cr ~/mbox/\[yocto\]_\[PATCH_7_8\]_convert_CRLF_line_terminators_to_CR_only.mbox
Applying: convert CRLF line terminators to CR only
/home/jzhang/eclipse-poky-windows/.git/rebase-apply/patch:79: trailing whitespace.
public FiniteStateWizard() {
/home/jzhang/eclipse-poky-windows/.git/rebase-apply/patch:81: trailing whitespace.

/home/jzhang/eclipse-poky-windows/.git/rebase-apply/patch:96: trailing whitespace.

/home/jzhang/eclipse-poky-windows/.git/rebase-apply/patch:101: trailing whitespace.
super.createPageControls(pageContainer);
/home/jzhang/eclipse-poky-windows/.git/rebase-apply/patch:112: trailing whitespace.

error: patch failed: plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/FiniteStateWizard.java:1
error: plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/FiniteStateWizard.java: patch does not apply
error: patch failed: plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/FiniteStateWizardPage.java:1
error: plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/FiniteStateWizardPage.java: patch does not apply Patch failed at 0001 convert CRLF line terminators to CR only When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".

-----Original Message-----
From: Grigoropol, IoanaX
Sent: Thursday, December 06, 2012 6:02 AM
To: Zhang, Jessica; yocto@yoctoproject.org
Subject: RE: [yocto] [PATCH] Fix incompatibility with jre1.6 support for typed HashMap

Hi Jessica,

There seems to be a bit of a mix-up on the new branch in the order of the patches were applied. Also, some files modified under Linux have CRLF ending instead of CR.
Can you please rebase the branch (the new one or the old one) to commit ec4fcf7b478f59e190d9b9fe9b56e44971c4f66c, and then apply the set of 8 patches I resent to the mailing list ?
Bare in mind that the patch before last (that converts from CRLF to CR) will not apply unless applied with option --keep-cr.

Thanks,
Ioana

-----Original Message-----
From: Zhang, Jessica
Sent: Thursday, December 06, 2012 1:12 AM
To: Grigoropol, IoanaX; yocto@yoctoproject.org
Subject: RE: [yocto] [PATCH] Fix incompatibility with jre1.6 support for typed HashMap

Hi Ioana,

None of your patches of today apply so there seems to be some rebase issue. Also, I've added headless build support changes for windows BC plugin, so can you rebase against jzhang/windows-build and resubmit the patch series?

Thanks,
Jessica

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Ioana Grigoropol
Sent: Wednesday, December 05, 2012 2:41 AM
To: yocto@yoctoproject.org
Subject: [yocto] [PATCH] Fix incompatibility with jre1.6 support for typed HashMap

Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
---
.../remote/utils/YoctoHostShellProcessAdapter.java | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/YoctoHostShellProcessAdapter.java b/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/YoctoHostShellProcessAdapter.java
index 9ab43cf..2dba0a6 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/YoctoHostShellProcessAdapter.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/YoctoHostShe
+++ llProcessAdapter.java
@@ -34,6 +34,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {

private Semaphore sem;

+
public YoctoHostShellProcessAdapter(IHostShell hostShell, ProcessStreamBuffer processStreamBuffer, CommandResponseHandler commandResponseHandler) throws IOException {
super(hostShell);
this.processStreamBuffer = processStreamBuffer; @@ -41,7 +42,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
this.calculator = new GitCalculatePercentage();
this.sem = new Semaphore(1);
this.command = "";
- this.commandMonitors = new HashMap<>();
+ this.commandMonitors = new HashMap<String, IProgressMonitor>();
}

public String getLastCommand() {
@@ -50,7 +51,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {

public synchronized void setLastCommand(String lastCommand) {
try {
- // there are still some processes that might take a long time and if we do not wait for them,
+ // there are still some processes that might take a long time and if
+we do not wait for them,
// then the semaphore will not be released, because an interrupted exception will occur
Thread.sleep(2000);
isFinished = false;
@@ -70,6 +71,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {

private class GitCalculatePercentage implements ICalculatePercentage {
final Pattern pattern = Pattern.compile("^Receiving objects:\\s*(\\d+)%.*");
+ @Override
public float calWorkloadDone(String info) throws IllegalArgumentException {
Matcher m = pattern.matcher(info.trim());
if(m.matches()) {
@@ -88,13 +90,16 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
}

private void updateMonitor(final int work){
+
Display.getDefault().asyncExec(new Runnable() {
+
@Override
public void run() {
if (getMonitor() != null) {
getMonitor().worked(work);
}
}
+
});
}

@@ -124,7 +129,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
updateMonitor(delta);
reportedWorkload += delta;
}
-
+
if (reportedWorkload == RemoteHelper.TOTALWORKLOAD)
doneMonitor();
}
@@ -152,8 +157,9 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
continue;
}
setCommandPrompt(value);
+
if (commandPrompt != null && endChar != null && command != null && processStreamBuffer != null &&
- value.startsWith(commandPrompt) && value.endsWith(endChar) &&
+ value.startsWith(commandPrompt) && value.endsWith(endChar) &&
!value.endsWith(command) && processStreamBuffer.getLastOutputLineContaining(command) != null /*&& waitForOutput*/) {
sem.release();
isFinished = true;
@@ -165,7 +171,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
this.commandResponseHandler.response(value, false);
}
}
-
+
}
private void setCommandPrompt(String value) {
if (commandPrompt == null) {
@@ -178,7 +184,7 @@ public class YoctoHostShellProcessAdapter extends HostShellProcessAdapter {
commandPrompt = value.substring(0, end);
endChar = PROMPT_USER_CH;
}
-
+
}
}
public boolean isFinished() {
--
1.7.9.5

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


[PATCHv2 3/3] script/build.sh: Added option to enable building from local repository.

mail@...
 

From: Timo Mueller <timo.mueller@bmw-carit.de>

If the script is called with the -l option the local git repository is
used instead of the upstream repository.
---
scripts/build.sh | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)

diff --git a/scripts/build.sh b/scripts/build.sh
index 693dcf7..54081d5 100755
--- a/scripts/build.sh
+++ b/scripts/build.sh
@@ -7,6 +7,7 @@ help ()
echo ""
echo "Options:"
echo "-h - display this help and exit"
+ echo "-l - use local git repository"
echo "BRANCH_NAME - git branch name to build upon"
echo "RELEAES_NAME - release name in the final output name"
echo "TAG_NAME - git tag name to build upon. defaults to HEAD if not set"
@@ -67,11 +68,14 @@ check_env ()
}

USE_LOCAL_GIT_REPO=0
-while getopts ":h" opt; do
+while getopts ":lh" opt; do
case $opt in
h)
help
;;
+ l)
+ USE_LOCAL_GIT_REPO=1
+ ;;
esac
done
shift $(($OPTIND - 1))
--
1.7.7.6


[PATCHv2 2/3] scripts/build.sh: Added help option to the cmdline

mail@...
 

From: Timo Mueller <timo.mueller@bmw-carit.de>

Calling the build script with the -h option will now show the usage.
The cmdline parsing can be extended to add new options in the future.
---
scripts/build.sh | 18 ++++++++++++++----
1 files changed, 14 insertions(+), 4 deletions(-)

diff --git a/scripts/build.sh b/scripts/build.sh
index cbb7375..693dcf7 100755
--- a/scripts/build.sh
+++ b/scripts/build.sh
@@ -3,12 +3,13 @@
help ()
{
echo "Build the Yocto Eclipse plugins"
- echo "Usage: $0 <branch name> <release name>";
+ echo "Usage: $0 [OPTIONS] BRANCH_NAME RELEASE_NAME [TAG_NAME]";
echo ""
echo "Options:"
- echo "<branch name> - git branch name to build upon"
- echo "<release name> - release name in the final output name"
- echo "[tag name] - git tag name to build upon. defaults to master if not set"
+ echo "-h - display this help and exit"
+ echo "BRANCH_NAME - git branch name to build upon"
+ echo "RELEAES_NAME - release name in the final output name"
+ echo "TAG_NAME - git tag name to build upon. defaults to HEAD if not set"
echo ""
echo "Example: $0 master r0 M1.1_rc1";
exit 1;
@@ -66,6 +67,15 @@ check_env ()
}

USE_LOCAL_GIT_REPO=0
+while getopts ":h" opt; do
+ case $opt in
+ h)
+ help
+ ;;
+ esac
+done
+shift $(($OPTIND - 1))
+

if [ $# -ne 2 ] && [ $# -ne 3 ]; then
help
--
1.7.7.6


[PATCHv2 1/3] scripts/build.sh: Added function to use the local repository for building

mail@...
 

From: Timo Mueller <timo.mueller@bmw-carit.de>

If USE_LOCAL_GIT_REPO is set to 1 the build scripts uses the local
repository of the eclipse poky project for building instead of the
upstream project. The local repository is derived from the location
for the build script.
---
scripts/build.sh | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/scripts/build.sh b/scripts/build.sh
index de81ce3..cbb7375 100755
--- a/scripts/build.sh
+++ b/scripts/build.sh
@@ -65,6 +65,8 @@ check_env ()
fi
}

+USE_LOCAL_GIT_REPO=0
+
if [ $# -ne 2 ] && [ $# -ne 3 ]; then
help
fi
@@ -97,6 +99,12 @@ mkdir ${BUILD_DIR} || fail $? "Create temporary build directory ${BUILD_DIR}"

#git clone
GIT_URL=git://git.pokylinux.org/eclipse-poky.git
+if [ $USE_LOCAL_GIT_REPO -eq 1 ]; then
+ SCRIPT_DIR=`dirname $0`
+ GIT_DIR=`readlink -f ${SCRIPTDIR}\..`
+ GIT_URL="file://${GIT_DIR}"
+fi
+
GIT_DIR=${BUILD_SRC}
#mkdir ${GIT_DIR}
#cp -r features/ ${GIT_DIR}
--
1.7.7.6


[PATCHv2 0/3][eclipse-poky] Add option to allow building from local repo

mail@...
 

From: Timo Mueller <timo.mueller@bmw-carit.de>

Hi,

I've rebased the patch series. It should now apply to the current master.

Best regards,
Timo

From the original cover letter:
<snip>
if you build eclipse-poky with the provided build script it will always use
the upstream version of the IDE.
During development I wanted to use my local repository to make sure that my
changes don't break the build system. Therefor I added an option to the build
script to allow building from the local eclipse-poky git repository.
</snip>

Timo Mueller (3):
scripts/build.sh: Added function to use the local repository for
building
scripts/build.sh: Added help option to the cmdline
script/build.sh: Added option to enable building from local
repository.

scripts/build.sh | 30 ++++++++++++++++++++++++++----
1 files changed, 26 insertions(+), 4 deletions(-)

--
1.7.7.6


I think my kernel image just went back in time...

Chris Tapp
 

In tmp/deploy/images:

1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended -20121209214459.bin

2) Cleaned the image and the task it contained (to pick up some changes on rebuild) and deleted the image files (.hddimg, etc.) in tmp/deploy/images making sure to leave the kernel files intact.

3) Rebuilt the image. The bzImage now has a timestamp of 2012-12-09 11:13 and the name ends -20121209105420.bin

This looks to me like the kernel image has reverted to an earlier one! It is certainly behaving as if this is the case, because a kernel option that I added is no longer in the deployed image...

Chris Tapp

opensource@keylevel.com
www.keylevel.com


meta-cedartrail - where is grub configured for 'install' option?

Chris Tapp
 

I am trying to change the 'install' behaviour for the meta-cedartrail image so that the installed system has a different grub.cfg file. Is there a file I can bbappend to achieve this?

image_live.bbclass refers to the 'install' syslinux label that triggers the install, but I've not been able to get from this to how/where grub.cfg is created.

Chris Tapp

opensource@keylevel.com
www.keylevel.com


Re: bitbake -c devshell option

Bruce Ashfield
 




On Sun, Dec 9, 2012 at 3:05 PM, Marco <koansoftware@...> wrote:
Hello,
I was used to work with oe-classic.
When I used oe-classic, often I used the 'devshell' option to try to compile (make uImage) the kernel with the entire environment set up correctly.
Now if I do the same procedure with Yocto 8 Danny it does not work.
For example I'm using a default configuration below:

1st step
---
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "danny:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 912 tasks of which 912 didn't need to be rerun and all succeeded.


2nd step just after 1st
------------------------
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

- Devshell starts in a new screen
------------------------
$ pwd
~/yocto-8-danny/poky/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3/linux

- lauch a kernel build (as I was used to do)
------------------------
$ make
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.


I would like to find out whether you can still do this and what is the new way to go

As Chris said, this way should still work, and it does work here for me. There's
one thing that you may notice with kernel's that have split source/build dirs
(like linux-yocto), is that once you have gone through the configure phase
and drop into the devshell you may not have KBUILT_OUTPUT set to the 
build directory, and end up dropping files in the source dir .. which causes you
mrproper and build issue.

I have a local append to devshell that sets:

      d.setVar("KBUILD_OUTPUT", "${B}")

To make sure things work.  If you need something like this as well, or have
problems with linux-yocot, I can arrange to have something like this added
by default. But since no one else has asked about it, I assumed no one else
is either using devshell, or they haven't run into it.

Cheers,

Bruce


 

TIA
--
Marco Cavallini
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto



--
"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"


Re: bitbake -c devshell option

Chris Larson <clarson@...>
 



On Sun, Dec 9, 2012 at 1:05 PM, Marco <koansoftware@...> wrote:
I was used to work with oe-classic.
When I used oe-classic, often I used the 'devshell' option to try to compile (make uImage) the kernel with the entire environment set up correctly.
Now if I do the same procedure with Yocto 8 Danny it does not work.
For example I'm using a default configuration below:

1st step
---
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

Build Configuration:
BB_VERSION        = "1.16.0"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.3"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp    = "danny:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 912 tasks of which 912 didn't need to be rerun and all succeeded.


2nd step just after 1st
------------------------
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

- Devshell starts in a new screen
------------------------
$ pwd
~/yocto-8-danny/poky/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3/linux

- lauch a kernel build (as I was used to do)
------------------------
$ make
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.


I would like to find out whether you can still do this and what is the new way to go


devshell runs with the source tree unpacked and patched. It has never guaranteed that the sources would already be *configured* at that time, either in oe-classic or current. Run a bitbake -c configure virtual/kernel first, or just use -c menuconfig.
--
Christopher Larson


bitbake -c devshell option

Marco <koansoftware@...>
 

Hello,
I was used to work with oe-classic.
When I used oe-classic, often I used the 'devshell' option to try to compile (make uImage) the kernel with the entire environment set up correctly.
Now if I do the same procedure with Yocto 8 Danny it does not work.
For example I'm using a default configuration below:

1st step
---
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

Build Configuration:
BB_VERSION = "1.16.0"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "poky"
DISTRO_VERSION = "1.3"
TUNE_FEATURES = "armv7a vfp neon cortexa8"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp = "danny:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 912 tasks of which 912 didn't need to be rerun and all succeeded.


2nd step just after 1st
------------------------
MACHINE="beagleboard" bitbake -c devshell virtual/kernel

- Devshell starts in a new screen
------------------------
$ pwd
~/yocto-8-danny/poky/build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-r4.3/linux

- lauch a kernel build (as I was used to do)
------------------------
$ make
scripts/kconfig/conf --silentoldconfig Kconfig
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.


I would like to find out whether you can still do this and what is the new way to go

TIA
--
Marco Cavallini


Re: meta-cedartrail - install to sdb fails to boot

Chris Tapp
 

On 9 Dec 2012, at 16:20, Chris Tapp wrote:

I've built an image using meta-cedartrail and copied the .hdd image onto a USB drive.

Booting the 'install' label install as expected to an mSATA SSD as sda on an Intel DN2800MT board and this boots as expected.

However, I need to use an eUSB SSD. The installer detects this as 'sdb' and installs ok, but the system fails to boot with a 'kernel panic' reporting that the root FS can't be found. The grub boot specifies:

set root=(hd0,1)

... root=/dev/sdb2

Which looks reasonable. The serial console diagnostics "... here are the available partitions:" entry does not list __any__ partitions. Does this mean that the driver required is currently a module and needs to be configured as a built-in? If so, is there an easy way to work out which one?

Adding

rootdelay=5

to the kernel command line means the kernel then sees the USB boot device. It is also sda2 (rather than sdb2, as installed), so I also needed to set

root=/dev/sda2

Chris Tapp

opensource@keylevel.com
www.keylevel.com


cannot find the pre-built kernel image for qemu for 1.3

Tim Coote <tim+yoctoproject.org@...>
 

Hullo
I'm sure that this is an obvious mistake on my part, but I cannot spot what I'm doing wrong. I'm pulling together an initial arm instance under qemu, following the instructions here: http://bit.ly/UObwg0. I'm using fedora, but I don't think that's relevant.

For 1.3, I cannot find the pre-built kernel images. I'd expect there to be a .bin file in here: http://bit.ly/UObPHz In the same way that the 1.2 kernel's in here: http://bit.ly/UObTXV

Have I missed something? is it somewhere else?

tia

Tim


eglibc-2.13: backport sotruss from eglibc-2.16

Elvis Dowson
 

Hi Khem,
                 I get the following error while attempting to backport support for the older eglibc-2.13 recipe and gcc-4.5.4, to make it work with the latest poky master.

I got the image to build and execute correctly, temporarily by commenting out the parts relating to sotruss, and it worked on my powerpc 440 target with softfloat.

Now, I just want to update the eglibc-2.13 recipe, so that it works correctly with poky master. I patched the eglibc-2.13 sources and it builds the required files.

However, during the installation phase, I get a problem, in that the scripts attempt to install libsotruss.so to the root folder on my host machine, instead of the yocto build folder:

/usr/bin/install -c /tool/yocto/poky/build/tmp/work/ppc405-poky-linux/eglibc/2.13-r32/build-powerpc-poky-linux/elf/sotruss-lib.so /sotruss-lib.so.new
/usr/bin/install -c /tool/yocto/poky/build/tmp/work/ppc405-poky-linux/eglibc/2.13-r32/build-powerpc-poky-linux/elf/sprof /tool/yocto/poky/build/tmp/work/ppc405-poky-linux/eglibc/2.13-r32/image/usr/bin/sprof.new

(cd /tool/yocto/poky/build/tmp/work/ppc405-poky-linux/eglibc/2.13-r32/build-powerpc-poky-linux/elf/.; /tool/yocto/poky/build/tmp/sysroots/x86_64-linux/usr/libexec/ppc405-poky-linux.gcc-cross-initial/gcc/powerpc-poky-linux/4.5.4/objdump -h dl-load.o dl-cache.o dl-lookup.o dl-object.o dl-reloc.o dl-deps.o dl-runtime.o dl-error.o dl-init.o dl-fini.o dl-debug.o dl-misc.o dl-version.o dl-profile.o dl-conflict.o dl-tls.o dl-origin.o dl-scope.o dl-execstack.o dl-open.o dl-close.o dl-trampoline.o dl-support.o dl-iteratephdr.o dl-addr.o enbl-secure.o dl-profstub.o dl-libc.o dl-sym.o dl-tsd.o dl-sysdep.o dl-vdso.o dl-machine.o dl-iteratephdr.os dl-addr.os dl-profstub.os dl-libc.os dl-sym.os dl-tsd.os unwind-dw2-fde-glibc.os dl-vdso.os framestate.os unwind-pe.os rtld.os dl-load.os dl-cache.os dl-lookup.os dl-object.os dl-reloc.os dl-deps.os dl-runtime.os dl-error.os dl-init.os dl-fini.os dl-debug.os dl-misc.os dl-version.os dl-profile.os dl-conflict.os dl-tls.os dl-origin.os dl-scope.os dl-execstack.os dl-caller.os dl-open.os dl-close.os dl-trampoline.os dl-sysdep.os dl-environ.os dl-minimal.os dl-brk.os dl-sbrk.os dl-start.os dl-machine.os soinit.os sofini.os interp.os static-stubs.o cache.o readlib.o xmalloc.o xstrdup.o chroot_canon.o sotruss-lib.os sotruss-lib.so) | \
gawk '/\.gnu\.glibc-stub\./ { \
 sub(/\.gnu\.glibc-stub\./, "", $2); \
 stubs[$2] = 1; } \
END { for (s in stubs) print "#define __stub_" s }' > /tool/yocto/poky/build/tmp/work/ppc405-poky-linux/eglibc/2.13-r32/build-powerpc-poky-linux/elf/stubsT
/usr/bin/install: cannot create regular file `/sotruss-lib.so.new': Permission denied

How can I get past this error?

Best regards,

Elvis Dowson


instructions for running the pre-built poky qemu images

Robert P. J. Day
 

updated an older page on how one can run the pre-built QEMU images:

http://www.crashcourse.ca/wiki/index.php/Running_pre-built_QEMU_images

and there are still three (admittedly minor) issues that one has to
work around to get it to work. the point is to be able to do this
*without* having to install OE or bitbake since, technically, you
don't need them.

1) as i mentioned earlier, the 1.3/ directories for the QEMU images
no longer contain the kernel images. is that deliberate? where are
they now, if anywhere?

2) it appears to be unnecessary to install bitbake just to run the
QEMU images, as long as you set OE_TMPDIR appropriately so that
bitbake doesn't complain and abort.

3) finally, there a mismatch between the directory name that runqemu
expects (x86_64-linux) and where the toolchains are installed by
default (x86_64-pokysdk-linux) which is fixed by a simple symlink but
it's not clear why the mismatch needs to be there in the first place.

and that's it. what's on the new wiki page seems to work.

rday

--

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

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


Re: bbappending a bbappend

Chris Tapp
 


On 9 Dec 2012, at 16:47, Chris Larson wrote:



On Sun, Dec 9, 2012 at 9:44 AM, Chris Tapp <opensource@...> wrote:
On 9 Dec 2012, at 16:30, Chris Larson wrote:

On Sun, Dec 9, 2012 at 7:50 AM, Bruce Ashfield <bruce.ashfield@...> wrote:
On 12-12-09 5:48 AM, Chris Tapp wrote:
On 9 Dec 2012, at 04:47, Bruce Ashfield wrote:




On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp <opensource@...
<mailto:opensource@keylevel.com>> wrote:

    On 9 Dec 2012, at 00:11, Chris Larson wrote:

    On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp
    <opensource@... <mailto:opensource@keylevel.com>> wrote:

        Is it possible to have more than one bbappend applied to a
        recipe?

        I'm using meta-cedartrail with my own layer (which is set as
        lower priority).

        Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to
        be able to enable CONFIG_HID_APPLE in my layer so my Apple
        keyboard works (and keep meta-cedartrail 'clean'). Is it
        possible to use another linux-yocto_3.0.bbappend in my layer?
        I've given it a try, but it's not working and I thought it
        would be an idea to see if it __should__ before I try and fix
        it ;-)


    All bbappends from all layers are applied, in layer priority order.

    Thanks, I was hoping that was the case.

    I wonder why this isn't working then - I think I've done it as
    shown in the dev manual...


Is it something other than the bbappends ? i.e. are you sure you have
all the required
dependencies for CONFIG_HID_APPLE already enabled, or in the same fragment
you are appending ?

menuconfig shows that the dependencies are ok. I've got a single
fragment referenced using a SRC_URI in the bbappend which sets
FILESEXTRAPATHS_prepend. The .cfg file just sets:

CONFIG_HID_APPLE=y

I can't find my .cfg file in the work area, so it seems as if it's not
being picked up.

I'd suggest putting your .bbappend on a pastebin so we can inspect it.


Did you use bitbake -e linux-yocto | grep SRC_URI= to confirm it's listed there?

I have now - it isn't showing. Any syntax errors in the bbappend are detected, so it looks like it's being processed.

--
Christopher Larson



Re: bbappending a bbappend

Chris Larson <clarson@...>
 



On Sun, Dec 9, 2012 at 9:44 AM, Chris Tapp <opensource@...> wrote:
On 9 Dec 2012, at 16:30, Chris Larson wrote:

On Sun, Dec 9, 2012 at 7:50 AM, Bruce Ashfield <bruce.ashfield@...> wrote:
On 12-12-09 5:48 AM, Chris Tapp wrote:
On 9 Dec 2012, at 04:47, Bruce Ashfield wrote:




On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp <opensource@...
<mailto:opensource@keylevel.com>> wrote:

    On 9 Dec 2012, at 00:11, Chris Larson wrote:

    On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp
    <opensource@... <mailto:opensource@keylevel.com>> wrote:

        Is it possible to have more than one bbappend applied to a
        recipe?

        I'm using meta-cedartrail with my own layer (which is set as
        lower priority).

        Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to
        be able to enable CONFIG_HID_APPLE in my layer so my Apple
        keyboard works (and keep meta-cedartrail 'clean'). Is it
        possible to use another linux-yocto_3.0.bbappend in my layer?
        I've given it a try, but it's not working and I thought it
        would be an idea to see if it __should__ before I try and fix
        it ;-)


    All bbappends from all layers are applied, in layer priority order.

    Thanks, I was hoping that was the case.

    I wonder why this isn't working then - I think I've done it as
    shown in the dev manual...


Is it something other than the bbappends ? i.e. are you sure you have
all the required
dependencies for CONFIG_HID_APPLE already enabled, or in the same fragment
you are appending ?

menuconfig shows that the dependencies are ok. I've got a single
fragment referenced using a SRC_URI in the bbappend which sets
FILESEXTRAPATHS_prepend. The .cfg file just sets:

CONFIG_HID_APPLE=y

I can't find my .cfg file in the work area, so it seems as if it's not
being picked up.

I'd suggest putting your .bbappend on a pastebin so we can inspect it.


Did you use bitbake -e linux-yocto | grep SRC_URI= to confirm it's listed there?
--
Christopher Larson


Re: bbappending a bbappend

Chris Tapp
 

On 9 Dec 2012, at 16:30, Chris Larson wrote:

On Sun, Dec 9, 2012 at 7:50 AM, Bruce Ashfield <bruce.ashfield@...> wrote:
On 12-12-09 5:48 AM, Chris Tapp wrote:
On 9 Dec 2012, at 04:47, Bruce Ashfield wrote:




On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp <opensource@...
<mailto:opensource@keylevel.com>> wrote:

    On 9 Dec 2012, at 00:11, Chris Larson wrote:

    On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp
    <opensource@... <mailto:opensource@keylevel.com>> wrote:

        Is it possible to have more than one bbappend applied to a
        recipe?

        I'm using meta-cedartrail with my own layer (which is set as
        lower priority).

        Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to
        be able to enable CONFIG_HID_APPLE in my layer so my Apple
        keyboard works (and keep meta-cedartrail 'clean'). Is it
        possible to use another linux-yocto_3.0.bbappend in my layer?
        I've given it a try, but it's not working and I thought it
        would be an idea to see if it __should__ before I try and fix
        it ;-)


    All bbappends from all layers are applied, in layer priority order.

    Thanks, I was hoping that was the case.

    I wonder why this isn't working then - I think I've done it as
    shown in the dev manual...


Is it something other than the bbappends ? i.e. are you sure you have
all the required
dependencies for CONFIG_HID_APPLE already enabled, or in the same fragment
you are appending ?

menuconfig shows that the dependencies are ok. I've got a single
fragment referenced using a SRC_URI in the bbappend which sets
FILESEXTRAPATHS_prepend. The .cfg file just sets:

CONFIG_HID_APPLE=y

I can't find my .cfg file in the work area, so it seems as if it's not
being picked up.

I'd suggest putting your .bbappend on a pastebin so we can inspect it.



--
Christopher Larson



Re: bbappending a bbappend

Chris Larson <clarson@...>
 

On Sun, Dec 9, 2012 at 7:50 AM, Bruce Ashfield <bruce.ashfield@...> wrote:
On 12-12-09 5:48 AM, Chris Tapp wrote:
On 9 Dec 2012, at 04:47, Bruce Ashfield wrote:




On Sat, Dec 8, 2012 at 7:54 PM, Chris Tapp <opensource@...
<mailto:opensource@keylevel.com>> wrote:

    On 9 Dec 2012, at 00:11, Chris Larson wrote:

    On Sat, Dec 8, 2012 at 5:07 PM, Chris Tapp
    <opensource@... <mailto:opensource@keylevel.com>> wrote:

        Is it possible to have more than one bbappend applied to a
        recipe?

        I'm using meta-cedartrail with my own layer (which is set as
        lower priority).

        Meta-cedartrail has a linux-yocto_3.0.bbappend, but I want to
        be able to enable CONFIG_HID_APPLE in my layer so my Apple
        keyboard works (and keep meta-cedartrail 'clean'). Is it
        possible to use another linux-yocto_3.0.bbappend in my layer?
        I've given it a try, but it's not working and I thought it
        would be an idea to see if it __should__ before I try and fix
        it ;-)


    All bbappends from all layers are applied, in layer priority order.

    Thanks, I was hoping that was the case.

    I wonder why this isn't working then - I think I've done it as
    shown in the dev manual...


Is it something other than the bbappends ? i.e. are you sure you have
all the required
dependencies for CONFIG_HID_APPLE already enabled, or in the same fragment
you are appending ?

menuconfig shows that the dependencies are ok. I've got a single
fragment referenced using a SRC_URI in the bbappend which sets
FILESEXTRAPATHS_prepend. The .cfg file just sets:

CONFIG_HID_APPLE=y

I can't find my .cfg file in the work area, so it seems as if it's not
being picked up.

I'd suggest putting your .bbappend on a pastebin so we can inspect it.
--
Christopher Larson


meta-cedartrail - install to sdb fails to boot

Chris Tapp
 

I've built an image using meta-cedartrail and copied the .hdd image onto a USB drive.

Booting the 'install' label install as expected to an mSATA SSD as sda on an Intel DN2800MT board and this boots as expected.

However, I need to use an eUSB SSD. The installer detects this as 'sdb' and installs ok, but the system fails to boot with a 'kernel panic' reporting that the root FS can't be found. The grub boot specifies:

set root=(hd0,1)

... root=/dev/sdb2

Which looks reasonable. The serial console diagnostics "... here are the available partitions:" entry does not list __any__ partitions. Does this mean that the driver required is currently a module and needs to be configured as a built-in? If so, is there an easy way to work out which one?

Chris Tapp

opensource@keylevel.com
www.keylevel.com


/poky-danny-8.01 task failed: /meta/recipes-devtools/openjade/openjade-native_1.3.2.bb, do_compile

kaiser farrell
 

Hi everyone..

i'm using poky-danny 8.0

I got error openjade/openjade-native_1.3.2.bb, do_compile .. how can i solve it?
http://pastebin.ubuntu.com/1421160/