[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version w

Re: [yocto] [layerindex-web][PATCH 5/7] update: ignore recommends when ordering layers

Hi Paul, I've sent the patches to mailing list: [yocto] [layerindex-web][PATCH 0/4] update.py: several fixes The one for recommends is: update.py: add layers when RECOMMENDS isn't satisfied Now you can drop [PATCH 5/7], others are still needed. // Robert On 07/06/2018 02:49 PM, Robert Yang

[yocto] [layerindex-web][PATCH 2/4] utils.py: fix checkout_repo when no HEAD

Fixed: $ git clone warning: remote HEAD refers to nonexistent ref, unable to checkout. $ git rev-parse HEAD HEAD fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git [...] -- [...]' Catch the error and avo

[yocto] [layerindex-web][PATCH 4/4] update.py: check whether branch existed when nocheckout

Fixed: Assume there is no master branch in hello layer: $ update.py -l hello -b master INFO: Skipping update of layer hello - branch master doesn't exist This is correct since hello layer doesn't have master branch, but when --nocheckout: $ update.py -l hello -b master --nocheckout [snip] INFO:

[yocto] [layerindex-web][PATCH 3/4] update.py: add layers when RECOMMENDS isn't satisfied

When layer_a RECOMMENDS layer_b, try to add layer_b before layer_a, but if layer_b is not found, still add layer_a. And print summary error mesage: $ update.py -b master ERROR: Issues found on branch master: openembedded-core: Added without LAYERRECOMMENDS meta-secure-env: Failed to add

[yocto] [layerindex-web][PATCH 1/4] update_layer.py: avoid calling setup_core_layer_sys_path() when --initial

Fixed: $ update.py -b [snip] NOTE: Starting bitbake server... Traceback (most recent call last): File "update_layer.py", line 471, in main utils.setup_core_layer_sys_path(settings, branch.name) File "/buildarea1/lyang1/layerindex-web/layerindex/utils.py", line 376, in setup_core_layer_sys

[yocto] [layerindex-web][PATCH 0/4] update.py: several fixes

The following changes since commit 5cfdfdca8b9200b5a6e4aa14661b14059a799310: rrs_upstream_history.py: fix set_regexes function (2018-06-06 11:25:46 +1200) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/li_recs http://cgit.openembedded.org/o

Re: [yocto] How to remove openssl from sysroots

On Sun, Jul 8, 2018 at 7:04 PM, Philip Balister wrote: > On 07/06/2018 03:06 PM, Raymond Yeung wrote: >> I've changed the subject heading to make it more specific to our problem. >> Hopefully this generates some responses. >> >> It has been blocking us for close to one week now. We want to use

[linux-yocto] [yocto-4.14][PATCH] cfg: add fragment on kernel selftest

When you want to run cases under tool/testing/selftest of kernel-source, these fragments are required. Signed-off-by: Hongzhi.Song --- cfg/debug-kselftest.cfg | 68 + cfg/debug-kselftest.scc | 4 +++ 2 files changed, 72 insertions(+) create mode

Re: [yocto] Any Linux/Yocto Image Installer (for target system)

This brings up the next logical question - where is the installer? I'd already done a grep and looked into the volume of output. You could ask why don't I read the code. Yes, only if I know what I'm reading is the "correct" file/code. Otherwise, I could be spending a lot of time reading a lo

Re: [yocto] How to remove openssl from sysroots

On 07/06/2018 03:06 PM, Raymond Yeung wrote: > I've changed the subject heading to make it more specific to our problem. > Hopefully this generates some responses. > > > It has been blocking us for close to one week now. We want to use our 3rd > party vendor openssl, not the one that comes wi

Re: [yocto] Yocto Sdk

On Sun, Jul 8, 2018 at 1:56 PM AKASH BHARDWAJ wrote: > > How to add ld-linux.so.2 for Extracting Yocto SDK,as while extracting glibc- > poky-cortexch-rpi-basic-image-toolchain.sh ,it shows that ld-linux.so.2. > While examining the directories,I found out that ld-linux-armeh4.so is > present but

[yocto] Yocto Sdk

How to add ld-linux.so.2 for Extracting Yocto SDK,as while extracting glibc- poky-cortexch-rpi-basic-image-toolchain.sh ,it shows that ld-linux.so.2. While examining the directories,I found out that ld-linux-armeh4.so is present but ld-linux.so.2 is not present,how can I add it?How can I rectify th

Re: [yocto] How to remove openssl from sysroots

We have a shell script that builds openssl. It uses the native makefiles from the open source project. There's no recipe. I suppose we define a recipe for this out-of-tree sources. Still, if we could yank out embedded openssl easily, that would be the best. Raymond _

Re: [yocto] How to remove openssl from sysroots

If the issue is that openssl is 'out of date', then oe-core already provides a 1.1 version that can be selected via PREFERRED_VERSION as well. What is the specific need for the 3rd party version? Alex 2018-07-08 0:41 GMT+02:00 Burton, Ross : > Presumably you've a recipe for the vendor openssl.

Re: [yocto] How to remove openssl from sysroots

I strongly recommend you just write a recipe that builds openssl as you wish, instead of building it out of the build system and somehow getting it into the images. The problem is that how do you intend to build software against openssl if it can't link to the one in oe-core (as you don't want it)