Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 08.02.2016 14:44, EXT Maciek Borzecki wrote: On pon, 2016-02-08 at 14:20 +0100, Woronicz, Bartosz ( NSN - PL/Wroclaw) wrote: The problem is, it doesn't doit delirebately, when I run bitbake -f -c latest_link myrecipe , it works when the process is in the tasks batch running bitbake

[yocto] wic adds wrong mount lines to my fstab

Hello list, I am using wic to generate partitioned yocto images. After I boot such an Image, I see two added entrys in my /etc/fstab wich are not correct. cat /etc/fstab # # /etc/fstab: static file system information # # /dev/root / auto

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 9 February 2016 at 08:37, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Ok, but I don't want to run it everytime, just after the do_unpack. What I > need to put it in requirements for each recipe ? > Maybe something like > > do_unpack[require] = "latest_link" >

[yocto] systemd and update-rc.d

Hello, I "activated" systemd as described in the development manual . My distro.conf (excerpt): /DISTRO_FEATURES = "systemd php ${DISTRO_FEATURES_DEFAULT} ${DISTRO_FEATURES_LIBC}

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

On 9 February 2016 at 13:51, Woronicz, Bartosz ( NSN - PL/Wroclaw) < bartosz.woron...@nokia.com> wrote: > Here is the whole bbclass > *: * > > DESCRIPTION = "Creates symlink to the latest version workdir of the > package" > > do_latest_link() { > if [ -n "${WORKDIR}" ]; then >

Re: [yocto] Where should I append Yocto bitbake task to create work folder symlink ?

Cheers, mate! That solves my issue (but with small fix). /do_unpack[postfuncs] += "do_latest_link" /instead/ //do_unpack[postfuncs] += "latest_link" Because, without "do_" it says WARNING: Function latest_link doesn't exist /Here is the whole bbclass/: / DESCRIPTION = "Creates symlink to

[yocto] [[PATCH][qa-tools] 03/16] toaster: Add helpers for clone, setup, start and stop.

From: Aníbal Limón README.md: Toaster tests requires bash so add it. TODO is add a sanity module for test this kind of issues like shell compatibility. Signed-off-by: Aníbal Limón --- README.md| 4 tests/toaster/helpers.py

[yocto] [[PATCH][qa-tools] 00/16] Add Toaster test suite support

This set of changes adds toaster test suite to qa-tools repo. Summary, - Add ToasterHelper class for clone/setup/start/stop toaster. - Add Toaster test suite script, mainly work did by QA Rumania team. - Add COPYRIGHT and improve instructions for install/usage. Next steps

[yocto] [[PATCH][qa-tools] 09/16] toaster/__init__.py: Update toaster test to match new ToasterHelper.

Signed-off-by: Aníbal Limón --- tests/toaster/__init__.py | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/tests/toaster/__init__.py b/tests/toaster/__init__.py index 3762094..d3c5fff 100755 --- a/tests/toaster/__init__.py +++

[yocto] [[PATCH][qa-tools] 08/16] toaster/helper.py: Add force mode to stop method.

The stop method have force mode because toaster without production setup have known issues when is on load, the server response 503 service unavailable. This mode iterates over process to found PID's of toaster instance then sends SIGKILL to it. Signed-off-by: Aníbal Limón

[yocto] [[PATCH][qa-tools] 11/16] README.md: Update with information about setup, toaster and maintainence.

Signed-off-by: Aníbal Limón --- README.md | 34 +++--- 1 file changed, 31 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 4efe1a8..a07e27f 100644 --- a/README.md +++ b/README.md @@ -2,18 +2,46 @@ Scripts used by

[yocto] [[PATCH][qa-tools] 04/16] tests/toaster/__init__.py: Add support for clone/setup/start/stop

From: Aníbal Limón The main idea is to have an script for execute tests against toaster so for now the arguments to execute toaster tests are fixed but will be configured with args in the console. Signed-off-by: Aníbal Limón ---

[yocto] [[PATCH][qa-tools] 12/16] toaster/toaster.py: Add missing shebang to call python.

Signed-off-by: Aníbal Limón --- toaster/toaster.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/toaster/toaster.py b/toaster/toaster.py index d3c5fff..9f477cb 100755 --- a/toaster/toaster.py +++ b/toaster/toaster.py @@ -1,3 +1,5 @@ +#!/usr/bin/env python +

[yocto] [[PATCH][qa-tools] 01/16] README.md: Update instructions on how install host deps on debian.

From: Aníbal Limón Signed-off-by: Aníbal Limón --- README.md | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 8d40c47..b5e6c8f 100644 --- a/README.md +++ b/README.md @@ -7,5 +7,9 @@ Scripts used

[yocto] [[PATCH][qa-tools] 02/16] utils/run/toaster.sh: Get rid of toaster shell script.

From: Aníbal Limón A module in python will be created for have toaster helpers with clone, setup, start, stop. Signed-off-by: Aníbal Limón --- utils/run/toaster.sh | 20 1 file changed, 20 deletions(-) delete mode 100755

[yocto] [[PATCH][qa-tools] 05/16] tests/toaster/helpers.py: When execute bash remove interactive mode.

From: Aníbal Limón Bash interactive mode isn't useful so remove it. Signed-off-by: Aníbal Limón --- tests/toaster/helpers.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/toaster/helpers.py

[yocto] [[PATCH][qa-tools] 06/16] tests/toaster/helpers.py: Fix toaster_start deadlocks.

When call toaster_start on failing scenarios (already started) it becomes blocked on process.communicate() function so add my own function for solve this issue. The new function uses a tempfile instead of PIPE for avoid deadlocks. Signed-off-by: Aníbal Limón ---

[yocto] [[PATCH][qa-tools] 07/16] ts/toaster/helpers.py: Add new class ToasterHelper instead functions.

In order to provide a better interface add a ToasterHelper class the functionality is the same so only modified functions to match method definitions. Signed-off-by: Aníbal Limón --- tests/toaster/helpers.py | 62 ++-- 1

[yocto] [[PATCH][qa-tools] 14/16] toaster/toaster.py: Add command line options.

Now toaster script can receive options from command line like the repository/branch and the work directory to use. Signed-off-by: Aníbal Limón --- toaster/toaster.py | 39 ++- 1 file changed, 34 insertions(+), 5 deletions(-)

[yocto] [[PATCH][qa-tools] 13/16] toaster: Add header to specify license to MIT.

Also add the COPYRIGHT.MIT license file. Signed-off-by: Aníbal Limón --- COPYING.MIT| 17 + toaster/helpers.py | 4 toaster/toaster.py | 4 3 files changed, 25 insertions(+) create mode 100644 COPYING.MIT diff --git

[linux-yocto] How to install c libraries on yocto

I'm new in te yocto proyect and i i want to know if you can help me with this problem. I want to compile a C program in my nitrogen6x but i don know how can add the c standard libraries to the image that i'm using, i read about it and find that c libraries for embedded linux systems are eglib but

[yocto] [[PATCH][qa-tools] 15/16] toaster/helpers.py: Fix ToasterHelper setup method git checkout.

When try to checkout from branch to another branch it fails because this operation isn't permited. So first create a branch before checkout. Example: git checkout jethro -b tmp fatal: Cannot update paths and switch to branch 'tmp' at the same time. Did you intend to checkout 'jethro' which can

[yocto] [meta-mingw][PATCH 0/9][master][jethro] Current set of patches that enable mingw support

This is my current set of patches to enable working meta-mingw support. It includes both master and jethro contents. See git://git.yoctoproject.org/poky-contrib mgh/meta-mingw-jethro -- for Jethro specific branch mgh/meta-mingw -- for Master specific branch Mark Hatle (9): nativesdk-gcc: Add

[yocto] [meta-mingw][PATCH 1/9][master][jethro] nativesdk-gcc: Add mingw32 named libraries to files list

Also we skip the staticdev sanity check, as the '.a' file should be packaged as listed. Signed-off-by: Mark Hatle --- recipes-devtools/gcc/gcc_%.bbappend | 6 ++ 1 file changed, 6 insertions(+) create mode 100644 recipes-devtools/gcc/gcc_%.bbappend diff --git

[yocto] [meta-mingw][PATCH 2/9][master][jethro] meta-environment: Update environment files to batch files

Since the environment .sh files can't be used on a normal windows machine, change to providing .bat files instead. The same mechanisms normally used can be used on the Windows command line. i.e. Unix way: $ source environment-setup-armv5te-wrs-linux-gnueabi.sh $ $CC hello.c Win32 way:

[yocto] [meta-mingw][PATCH 5/9][master][jethro] binutils-cross-canadian: Fix LTO failure

GCC was failing with a message similar to: e:/windri~1/lx8.sdk/qemux8~1.800/sysroots/i686-w~1/usr/bin/i586-w~3/../../libexec/i586-wrs-linux/gcc/i586-wrs-linux/5.2.0/real-ld.exe: unrecognized option '-plugin' The issue was that by default plugin support was disabled in binutils. By enabling the

[yocto] [meta-mingw][PATCH 8/9][master] binutils/gdb: Sync with latest oe-core master version

Signed-off-by: Mark Hatle --- recipes-devtools/binutils/binutils-cross-canadian_2.2%.bbappend | 5 + recipes-devtools/binutils/binutils-cross-canadian_2.25%.bbappend | 5 - recipes-devtools/gdb/gdb-cross-canadian_7.%.bbappend | 5 +

[yocto] [meta-mingw][PATCH 7/9][master] *-mingw32.conf: Update the SDKMACHINE to include additional PREFERRED_PROVIDER

nativesdk-${SDK_PREFIX}libc-initial is also needed to override some glibc settings. Signed-off-by: Mark Hatle --- conf/machine-sdk/i686-mingw32.conf | 1 + conf/machine-sdk/x86_64-mingw32.conf | 1 + 2 files changed, 2 insertions(+) diff --git

[yocto] [meta-mingw][PATCH 6/9][master] gettext, gmp: Resync to oe-core versions

Use a wild card for gettext 0.19 version. It's unlikely this setting will change during the gettext 0.19.* lifecycle. Signed-off-by: Mark Hatle --- recipes-core/gettext/gettext_0.19.%.bbappend | 2 ++ recipes-core/gettext/gettext_0.19.4.bbappend | 2 --

[yocto] [meta-mingw][PATCH 4/9][master][jethro] toolchain-scripts-mingw32.bbclass: Update to match YP 2.0 release

The environment script generatation is updated to match YP 2.0 version. In addition, there was an error in the way the EXTRAPATH component was being generated. Signed-off-by: Mark Hatle --- classes/toolchain-scripts-mingw32.bbclass | 24 +++- 1

[yocto] [meta-mingw][PATCH 3/9][master][jethro] toolchain-scripts-mingw32: Use short paths (8.3)

When using standard paths, the user may end up exceeding the path length to some toolchain helper libraries (DLLs) and binaries. By switching to using the "short path", we can avoid this in many more cases. If the user does exceed the path length, their only option will be to move the SDK lower

Re: [linux-yocto] How to install c libraries on yocto

> I'm new in te yocto proyect and i i want to know if you can help me with this > problem. > I want to compile a C program in my nitrogen6x but i don know how can add the > c standard > libraries to the image that i'm using, i read about it and find that c > libraries for embedded linux >

[yocto] Debugging shared libraries

I'm trying to debug some code (mplayer) which uses some shared libraries from ffmpeg. When I use GDB (via gdbserver), I don't get all the debug information I need - note that many of the shared libraries do not have any symbolic debugging info: (gdb) info sharedlibrary FromTo