Re: [yocto] [PATCH 00/12] [auh] make it easy to use by recipe maintainer

I had added alexander.kana...@linux.intel.com in the cc list, but it was gone, looks strange, now add him again. // Robert On 12/07/2017 03:37 PM, Robert Yang wrote: * Usages: (No settings is required by default) - Upgrade one recipe: $ upgradehelper.py less - Upgrade multiple

[yocto] [PATCH 11/12] upgradehelper.py: print info when recipe is skipped to upgrade

This makes debug easier. Signed-off-by: Robert Yang --- upgradehelper.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index 3ad33ae..c099445 100755 --- a/upgradehelper.py +++ b/upgradehelper.py @@ -826,11

[yocto] [PATCH 10/12] upgradehelper.py: add --apply-failed option

-f, --apply-failedApply failed patch in the repo after upgrade is done And add "FAILED:" in subject when failed. So that the user can go on working based on the commit. Signed-off-by: Robert Yang --- upgradehelper.py | 12 +++- 1 file changed, 11

[yocto] [PATCH 09/12] upgradehelper.py: use git user in commit when recipes are specified

E.g.,: $ upgradehelper.py less commit d9b551438037e105eebabbbcb2da6d8b8cae7504 Author: Robert Yang Date: Wed Dec 6 16:38:55 2017 +0800 less: upgrade to 529 Signed-off-by: Robert Yang Signed-off-by: Robert Yang

[yocto] [PATCH 08/12] upgradehelper.py: clean repo only once when recipes are specified

E.g.: $ upgradehelper.py less strace bash git The commit is removed when failed, and kept when succeed, but it would be removed when next recipe runs, so only run clean_repo once can keep the commit, which is helpful for the user. Signed-off-by: Robert Yang ---

[yocto] [PATCH 07/12] upgradehelper.py: always do upgrade when recipes are specified

For example, first run: $ upgradehelper.py less -d 5 It did the upgrade Second run: $ upgradehelper.py less -d 5 DEBUG: Skipping upgrade of less: is in history and not 30 days passed Let it always do the upgrade makes it easier to use when do upgrade locally. It will still do the check when the

[yocto] [PATCH 03/12] upgradehelper.py: use UniverseUpdater for all cases

* Use UniverseUpdater() for the following 3 cases: + Upgrade all recipes + Upgrade 1 recipe - '--maintainer' is not a must when any more when use --send-emails, the maintainer be got from distrodata. + Upgrade multiple recipes * Use "args" as the parameter of UniverseUpdater() and

[yocto] [PATCH 05/12] modules/steps.py: fix warn when skip compilation

* The previous code lacks a "% var" in the end: W(" %s: Compilation was skipped by user choice!") * Move the skipping steps to upgradehelper.py rather than modules/steps.py, do not run compile is more straight-forward than return early from it when skipping. Signed-off-by: Robert Yang

[yocto] [PATCH 06/12] upgradehelper.py: only check email settings when -e is specified

Fixed: $ upgradehelper.py less ERROR: smtp host not set! Sending emails disabled! ERROR: 'From' address not set! Sending emails disabled! Only check email settings when "-e" is specified can fix the problem. Signed-off-by: Robert Yang --- upgradehelper.py | 3 ++- 1

[yocto] [PATCH 04/12] modules/steps.py: fix warn when skip compilation

Signed-off-by: Robert Yang --- modules/steps.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/steps.py b/modules/steps.py index 0c527a4..677d101 100644 --- a/modules/steps.py +++ b/modules/steps.py @@ -137,7 +137,7 @@ def

[yocto] [PATCH 02/12] upgradehelper.py: support upgrade multiple recipes

Now we can use: $ upgradehelper.py recipe1 recipe2 Signed-off-by: Robert Yang --- upgradehelper.py | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/upgradehelper.py b/upgradehelper.py index d439a4c..220e459 100755 --- a/upgradehelper.py +++

[yocto] [PATCH 01/12] upgradehelper.py: fix checking for do_checkpkg

The error message in the log is: Initialising tasks...ERROR: Task do_checkpkg does not exist for target strace [snip] So line.find("ERROR: Task do_checkpkg does not exist") == 0 doesn't work, use != -1 to fix the problem. Signed-off-by: Robert Yang ---

[yocto] [PATCH 00/12] [auh] make it easy to use by recipe maintainer

* Usages: (No settings is required by default) - Upgrade one recipe: $ upgradehelper.py less - Upgrade multiple recipes: $ upgradehelper.py less bash The commit will be kept in the repo when *succeed*. No commit when *failed* by default unless -f is used. - Upgrade recipes

Re: [yocto] Build error: "u-boot-imx_2017.03.bb:do_compile" failed ( freescale I.MX 6 on Ubuntu 16.04) ?

I don't know what version of Yocto you're using, but if it's older than 2.3 (which does filter what binaries are seen from the host system with HOSTTOOLS), then your build is probably autodetecting swig from host and you can easily disable that with: do_compile_prepend () { sed 's@\(^always

Re: [yocto] Build error: "u-boot-imx_2017.03.bb:do_compile" failed ( freescale I.MX 6 on Ubuntu 16.04) ?

Hello Jerry, U-Boot depends on Python but the dependency is not included in the U-Boot recipe AFAIK. I have already sent a patchset which was not complete at that time to the yocto mailinglist. Ross meant one needs to inherit from Python U-Boot class in the recipe not just include a

[linux-yocto] [PATCH] common-pc*.scc: Add igb to common-pc drivers

The IGB driver is showing up on some general hardware (like MinnowBoard) which is one of the Yocto Project Reference Platforms. Signed-off-by: Saul Wold --- Bruce, this is for 4.9 and newer. Thanks! bsp/common-pc-64/common-pc-64.scc | 1 + bsp/common-pc/common-pc.scc

Re: [yocto] tiny-linux distribution with raspberrypi error

i tried the following bitbake -c clean rpi-basic-image (to clean the build) added the following to the local IMAGE_FSTYPES_append = " rpi-sdimg" => when i copied the text from the email, it gave class unavailable and then i found that there is a hidden character before the end quotes from

Re: [yocto] tiny-linux distribution with raspberrypi error

I trid the rpi-sdimg as mentioned but i get IMAGE_CMD defined for IMAGE_FSTYOE entry 'rpi-sdimg' possibly invalid type name or missing support class. any idea how to create the rpi image. On Sun, Nov 19, 2017 at 2:59 AM, Khem Raj wrote: > I think you can generate a SD card

[linux-yocto] [kernel-cache][yocto-4.12][V2][PATCH 1/1] features/i915/i915.cfg: compile i915 as a module

Set i915 as a module to trigger the firmware load at the same time the module is loaded. This can avoid a timing problem between the driver starting and it triggering a firmware load, after compile it as module i915 driver will start after the rootfs is ready, then the firmware store in

Re: [linux-yocto] [kernel-cache][yocto-4.12][PATCH] features/i915/i915.cfg: compile i915 as a module

On 12/06/2017 09:03 PM, Bruce Ashfield wrote: > On 12/05/2017 09:10 PM, Liwei Song wrote: >> >> >> On 12/06/2017 06:26 AM, Bruce Ashfield wrote: >>> On 12/04/2017 08:16 PM, Liwei Song wrote: Set i915 as a moudle to trigger the firmware load >>> >>> typo: module >>> at the same time the

[yocto] Q: Kernel SCC files: shouldn't a changed patch trigger a rebuild?

Hello list, i have written a kernel recipe derived from linux-yocto-custom. The SRC_URI includes a SCC file that in turn includes a kernel patch. First of all, this works as expected, the patch is applied to the kernel source and my custom kernel is built. But the kernel is NOT rebuilt if i

[yocto] [poky-tiny] [meta-raspberry] Create rpi-img from generated cpio archive

hi yocto community, i have been testing the poky-tiny with meta-raspberry pi, i successfully compiled the kernel and all the underlying components, but the output is a cpio archive. However, the rpi-image has 2 partitions, a windows and linux partition. I am now stopping at this point, where i

Re: [yocto] externalsrc + sstate why is not compatible?

On Wed, Dec 06, 2017 at 10:59:37AM -0600, Koehler, Yannick wrote: > Ok, will try that. If that works, I may see if I can alter the file > fetcher to use symlinks, not sure if sstate subsystem will like that > or not. That was my idea, but I've never tried it. I'm sure the devil is in the

Re: [yocto] externalsrc + sstate why is not compatible?

Ok, will try this... In our case, we are using CMake for most user space app, and when developing purely app related stuff we can use cmake directly thru command-line or eclipse without actually having a need for yocto. Yocto in this context only serve to build the final image artefact. As

Re: [yocto] Allowing a local command to be executed in a recipe.

On 12/06/2017 07:55 PM, Paul Knopf wrote: I have a local utility that is manually installed on our dev/build machines. How do I configure Yocto to let me use this local command? It is located in /usr/local/bin. Lets say the command is "my-command". Write a recipe for the command, and

[yocto] Allowing a local command to be executed in a recipe.

I have a local utility that is manually installed on our dev/build machines. How do I configure Yocto to let me use this local command? It is located in /usr/local/bin. Lets say the command is "my-command". -- ___ yocto mailing list

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:13 PM, Koehler, Yannick wrote: When you say "subdirs", are you referring to submodules or something along those line? We have used attempted to use submodules and it still required 20 + 1 repo and the overhead is similar to yocto + 20 repo but then you have yocto + 20 repos +

[yocto] Build error: "u-boot-imx_2017.03.bb:do_compile" failed ( freescale I.MX 6 on Ubuntu 16.04) ?

I got an error when trying to build for freescale I.MX6 on Ubuntu 16.04.(see below) (I just follow the guide from http://freescale.github.io) Anybody got hints? Thanks! Jerry === | tools/libfdt_wrap.c:147:21:

Re: [yocto] externalsrc + sstate why is not compatible?

Ok, will try that. If that works, I may see if I can alter the file fetcher to use symlinks, not sure if sstate subsystem will like that or not. If we do so, and someone change the file in /src/somedir will yocto redo the fetch/unpack pattern to recopy over the original content by itself? --

Re: [yocto] [PATCH] yocto: matchbox-window-manager-2: Makefile with spaces instead of a tab refuses to compile

This patch was corrupted because you copied/pasted it into Thunderbird instead of using git-send-email, but I applied it by hand. Ross On 19 November 2017 at 19:58, Petr Cvek wrote: > A wrong spacing in Makefile.am generates a Makefile which will refuse > to compile. This

Re: [yocto] externalsrc + sstate why is not compatible?

On Wed, Dec 06, 2017 at 02:13:26PM +, Koehler, Yannick wrote: > In regards to file fetcher, I will go check the code, I thought the > unpack would only occurs for tarball, not subdir. If you have: SRC_URI := "file://some-dir/" and your tree looks somewhat like this: .git

Re: [yocto] externalsrc + sstate why is not compatible?

When you say "subdirs", are you referring to submodules or something along those line? We have used attempted to use submodules and it still required 20 + 1 repo and the overhead is similar to yocto + 20 repo but then you have yocto + 20 repos + 1 main repos, as such, this is not acceptable

Re: [yocto] How to append to image, not machine?

Hi, One solution is to add a custom action with ROOTFS_POSTPROCESS_COMMAND in one of the image, that will change interfaces file (with sed for example, or symlink, etc ...). Best Regards, Vincent 2017-12-06 14:43 GMT+01:00 Marek Słomiany : > Hi, > > I'm building system

Re: [linux-yocto] [kernel-cache][yocto-4.12][PATCH] features/i915/i915.cfg: compile i915 as a module

On 12/05/2017 09:10 PM, Liwei Song wrote: On 12/06/2017 06:26 AM, Bruce Ashfield wrote: On 12/04/2017 08:16 PM, Liwei Song wrote: Set i915 as a moudle to trigger the firmware load typo: module at the same time the module is loaded. This can aviod i915 driver load rootfs's firmware

Re: [yocto] bitbake menuconfig fails

Thanks Zoran What you say makes perfect sense. I also got the feeling that something doesn't match between the new kernel and yocto. Maybe I should also upgrade yocto. Thanks again. On 06/12/17 09:22, Zoran Stojsavljevic wrote: Hello Mircea, From my point of view: /_> /usr/bin/ld: cannot

Re: [yocto] variable override syntax, where is it documented?

On 12/06/2017 10:58 AM, Bernd wrote: I just found out that I can ovverride the line hostname = "${MACHINE}" in base-files simply by assigning a value to hostname_pn-base-files in my configuration file and it will re-assign it with a higher priority than "=". Now I wonder where this kind of

[yocto] variable override syntax, where is it documented?

I just found out that I can ovverride the line hostname = "${MACHINE}" in base-files simply by assigning a value to hostname_pn-base-files in my configuration file and it will re-assign it with a higher priority than "=". Now I wonder where this kind of black magic is documented, I don't seem

Re: [yocto] externalsrc + sstate why is not compatible?

On 12/06/2017 04:15 AM, Koehler, Yannick wrote: In our situation, we have many packages that are in-house, as such we use a local folder for the several in-house modules. To do so, we need to use externalsrc to point to the local code so that the git repo contains both the code + recipe,

[yocto] [meta-security][PATCH 1/1] swtpm/libtpm: update to latest master

This allows dropping some patches for issues that were addressed upstream. It also brings in support for connecting swtpm to qemu without relying on CUSE. Signed-off-by: Patrick Ohly --- meta-tpm/recipes-tpm/libtpm/libtpm_1.0.bb | 4 +-