date:20170914

Re: [yocto] Best practices when for script recipes.

2017-09-14 Thread Paul D. DeRocco

> From: Einar Vading
> 
> If I have one or a few shell scripts with their own recipe. Do I make
> a git and use the git from the recipe or do I just add the scripts to
> a files directory and install from there?

A recipe should fetch from something other than a files directory
accompanying the recipe if it's large, and you don't want every user of
the layer containing that recipe to have it unless they specifically
include that package. Even then, it only needs to be a git repo if you
want it under version control--FTP is also a valid source.

But in your case, what the recipe needs is tiny, so there's no reason not
to include it with the recipe in a files directory. That's a completely
routine thing to do.

-- 

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

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

[yocto] [meta-raspberry-pi] needing newer or patched version of g++

2017-09-14 Thread Bill Jenkins

After creating an SDK for a 32-bit Raspberry Pi3 target, I ran into the 
following compiler error when
compiling an application using the SDK:

internal compiler error: Max. number of generated reload insns per insn is 
achieved (90)

It turns out that a patch was submitted for g++ early last year for the above 
problem, but apparently that
patch is not in the 6.3.0 version within the SDK. When I try to specify a newer 
version, 
(by using PREFERRED_VERSION_gcc-cross-${TARGET_ARCH}) bitbake reports that only 
5.4.0 or 6.3.0 
are available. Any suggestions on how to resolve this? (i.e. is there some way 
to use a newer g++ or to 
apply the patch?)

Thanks,
Bill
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA cycle report for 2.2.2 rc2

2017-09-14 Thread Cruz, Libertad

Hello All,



Here is the report for the 2.2.2 point release test cycle.

Full Report :  
https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-_Full_Point_Release_Test_Cycle_2.2.2_rc2

=== Summary 

The QA cycle for point release 2.2.2 rc2 is complete.  There are 3 new bugs: 
bug 12080[2]  blocks testing to the eSDK component since eSDK functionalities 
cannot be executed. Bugs 12075[1], 12073[3], 12081[4] don't block full 
functionalities.



LPT results are waiting to be updated by Windriver.


Performance

Compared with 2.2.2 rc1 there was a regression of 14.71 while building rootfs 
on Ubuntu, there was also a regression on Fedora while building sato of 7.46% 
and a regression on kernel of 12.12%.





Ubuntu Test   2.2.2_rc1 2.2.2_rc2 %

  sato   1:00:42  1:01:16   
0.93

  rootfs2:162:36
 14.71

  rmwork 0:59:29  0:59:51   
0.62

  kernel5:015:00
 -0.33

  eSDK  3:223:19
 -1.49





Fedora Test   2.2.2_rc1 2.2.2_rc2 %

  sato   1:01:55  1:06:32   
7.46

  rootfs2:492:51
 1.18

  rmwork 0:59:52  1:01:32   
2.78

  kernel6:036:47
 12.12

  eSDK  3:443:54
 4.46





ptest

There was an improvement on the pass rate in the following packages in 
comparison with 2.2.2 rc1:

gdk-pixbuf with 5%

libxml2 with 4.20%

lttng-tools with 3.20%



On the other side there was a regression on the pass rate in comparison with 
2.2.2 rc1:

acl with 6.80%

e2fsprogs with 100% regression

gawk with .10%

quilt with 1.80%

valgrind of 53.10%





Compliance

Results are yet to be documented by Windriver.



=== QA-Hints



There is only one concern on the eSDK component it cannot execute. QA 
recommends an 2.2.2 rc3 to only verify the eSDK component.



=== Bugs 



   New Bugs

-12075[1]  [morty] testimage quemux86/qemux86-64 lsb tcgetattr: 
Input/output error^M

-12080[2] [Morty][Test Case 1605] 
TCTEMP_2.3_AUTO_sdkext_eSDK_devtool_build_make

-12073[3] selftest: setUpClass failed failing on ubuntu 17.04 
(oeqa.selftest.signing.Signing)

-12081[4] [morty] PTEST: Package Name flex, gzip, slang, do not 
appear in 2.2.2 rc2



Full Bug Report : 
https://wiki.yoctoproject.org/wiki/WW37_-_2017-09-13_-_Full_Point_Release_Test_Cycle_2.2.2_rc2#Bugs_Found_during_QA_Test





 Links =



1.https://bugzilla.yoctoproject.org/show_bug.cgi?id=12075 [1]

2.https://bugzilla.yoctoproject.org/show_bug.cgi?id=12080 [2]

3.https://bugzilla.yoctoproject.org/show_bug.cgi?id=12073 [3]

4.https://bugzilla.yoctoproject.org/show_bug.cgi?id=12081 [4]







Regards

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

Re: [yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed

2017-09-14 Thread Khem Raj

On Thu, Sep 14, 2017 at 10:39 AM yahia farghaly 
wrote:

>
> When i just do this IMAGE_INSTALL_append = " festival" . it promotes me
> with error of
> *do_compile: oe_runmake failed* and* No GNU_HASH in the elf binary *
>

This means linker flags set by oe are not passed to link step  so you might
fix this By
Fixing the linker rules in makefiles

Secondly it might be ignoring the environment flags completely in this case
again you can fix this in makefiles by removing hard assignments and using
+= or weaker fallbacks using ?=

>
> here is the log:
>
>>
>> *Build Configuration:*
>> *BB_VERSION= "1.34.0"*
>> *BUILD_SYS = "x86_64-linux"*
>> *NATIVELSBSTRING   = "universal"*
>> *TARGET_SYS= "arm-poky-linux-gnueabi"*
>> *MACHINE   = "raspberrypi3"*
>> *DISTRO= "poky"*
>> *DISTRO_VERSION= "2.3.2"*
>> *TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4
>> callconvention-hard cortexa7"*
>> *TARGET_FPU= "hard"*
>> *meta  *
>> *meta-poky *
>> *meta-yocto-bsp= "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"*
>> *meta-oe   *
>> *meta-python   *
>> *meta-multimedia   *
>> *meta-networking   = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"*
>> *meta-raspberrypi  = "pyro:c981f01a2cdb3299eb57920cffbb5dfd4248209a"*
>> *meta-ros  = 
>> "master:3ff83184bd16a9ef13660dd5df08687a6c17a458"**meta-mylayer
>>  = "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"*
>>
>
>> *Initialising tasks: 100%
>> ||
>> Time: 0:00:05*
>
>
>> *NOTE: Executing SetScene Tasks*
>> *NOTE: Executing RunQueue Tasks*
>> *ERROR: festival-2.3-r0 do_compile: oe_runmake failed*
>
>
>> *ERROR: festival-2.3-r0 do_compile: Function failed: do_compile (log file
>> is located at
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086)*
>> *ERROR: Logfile of failure stored in:
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086*
>
>
>> *Log data follows:*
>> *| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32',
>> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
>> *| DEBUG: Executing shell function do_compile*
>> *| NOTE: make*
>> *| ERROR: oe_runmake failed*
>> *| config/config:43:
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/config:
>> No such file or directory*
>> *| config/common_make_rules:67:
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/common_make_rules.mak:
>> No such file or directory*
>> *| Makefile:84:
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/top_level.mak:
>> No such file or directory*
>> *| Makefile:85:
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak:
>> No such file or directory*
>> *| make: *** No rule to make target
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak'.
>> Stop.*
>
>
>> *| ERROR: Function failed: do_compile (log file is located at
>> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086)*
>
>
>> *ERROR: Task
>> (/yocto/poky/meta-ros/recipes-extended/festival/festival_2.3.bb:do_compile)
>> failed with exit code '1'*
>
>
>> *ERROR: speech-tools-2.3-r0 do_package_qa: QA Issue: No GNU_HASH in the
>> elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/pda'*
>> *No GNU_HASH in the elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/design_filter'*
>> *No GNU_HASH in the elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/sigfilter'*
>> *No GNU_HASH in the elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ols_test'*
>> *No GNU_HASH in the elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ch_utt'*
>> *No GNU_HASH in the elf binary:
>> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/sig2fv'*
>> *No GNU_HASH in the elf binary:
>>

[yocto] [meta-selinux] Update announcement

2017-09-14 Thread Mark Hatle

I have pushed an update to meta-selinux to work with master.  A few key changes:

The oe-selinux and poky-selinux distro configurations HAVE BEEN REMOVED!  It is
now up to the user to enable the components using the appropriate
DISTRO_FEATURES as documented in the README file.  (acl xattr pam selinux)

The layer now requires meta-selinux as part of the 'setools' upgrade.  The tool
is now a python based tool.

SELinux componetns have been updated to version 2.7.

Refpolicy is at 2.20170204, git at master as of yesterday.

The README for the layer has been updated to include some additional information
about running the included images.

Changelog:

f1f0860 openssh: set ChallengeResponseAuthentication to no
24cce7b refpolicy: fix a typo in RDEPENDS
827b305 initscripts: use the 'i' option for restorecon command
eeb2c2f audit: fix the wrong packaging for auditd.service
2aadc0d audit 2.7.1 -> 2.7.6
beaaa37 attr: fix ptest failures when selinux enabled
232bfeb systemd: Remove inherit enable-selinux, obsolete
40a581d selinux: uprev include file to 20170804
3aafa96 libsepol: uprev to 2.7 (20170804)
375dfa6 libselinux: uprev to 2.7 (20170804)
b00974f libsemanage: uprev to 2.7 (20170804)
43adb0c checkpolicy: uprev to 2.7 (20170804)
f838032 secilc: uprev to 2.7 (20170804)
c9186be policycoreutils: uprev to 2.7 (20170804)
9b70823 sepolgen: remove package
d8d6ac6 mcstrans: add package 2.7 (20170804)
9a07ac8 restorecond: add package 2.7 (20170804)
a5b5f5b selinux-sandbox: add package 2.7 (20170804)
1d3df56 selinux-python: add package 2.7 (20170804)
17cda5a semodule-utils: add package 2.7 (20170804)
28b961c selinux-dbus: add package 2.7 (20170804)
a1f9832 selinux-gui: add package 2.7 (20170804)
493b567 policycoreutils: fixes for 2.7 uprev
fe8bc07 refpolicy_common: depends on semodule-utils-native
fdf7612 setools: uprev to 4.1.1
96b54b4 packagegroup-*: sync package names
2c7c0e9 selinux-python: add setools to RDEPENDS
8bd72df refpolicy-git: Update to lastest git version
694b8d1 README: Update and remove references to distros, replace w/ 
DISTRO_FEATURES
4fefe83 Refactor to conform to YP Compat requirements
6733785 README: Add information about running the system
dddf265 packagegroups: Fix LIC_FILES_CHKSUM
bca5c61 refpolicy: Add '/bin/bash.bash', an update-alternative to the policy
907e373 policycoreutils: Update fixfile
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] u-boot: drop now upstreamed patches

2017-09-14 Thread Andrea Galbusera

oe-core now provides v2017.09 of u-boot which already merged both patches
introduced by commit 94e2929f746f7e49a7870f7ea889dcbed05296c7 so we can
drop them from meta-raspberrypi.

Signed-off-by: Andrea Galbusera 
---
 ...01-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch | 67 
 .../0002-rpi-Enable-USB-keyboard-support.patch | 71 --
 recipes-bsp/u-boot/u-boot_%.bbappend   |  7 ---
 3 files changed, 145 deletions(-)
 delete mode 100644 
recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
 delete mode 100644 
recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch

diff --git 
a/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch 
b/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
deleted file mode 100644
index ffabe89..000
--- 
a/recipes-bsp/u-boot/u-boot/0001-Revert-dm-arm-rpi-Drop-CONFIG_OF_EMBED.patch
+++ /dev/null
@@ -1,67 +0,0 @@
-From 46035d84eb75d54e524d068c29a42c4f562f757a Mon Sep 17 00:00:00 2001
-From: Paul Barker 
-Date: Wed, 2 Aug 2017 11:37:30 +0100
-Subject: [PATCH 1/2] Revert "dm: arm: rpi: Drop CONFIG_OF_EMBED"
-
-This reverts commit 25877d4e4c45451c5398aec3de50e0d5befe0e9f.
-
-Signed-off-by: Paul Barker 
-Upstream-status: Pending

- configs/rpi_2_defconfig | 1 +
- configs/rpi_3_32b_defconfig | 1 +
- configs/rpi_3_defconfig | 1 +
- configs/rpi_defconfig   | 1 +
- 4 files changed, 4 insertions(+)
-
-diff --git a/configs/rpi_2_defconfig b/configs/rpi_2_defconfig
-index 862203f..6aa0532 100644
 a/configs/rpi_2_defconfig
-+++ b/configs/rpi_2_defconfig
-@@ -13,6 +13,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_3_32b_defconfig b/configs/rpi_3_32b_defconfig
-index 95b1677..7396925 100644
 a/configs/rpi_3_32b_defconfig
-+++ b/configs/rpi_3_32b_defconfig
-@@ -14,6 +14,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_3_defconfig b/configs/rpi_3_defconfig
-index f91b53d..1b1ee67 100644
 a/configs/rpi_3_defconfig
-+++ b/configs/rpi_3_defconfig
-@@ -14,6 +14,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
-diff --git a/configs/rpi_defconfig b/configs/rpi_defconfig
-index e2d81ab..c7cf6e0 100644
 a/configs/rpi_defconfig
-+++ b/configs/rpi_defconfig
-@@ -13,6 +13,7 @@ CONFIG_CMD_MMC=y
- CONFIG_CMD_USB=y
- # CONFIG_CMD_FPGA is not set
- CONFIG_CMD_GPIO=y
-+CONFIG_OF_EMBED=y
- CONFIG_DM_MMC=y
- CONFIG_MMC_SDHCI=y
- CONFIG_MMC_SDHCI_BCM2835=y
--- 
-2.7.4
-
diff --git 
a/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch 
b/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch
deleted file mode 100644
index 675d7d9..000
--- a/recipes-bsp/u-boot/u-boot/0002-rpi-Enable-USB-keyboard-support.patch
+++ /dev/null
@@ -1,71 +0,0 @@
-From e4ddccdcf2360c104de502db140a2dbb90b63cfe Mon Sep 17 00:00:00 2001
-From: Simon Glass 
-Date: Thu, 24 Aug 2017 19:45:31 -0600
-Subject: [PATCH 2/2] rpi: Enable USB keyboard support
-
-This is currently disabled, so USB keyboards are not detected in U_Boot.
-Enable this option to fix that.
-
-Backported to v2017.07.
-
-Signed-off-by: Simon Glass 
-Signed-off-by: Paul Barker 
-Upstream-status: Backport

- configs/rpi_2_defconfig | 1 +
- configs/rpi_3_32b_defconfig | 1 +
- configs/rpi_3_defconfig | 1 +
- configs/rpi_defconfig   | 1 +
- 4 files changed, 4 insertions(+)
-
-diff --git a/configs/rpi_2_defconfig b/configs/rpi_2_defconfig
-index 6aa0532..9851836 100644
 a/configs/rpi_2_defconfig
-+++ b/configs/rpi_2_defconfig
-@@ -22,6 +22,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
-diff --git a/configs/rpi_3_32b_defconfig b/configs/rpi_3_32b_defconfig
-index 7396925..c9bdcd7 100644
 a/configs/rpi_3_32b_defconfig
-+++ b/configs/rpi_3_32b_defconfig
-@@ -24,6 +24,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
- CONFIG_SYS_WHITE_ON_BLACK=y
- CONFIG_CONSOLE_SCROLL_LINES=10
-diff --git a/configs/rpi_3_defconfig b/configs/rpi_3_defconfig
-index 1b1ee67..e9c9806 100644
 a/configs/rpi_3_defconfig
-+++ b/configs/rpi_3_defconfig
-@@ -24,6 +24,7 @@ CONFIG_USB=y
- CONFIG_DM_USB=y
- CONFIG_USB_STORAGE=y
- CONFIG_USB_KEYBOARD=y
-+CONFIG_DM_KEYBOARD=y
- CONFIG_DM_VIDEO=y
-

[linux-yocto] [yocto-kernel-cache][PATCH] common-pc-wifi.cfg: Add CONFIG_BRCMFMAC_PCIE

2017-09-14 Thread California Sullivan

This is needed for some Broadcomm wifi drivers.

Signed-off-by: California Sullivan 
---
This is for yocto-4.9 and newer.

 bsp/common-pc/common-pc-wifi.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/common-pc/common-pc-wifi.cfg b/bsp/common-pc/common-pc-wifi.cfg
index 272f912..c2f7d38 100644
--- a/bsp/common-pc/common-pc-wifi.cfg
+++ b/bsp/common-pc/common-pc-wifi.cfg
@@ -20,6 +20,7 @@ CONFIG_BRCMUTIL=m
 CONFIG_BRCMSMAC=m
 CONFIG_BRCMFMAC=m
 CONFIG_BRCMFMAC_USB=y
+CONFIG_BRCMFMAC_PCIE=y
 
 CONFIG_WEXT_CORE=y
 CONFIG_WEXT_PROC=y
-- 
2.9.5

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

[yocto] externalsrc sstate

2017-09-14 Thread Vignesh Rajendran

Dear Yocto,

While using externalsrc for the recipes, sstate is not working for the
recipes.

Is it possible to enable setscene tasks, if srctree_hash_files reports
nothing has changed?

my environment is using makefile based sources in git.

Can you please provide your feedback? Or do i need to consider some other
constraints too?

Regards

Vignesh Rajendran





*“ Learning never exhausts the mind ”   -- Leonardo da
Vinci --*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] OpenEmbedded Developer Meeting Oct 22, 2017 in Prague (before ELCE)

2017-09-14 Thread Ruslan Bilovol

On Thu, Aug 24, 2017 at 9:37 PM, Philip Balister  wrote:
> Once again we will have a developer meeting in Prague the Sunday before
> ELCE.
>
> Please go to https://www.openembedded.org/wiki/OEDEM_2017 and add
> yourself if you are attending and ideas for topics.
>
> Although it is called a developer meeting, we invite members of the
> larger community to attend. The core developers are always interested in
> hearing how OpenEmbedded is used, and what we can do to make it better
> for building the embedded devices of the future.

Is it free to attend, anything else required except of
self-registration on wiki?

Thanks,
Ruslan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux] krogoth support

2017-09-14 Thread Reach, Jonathon A

Hello,

I currently have a krogoth based project that I need to add the meta-selinux 
layer to.

Does anyone know what it would take to accomplish this? Most poky patches fail 
as well as compilation issues with kernel features that postdate krogoth.

Appreciatively,

Jonathon Reach
Cyber Security Product Engineer
Electronics & Safety

[DELPHI_RGB_Mar2013 copy.png]

5825 Delphi Drive
Troy, MI 48098, USA

jonathon.a.re...@delphi.com
+1 586.291.0692


 Note: If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify us immediately by replying to the message 
and deleting it from your computer. Thank you. 

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

[yocto] Best practices when for script recipes.

2017-09-14 Thread Einar Vading

Hi,

I was just wondering if there is some best practice advice on how to
handle adding a single script from a recipe.

If I have one or a few shell scripts with their own recipe. Do I make
a git and use the git from the recipe or do I just add the scripts to
a files directory and install from there?

Are there any pros and cons to either?

Best regards,
Einar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-xilinx] How to include Xilinx DMA driver

2017-09-14 Thread Sandeep Gundlupet Raju

Hi Fan,

Thanks,
Sandeep


-Original Message-
From: meta-xilinx-boun...@yoctoproject.org 
[mailto:meta-xilinx-boun...@yoctoproject.org] On Behalf Of Fan Zhang
Sent: Monday, September 11, 2017 9:38 AM
To: Robert Berger ; yocto@yoctoproject.org; 
meta-xil...@yoctoproject.org
Subject: Re: [meta-xilinx] [yocto] How to include Xilinx DMA driver

Hi all

Thank you Robert for the guide. I tried option [1] out of tree driver. 
Got it compiled, and loaded when image boot up. My understand of the dma driver 
is that Linux DMA engine depends on the Xilinx device driver
(xilinx_cdma.c) and then dma_proxy.c driver depends on the Linux DMA engine. Am 
I correct?
Yes
It does seems Xilinx_cdma is loaded succefully, but dmatest didn't. Here is the 
message I've got:

In order to use DMATEST IP assumes AXI_DMA IP streaming interfaces are 
connected back to back in the HW design. Refer 
http://www.wiki.xilinx.com/DMA+Drivers+-+Soft+IPs 

root@microzed-zynq7:~# dmesg | grep dma
[    0.202348] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[    0.202370] dma-pl330 f8003000.dmac: DBUFF-128x8bytes 
Num_Chans-8 Num_Peri-4 Num_Events-16
[    0.202654] xilinx-vdma 7e20.dma: failed to get axi_clk (4294967294)
[    0.202679] xilinx-vdma: probe of 7e20.dma failed with error -2
[    2.609417] xilinx-cdma 7e20.dma: Xilinx AXI CDMA Engine driver 
Probed!!
[    2.635552] Modules linked in: axidmatest(O+) xilinx_cdma(O)
[    2.659271] PC is at xilinx_axidmatest_probe+0xd8/0x418 [axidmatest]
[    2.916646] [] (xilinx_axidmatest_probe [axidmatest]) from 
[] (platform_drv_probe+0x50/0xb0)
[    3.028812] udevd[674]: worker [687] failed while handling 
'/devices/soc0/dmatest@0'

 From these message, I'm guessing there is an issue in configuration of 
the common clock framework. Is the clkc.c needs to be built as an out of 
tree module to be used in Yocto?

From 2017.1 onwards CCF is mandatory for all Xilinx drivers.
Fan

On 08/09/2017 12:20 PM, Robert Berger wrote:
> Hi,
>
> On 2017-09-08 19:00, Fan Zhang wrote:
>> Hi All,
>>
>> 1. How to include xilinx_dma.c driver in to the poky image build?
>
> In case you want to include out-of tree drivers it could work like 
> this[1] in case you want in-tree it's just a kernel patch similar to[2].
>
> Apparently you will need to turn on kernel config features. You might 
> try something like this[3].
>
> For Yocto/Xilinx specific questions you might want to ask on the 
> Xilinx mailing list[4].
>
> [1] 
> https://github.com/RobertBerger/meta-mainline/tree/pyro-training-v4.9.x/multi-v7-ml/recipes-zedboard/xilinx-dma
>
> [2] 
> https://github.com/RobertBerger/meta-mainline/blob/pyro-training-v4.9.x/multi-v7-ml/recipes-kernel/linux/patch/4.9.x/patches/zedboard-zynq7/zynq-qspi/0001-zynq-zedboard-non-mainline-qspi-support.patch
>
> [3] 
> https://github.com/RobertBerger/meta-mainline/tree/pyro-training-v4.9.x/multi-v7-ml/recipes-kernel/linux/config/multi-v7-ml-base/features/zynq-qspi
>
> [4] https://lists.yoctoproject.org/listinfo/meta-xilinx
>
> Regards,
>
> Robert
>
>

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

[yocto] [pyro][meta-oracle-java][PATCH 2/2] oracle-java: create directory before creating links

2017-09-14 Thread Fabio Berton

From: Jan Remmet 

if bindir directory doesn't exists the link is created wrongly:

file -b 
tmp/work/x86_64-linux/oracle-jse-jdk-x86-64-native/1.8.0-u131r0/image/home/yocto/build/tmp/sysroots/x86_64-linux/usr/bin
symbolic link to
`/home/yocto/build/tmp/sysroots/x86_64-linux/usr/lib/jvm/java-8-oracle/bin/javac'

tested on morty

Signed-off-by: Jan Remmet 
Signed-off-by: Maxin B. John 
(cherry picked from commit 731d3d2cf7e7d65954991e79b9918575e06081c8)
---
 recipes-devtools/oracle-java/oracle-jse-jdk.inc | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc 
b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
index 935ad9b..a7210d9 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk.inc
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
@@ -12,11 +12,14 @@ JDK_JRE = "jdk"
 require oracle-jse.inc
 
 do_install_class-native() {
-   install -d -m 0755  ${D}${libdir_jvm}
+   install -d  ${D}${libdir_jvm}
cp -a ${S}/${JDK_JRE}${PV}_${PV_UPDATE} ${D}${JDK_HOME}
 
+   install -d  ${D}${bindir}
ln -sf ${JDK_HOME}/bin/java ${D}${bindir}
ln -sf ${JDK_HOME}/bin/javac${D}${bindir}
+
+   install -d  ${D}${JDK_HOME}/bin
ln -sf javah${D}${JDK_HOME}/bin/gjavah
ln -sf jar  ${D}${JDK_HOME}/bin/fastjar
 }
-- 
2.14.1

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

[yocto] [pyro][meta-oracle-java][PATCH 1/2] Fix binary paths when setting alternatives

2017-09-14 Thread Fabio Berton

From: Jan Kiszka 

Neither the JDK nor the JRE puts binaries under $JAVA_HOME/jre anymore.
Seen with Java 8, update 131.

Signed-off-by: Jan Kiszka 
Signed-off-by: Maxin B. John 
(cherry picked from commit 0a25dd797e4cac7b727cd38308a46698a95b21b9)
---
 recipes-devtools/oracle-java/oracle-jse-jdk.inc | 12 ++--
 recipes-devtools/oracle-java/oracle-jse.inc |  4 ++--
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/recipes-devtools/oracle-java/oracle-jse-jdk.inc 
b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
index 9fd76e1..935ad9b 100644
--- a/recipes-devtools/oracle-java/oracle-jse-jdk.inc
+++ b/recipes-devtools/oracle-java/oracle-jse-jdk.inc
@@ -28,14 +28,14 @@ PROVIDES += "virtual/javac virtual/java-initial"
 
 pkg_postinst_${PN} () {
update-alternatives --install ${bindir}/jar   jar   ${JDK_HOME}/bin/jar 
100
-   update-alternatives --install ${bindir}/java  java  
${JDK_HOME}/jre/bin/java 100
-   update-alternatives --install ${bindir}/javac javac 
${JDK_HOME}/jre/bin/javac 100
+   update-alternatives --install ${bindir}/java  java  
${JDK_HOME}/bin/java 100
+   update-alternatives --install ${bindir}/javac javac 
${JDK_HOME}/bin/javac 100
update-alternatives --install ${bindir}/javah javah 
${JDK_HOME}/bin/javah 100
 }
 
 pkg_prerm_${PN} () {
-   update-alternatives --remove jar   ${JDK_HOME}/jre/bin/jar
-   update-alternatives --remove java  ${JDK_HOME}/jre/bin/java
-   update-alternatives --remove javac ${JDK_HOME}/jre/bin/javac
-   update-alternatives --remove javah ${JDK_HOME}/jre/bin/javah
+   update-alternatives --remove jar   ${JDK_HOME}/bin/jar
+   update-alternatives --remove java  ${JDK_HOME}/bin/java
+   update-alternatives --remove javac ${JDK_HOME}/bin/javac
+   update-alternatives --remove javah ${JDK_HOME}/bin/javah
 }
diff --git a/recipes-devtools/oracle-java/oracle-jse.inc 
b/recipes-devtools/oracle-java/oracle-jse.inc
index 18ef411..f40ea5c 100644
--- a/recipes-devtools/oracle-java/oracle-jse.inc
+++ b/recipes-devtools/oracle-java/oracle-jse.inc
@@ -41,9 +41,9 @@ PROVIDES += "virtual/java"
 inherit update-alternatives
 
 pkg_postinst_${PN} () {
-   update-alternatives --install ${bindir}/java java 
${JDK_HOME}/jre/bin/java 75
+   update-alternatives --install ${bindir}/java java ${JDK_HOME}/bin/java 
75
 }
 
 pkg_prerm_${PN} () {
-   update-alternatives --remove java ${JDK_HOME}/jre/bin/java
+   update-alternatives --remove java ${JDK_HOME}/bin/java
 }
-- 
2.14.1

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

Re: [yocto] [meta-ros] festival-2.3-r0 do_compile: oe_runmake failed

2017-09-14 Thread yahia farghaly

When i just do this IMAGE_INSTALL_append = " festival" . it promotes me
with error of
*do_compile: oe_runmake failed* and* No GNU_HASH in the elf binary *

here is the log:

>
> *Build Configuration:*
> *BB_VERSION= "1.34.0"*
> *BUILD_SYS = "x86_64-linux"*
> *NATIVELSBSTRING   = "universal"*
> *TARGET_SYS= "arm-poky-linux-gnueabi"*
> *MACHINE   = "raspberrypi3"*
> *DISTRO= "poky"*
> *DISTRO_VERSION= "2.3.2"*
> *TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard
> cortexa7"*
> *TARGET_FPU= "hard"*
> *meta  *
> *meta-poky *
> *meta-yocto-bsp= "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"*
> *meta-oe   *
> *meta-python   *
> *meta-multimedia   *
> *meta-networking   = "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"*
> *meta-raspberrypi  = "pyro:c981f01a2cdb3299eb57920cffbb5dfd4248209a"*
> *meta-ros  = 
> "master:3ff83184bd16a9ef13660dd5df08687a6c17a458"**meta-mylayer
>  = "pyro:ce26a57e04ad65c02087629701d96448a44e73d5"*
>
> *Initialising tasks: 100%
> ||
> Time: 0:00:05*
> *NOTE: Executing SetScene Tasks*
> *NOTE: Executing RunQueue Tasks*
> *ERROR: festival-2.3-r0 do_compile: oe_runmake failed*
> *ERROR: festival-2.3-r0 do_compile: Function failed: do_compile (log file
> is located at
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086)*
> *ERROR: Logfile of failure stored in:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086*
> *Log data follows:*
> *| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32',
> 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']*
> *| DEBUG: Executing shell function do_compile*
> *| NOTE: make*
> *| ERROR: oe_runmake failed*
> *| config/config:43:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/config:
> No such file or directory*
> *| config/common_make_rules:67:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/common_make_rules.mak:
> No such file or directory*
> *| Makefile:84:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/top_level.mak:
> No such file or directory*
> *| Makefile:85:
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak:
> No such file or directory*
> *| make: *** No rule to make target
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/recipe-sysroot/usr/share/speech-tools/config/rules/install.mak'.
> Stop.*
> *| ERROR: Function failed: do_compile (log file is located at
> /yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/festival/2.3-r0/temp/log.do_compile.111086)*
> *ERROR: Task
> (/yocto/poky/meta-ros/recipes-extended/festival/festival_2.3.bb:do_compile)
> failed with exit code '1'*
> *ERROR: speech-tools-2.3-r0 do_package_qa: QA Issue: No GNU_HASH in the
> elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/pda'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/design_filter'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/sigfilter'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ols_test'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ch_utt'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/sig2fv'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/siod'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ngram_test'*
> *No GNU_HASH in the elf binary:
> '/yocto/poky/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/speech-tools/2.3-r0/packages-split/speech-tools/usr/bin/ch_wave'*
> *No GNU_HASH in the elf binary:
>

Re: [linux-yocto] [PATCH] Intel Axxia updates to linux-yocto-4.1

2017-09-14 Thread Bruce Ashfield


On 09/14/2017 11:52 AM, Daniel Dragomir wrote:

Hello Bruce!

Please review and merge this patch in Axxia branches from
linux-yocto-4.1:
- standard/axxia/base
- standard/preempt-rt/axxia/base

Changes included in this series (axxia tag: 1.64):
- Multiple MSI interrupts and MSI-X on 5600 and 6700.



merged

Bruce


Thank you,
Daniel Dragomir

Palani (1):
   drivers/pci: MSI/MSIx support for Axxia (X9, XLF) PCIe host driver

  drivers/pci/host/pcie-axxia.c | 465 ++
  drivers/pci/host/pcie-axxia.h |   5 +-
  2 files changed, 338 insertions(+), 132 deletions(-)



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

Re: [yocto] Perforce fetcher ignores module and label

2017-09-14 Thread Andrew Bradford

Hi Katu,

Sorry for my delay in responding.

On 09/14 11:13, Katu Txakur wrote:
> Have you had time to look at this? I tried to go back to the old perforce
> fetcher but I got a license error and I couldn't work around it.

On the pyro branch of poky, if you revert these two commits, in this
order:

35081f55185a8a9804c21b16cd4600ba70646a10 "bitbake: bitbake-user-manual: Addeds 
support for the Perforce Fetcher"
40f3099e8ec5c6f3a8b7f3d0e90f1c65c388ee77 "base.bbclass: p4 fetcher supports 
srcrev"

And then apply the patch attached, this should bring the pyro branch of
poky back to how the old perforce fetcher worked.  I have tested having
two different depot paths in a recipe SRC_URI and they both are fetched
how I believe you want them to be, next to each other in WORKDIR.

Just be aware, I believe this loses the ability to use
SRC_REV="${AUTOREV}" to automatically find the newest changelist which
my previous changes introduced.

The format for SRC_URI that I tested was like:

SRC_URI = 
"p4://username:password:server.hostname.example.com:1666@depot/path/to/directory/...;cset=178374"

You should also be able to specify P4PORT to set the host and port
number but you may then lose the ability to have the username and
password (although I haven't tested this and don't remember how it used
to work).  You should also be able to specify the P4DATE variable in
your recipe to apply to all p4 fetches instead of using the "cset="
parameter, and instead of using the "cset=" param you should also be
able to specify a "revision=" for a single file or a "label=" for a
label.  I've only tested using the "cset=" way as the others don't
easily apply to how my team internally uses perforce, sorry.

I think I understand how I could make the current perforce fetcher
(without the above reverts or attached patch) do the multi-directory
fetching that you want, but I don't personally want to do that in my
workflow so I'm not going to spend a bunch of time implementing it now.
But if you do implement it, I'd be happy to test patches for you.

Thanks,
Andrew

> 2017-08-31 18:54 GMT+01:00 Andrew Bradford :
> 
> > Hi Katu,
> >
> > On 08/28 17:43, Katu Txakur wrote:
> > > Thanks for looking at this. See my recipe below. I've left the bits
> > related
> > > to systemd service but I don't think they matter for this. I'm using an
> > old
> > > implementation of Perforce (2010) in case this matters. I've tried going
> > > back to the old perforce.py fetcher but I get a license error... do you
> > > know if it would be easy to revert to the old version in my bitbake
> > folder
> > > until we make this work?
> >
> > Sorry, I've been swamped this week and haven't been able to look into
> > this yet.  This coming weekend is a holiday weekend in the USA, too.
> > But I plan to look at this early next week, hope that's OK.
> >
> > We should be able to create a patch series to revert my changes so you
> > can go back to the old perforce fetcher.  It might also be worth
> > investigating how to take the current perforce fetcher and enable some
> > of the use cases that you have (but we can do this after we successfully
> > revert).
> >
> > I'll try to send a patch to you next week for the reverting.
> > Thanks,
> > Andrew
> >
> > > DESCRIPTION = "Dummy recipe to fetch from Perforce"
> > > SECTION = "PerforceRecipes"
> > > LICENSE = "CLOSED"
> > > PR = "r0"
> > >
> > > inherit cmake
> > > DEPENDS = "boost alsa-tools"
> > >
> > > P4USER = "myuser"
> > > P4PASSWD = ""
> > > P4PORT = "192.168.1.55:1666"
> > > FETCHCMD_p4 = "/usr/local/bin/p4"
> > >
> > > SRC_URI = " \
> > > p4://${P4USER}:${P4PASSWD}@myrepo/myfolder/...; \
> > > file://perforce-recipe.service \
> > > "
> > > SRCREV = "${AUTOREV}"
> > > S = "${WORKDIR}/p4"
> > >
> > > do_install_append () {
> > > install -d ${D}${systemd_unitdir}/system
> > > install -m 0644 ../perforce-recipe.service
> > ${D}${systemd_unitdir}/system
> > > }
> > >
> > > NATIVE_SYSTEMD_SUPPORT = "1"
> > > SYSTEMD_PACKAGES = "perforce-recipe"
> > > SYSTEMD_SERVICE_${PN} = "perforce-recipe.service"
> > >
> > > SYSTEMD_AUTO_ENABLE = "disable"
> > >
> > > FILES_${PN} = "${systemd_unitdir} ${bindir}"
> > >
> > >
> > > 2017-08-28 15:27 GMT+01:00 Andrew Bradford  > >:
> > >
> > > > Hi Katu,
> > > >
> > > > On 08/28 08:56, Katu Txakur wrote:
> > > > > 2017-08-11 13:52 GMT+01:00 Andrew Bradford <
> > and...@bradfordembedded.com
> > > > >:
> > > > > On 08/11 11:34, Katu Txakur wrote:
> > > > > > > 2017-08-07 12:17 GMT+01:00 Andrew Bradford <
> > > > and...@bradfordembedded.com
> > > > > > >:
> > > > > > > > On 08/02 10:28, Paul Eggleton wrote:
> > > > > > > > > On Wednesday, 2 August 2017 9:40:10 AM CEST Katu Txakur
> > wrote:
> > > > > > > > > > I'm still having problems fetching from Perforce. Is there
> > any
> > > > > > > > > > documentation based on the latest implementation of the
> > > > > > > > > > poky/bitbake/lib/bb/fetch2/perforce.py file?
> > > > > >

Re: [linux-yocto] [PATCH] ipv6: Fix expected expression before OR operand error

2017-09-14 Thread Bruce Ashfield


I already have a fix staged for this one, the pushed commits
were only for testing purposes.

Cheers,

Bruce

On 09/14/2017 12:14 PM, Daniel Dragomir wrote:

Use parentheses for the entire condition for if statement.
Error introduced by commit
d27e21a ("udp: consistently apply ufo or fragmentation")

| tmp/work-shared/axxiaarm64/kernel-source/net/ipv6/
| ip6_output.c:1343:30: error: expected expression before '||' token
| if (skb && skb_is_gso(skb)) ||

Tested on branches: standard/axxia/base
standard/preempt-rt/axxia/base

Also affected: standard/base
standard/preempt-rt/base
and so on.

Signed-off-by: Daniel Dragomir 
---
  net/ipv6/ip6_output.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
index eb05df0..a6da5fa 100644
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -1340,12 +1340,12 @@ emsgsize:
 */
  
  	cork->length += length;

-   if (skb && skb_is_gso(skb)) ||
+   if ((skb && skb_is_gso(skb)) ||
(((length > mtu) &&
(skb_queue_len(queue) <= 1) &&
(sk->sk_protocol == IPPROTO_UDP) &&
(rt->dst.dev->features & NETIF_F_UFO) &&
-   (sk->sk_type == SOCK_DGRAM) && !udp_get_no_check6_tx(sk))) {
+   (sk->sk_type == SOCK_DGRAM) && !udp_get_no_check6_tx(sk {
err = ip6_ufo_append_data(sk, queue, getfrag, from, length,
  hh_len, fragheaderlen,
  transhdrlen, mtu, flags, rt);



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

[linux-yocto] [PATCH] ipv6: Fix expected expression before OR operand error

2017-09-14 Thread Daniel Dragomir

Use parentheses for the entire condition for if statement.
Error introduced by commit
d27e21a ("udp: consistently apply ufo or fragmentation")

| tmp/work-shared/axxiaarm64/kernel-source/net/ipv6/
| ip6_output.c:1343:30: error: expected expression before '||' token
| if (skb && skb_is_gso(skb)) ||

Tested on branches: standard/axxia/base
standard/preempt-rt/axxia/base

Also affected: standard/base
standard/preempt-rt/base
and so on.

Signed-off-by: Daniel Dragomir 
---
 net/ipv6/ip6_output.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
index eb05df0..a6da5fa 100644
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -1340,12 +1340,12 @@ emsgsize:
 */
 
cork->length += length;
-   if (skb && skb_is_gso(skb)) ||
+   if ((skb && skb_is_gso(skb)) ||
(((length > mtu) &&
(skb_queue_len(queue) <= 1) &&
(sk->sk_protocol == IPPROTO_UDP) &&
(rt->dst.dev->features & NETIF_F_UFO) &&
-   (sk->sk_type == SOCK_DGRAM) && !udp_get_no_check6_tx(sk))) {
+   (sk->sk_type == SOCK_DGRAM) && !udp_get_no_check6_tx(sk {
err = ip6_ufo_append_data(sk, queue, getfrag, from, length,
  hh_len, fragheaderlen,
  transhdrlen, mtu, flags, rt);
-- 
2.7.4

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

[linux-yocto] [PATCH] Intel Axxia updates to linux-yocto-4.1

2017-09-14 Thread Daniel Dragomir

Hello Bruce!

Please review and merge this patch in Axxia branches from
linux-yocto-4.1: 
- standard/axxia/base
- standard/preempt-rt/axxia/base

Changes included in this series (axxia tag: 1.64):
- Multiple MSI interrupts and MSI-X on 5600 and 6700.

Thank you,
Daniel Dragomir

Palani (1):
  drivers/pci: MSI/MSIx support for Axxia (X9, XLF) PCIe host driver

 drivers/pci/host/pcie-axxia.c | 465 ++
 drivers/pci/host/pcie-axxia.h |   5 +-
 2 files changed, 338 insertions(+), 132 deletions(-)

-- 
2.7.4

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

[linux-yocto] [PATCH] drivers/pci: MSI/MSIx support for Axxia (X9, XLF) PCIe host driver

2017-09-14 Thread Daniel Dragomir

From: Palani 

Implemented the MSI domain ops to support Multiple MSI interrupts
in X9 and XLF. Added support for MSI-X interrupts for all the
PEI(0/1/2) host controllers in X9.

Signed-off-by: Palani 
---
 drivers/pci/host/pcie-axxia.c | 465 ++
 drivers/pci/host/pcie-axxia.h |   5 +-
 2 files changed, 338 insertions(+), 132 deletions(-)

diff --git a/drivers/pci/host/pcie-axxia.c b/drivers/pci/host/pcie-axxia.c
index 99c9020..bab3d77 100644
--- a/drivers/pci/host/pcie-axxia.c
+++ b/drivers/pci/host/pcie-axxia.c
@@ -28,9 +28,12 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "pcie-axxia.h"
 
+#define AXXIA_GENERIC_MSI_DOMAIN_IRQ 1
+
 #define PEI_GENERAL_CORE_CTL_REG 0x38
 #define PEI_SII_PWR_MGMT_REG 0xD4
 #define PEI_SII_DBG_0_MON_REG 0xEC
@@ -114,6 +117,9 @@
 #define PCIE_MSIX_INTR0_ENABLE 0xb4
 #define PCIE_MSIX_INTR0_STATUS 0xb0
 
+#define AXI_GPREG_EDG_IRQ_STAT_HI 0x3a0
+#define AXI_GPREG_EDG_IRQ_MASK_HI 0x3a4
+#define MSIX_ASSERTED(0x1 << 8)
 /* SYSCON */
 #define AXXIA_SYSCON_BASE 0x8002C0
 
@@ -468,6 +474,222 @@ static struct pci_ops axxia_pciex_pci_ops = {
.write = axxia_pciex_write_config,
 };
 
+static void axxia_dw_pcie_msi_clear_irq(struct pcie_port *pp, int irq)
+{
+   unsigned int res, bit, val;
+
+   res = (irq / 32) * 12;
+   bit = irq % 32;
+   axxia_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, );
+   val &= ~(1 << bit);
+   axxia_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
+}
+
+static void axxia_dw_pcie_msix_set_irq(struct pcie_port *pp, int irq, int mask)
+{
+   unsigned int res, bit, val;
+
+   res = (irq / 16) * 12;
+   bit = irq % 16;
+   axxia_axi_gpreg_readl(pp, PCIE_MSIX_INTR0_ENABLE + res, );
+   if (mask)
+   val |= 1 << bit;
+   else
+   val &= ~(1 << bit);
+   axxia_axi_gpreg_writel(pp, val, PCIE_MSIX_INTR0_ENABLE + res);
+   bit = irq % 32;
+   axxia_axi_gpreg_readl(pp, PEI_MSIX_INTR_ENABLE + res, );
+   if (mask)
+   val |= 1 << bit;
+   else
+   val &= ~(1 << bit);
+   axxia_axi_gpreg_writel(pp, val, PEI_MSIX_INTR_ENABLE + res);
+}
+
+static void axxia_dw_pcie_msi_set_irq(struct pcie_port *pp, int irq)
+{
+   unsigned int res, bit, val;
+
+   res = (irq / 32) * 12;
+   bit = irq % 32;
+   axxia_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, );
+   val |= 1 << bit;
+   axxia_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
+}
+
+static int axxia_check_set_msi_mode(struct pcie_port *pp, u32 is_msix)
+{
+   u32 val;
+
+   if (pp->msi_mode == AXXIA_MSI_UNCONFIGURED) {
+   if (is_msix) {
+   axxia_axi_gpreg_readl(pp, AXI_GPREG_MSTR, );
+   val &= ~CFG_MSI_MODE;
+   axxia_axi_gpreg_writel(pp, val, AXI_GPREG_MSTR);
+   pp->msi_mode = AXXIA_MSIX_MODE;
+   } else {
+   axxia_axi_gpreg_readl(pp, AXI_GPREG_MSTR, );
+   val |= CFG_MSI_MODE;
+   axxia_axi_gpreg_writel(pp, val, AXI_GPREG_MSTR);
+   pp->msi_mode = AXXIA_MSI_MODE;
+   }
+   } else {
+   if ((is_msix && (pp->msi_mode == AXXIA_MSI_MODE)) ||
+   ((!is_msix) && (pp->msi_mode == AXXIA_MSIX_MODE))) {
+   dev_info(pp->dev,
+   "Axxia already in %s mode, %s not supported\n",
+   pp->msi_mode == AXXIA_MSI_MODE ? "MSI" : "MSIX",
+   pp->msi_mode == AXXIA_MSI_MODE ? "MSIX" : "MSI");
+   return -EINVAL;
+   }
+   }
+   return 0;
+}
+
+
+#ifdef AXXIA_GENERIC_MSI_DOMAIN_IRQ
+static struct irq_chip axxia_msi_top_irq_chip = {
+   .name = "PCI-MSI",
+};
+
+static struct msi_domain_info axxia_msi_domain_info = {
+   .flags  = (MSI_FLAG_USE_DEF_DOM_OPS | MSI_FLAG_USE_DEF_CHIP_OPS |
+  MSI_FLAG_MULTI_PCI_MSI | MSI_FLAG_PCI_MSIX),
+   .chip   = _msi_top_irq_chip,
+};
+
+static void axxia_compose_msi_msg(struct irq_data *data, struct msi_msg *msg)
+{
+   struct pcie_port *pp = irq_data_get_irq_chip_data(data);
+   u64 msi_target = virt_to_phys((void *)pp->msi_data);
+
+   if (pp->msi_mode == AXXIA_MSIX_MODE) {
+   msi_target = msi_target + (data->hwirq * 4);
+   msg->address_lo = (u32)(msi_target & 0x);
+   msg->address_hi = (u32)(msi_target >> 32 & 0x);
+   msg->data = 0x12345678;
+   } else {
+   msg->address_lo = (u32)(msi_target & 0x);
+   msg->address_hi = (u32)(msi_target >> 32 & 0x);
+   msg->data = data->hwirq;
+   }
+
+}
+
+static int

[yocto] Customise file system

2017-09-14 Thread Sabrine Fatnassi

Hello,
My kerlink gateway OS was built using Yocto.
It has a Root Read only file system.

I need to update the opkg configuration files available under "/etc/opkg"
So I created a directory under /user/rootfs_rw/etc named opkg and I created
a new configuration file opkg.conf containing my custom config.

But seems like opkg is not taken into consideration my customized file and
it is always using the configuration file under /etc/opkg

what have I missed?
Thanks!
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

2017-09-14 Thread Mark Hatle

On 9/14/17 5:31 AM, wenzong fan wrote:
> 
> 
> On 09/14/2017 08:07 AM, Mark Hatle wrote:
>> On 9/12/17 9:19 PM, Mark Hatle wrote:
>>> On 9/12/17 9:06 PM, wenzong fan wrote:
 On 09/12/2017 06:59 PM, Chanho Park wrote:
> Hi,
>
> I can't apply this patch on top of the master branch. Which revision did
> you make the patches?

 Oops, that's my fault. I did a "sed -i -e 's/Subject: [/Subject:
 [meta-selinux][/g' 00*" to add prefix for mail subjects, that also
 changed the removed patch files in libsemanage.

 I'll send v2.

 Thanks
 Wenzong
>>>
>>> I don't see the original set of patches in my archives.  When you rebase, 
>>> please
>>> rebase on top of mgh/master-next.
>>
>> My mailer finally loaded the original set.  I saw the same problems, but was
>> able to get them merged.
>>
>> I have updated 'mgh/master-next'.  Please verify the contents include all of
>> your changes.
> 
> All my changes are there now.
> 
>>
>> I tried to build a system and boot it, but it didn't work.  I'm guessing I
>> forgot something simple, but I can't make master-next into master without
>> knowing I can boot..  Any clue would be useful.  Thanks!
>>
>>
>> My configuration is:
>>
>> bblayers.conf:
>>
>> oe-core (master) & meta-selinux (mgh/master-next)
>>
>>
>> local.conf:
>>
>> IMAGE_FEATURES_append = " debug-tweaks ssh-server-openssh"
>>
>> DISTRO_FEATURES_append = " opengl x11 wayland acl xattr pam selinux"
>>
>> PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-mls"
>> PREFERRED_VERSION_refpolicy-mls = "2.20170204"
> 
> Above configs are OK, you can simply use:
> 
> DISTRO = "poky-selinux"
> PREFERRED_VERSION_refpolicy-mls ?= "2.20170204"

The DISTRO settings in meta-selinux are being removed (they are no longer in the
master-next branch).  Instead the user will be required to set the
DISTRO_FEATURE 'selinux' to enable the components.  (It is expected they will
also enable acl/xattr and pam.)

>>
>>
>> I ran QEMU using:
>>
>>
>> runqemu qemux86 core-image-selinux ext4 nographic
>>
>>
> 
> Please run QEMU with:
> 
> $ runqemu qemux86 core-image-selinux ext4 nographic 
> bootparams="selinux=1 enforcing=0"



>>
>> Trying to login I get:
>>
>> qemux86 login: root
>> [   23.960609] kauditd_printk_skb: 13 callbacks suppressed
>> Cannot execute /bin/sh: Permission denied
>> [   23.973922] audit: type=1400 audit(1505347190.805:29): avc:  denied  {
>> execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
>> scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
>> tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0
>> [   23.975463] audit: type=1400 audit(1505347190.813:30): avc:  denied  {
>> execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
>> scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
>> tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0
>>
>>
> 
> This should be blocked by refpolicy-mls, please boot with "selinux=1 
> enforcing=0" to verify if SELinux tools work. For example:

I would like to update the README file for the layer on how the user can
actually make a bootable system.  If this involves adding a user, that is fine.
But at present there is no way to login w/o turning off enforcing.  That seems
to defeat the purpose of enabling selinux in a design.

So any help you can give me for the documentation would be appreciated.

> $ sestatus

root@qemux86:~# sestatus
SELinux status: enabled
SELinuxfs mount:/sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: mls
Current mode:   permissive
Mode from config file:  enforcing
Policy MLS status:  enabled
Policy deny_unknown status: allowed
Memory protection checking: requested (insecure)
Max kernel policy version:  30

> OR:
> $ semanage login -l

root@qemux86:~# semanage login -l

Login Name   SELinux User MLS/MCS RangeService

__default__  user_u   s0-s0*
root root s0-s15:c0.c1023  *

(I followed the information below and enabled the python components.)

> Actually this doesn't work since runtime dependencies, I commented off 
> this from setools_4.1.1.bb:
> 
> # TODO: depends on meta-python, disable the RDEPENDS for now:
> # RDEPENDS_${PN} += "python-networkx python-enum34 python-decorator 
> python-setuptools"
> 
> For community， we need to discuss if we can get meta-selinux depend on 
> meta-python by default? Or just get users to do that?

Yes, we can add a requirement for meta-python.  I just need to clearly document
in the commit message why it is there.

I will work to update the mgh/master-next with the meta-python items and some of
the information above...

--Mark

> Thanks
> Wenzong
> 
>>
>>> --Mark
>>>
>>
>>

-- 
___
yocto mailing list
yocto@yoctoproject.org

Re: [yocto] [meta-raspberrypi] enable serial communication pi 3

2017-09-14 Thread Andrei Gherzan

On Wed, Sep 13, 2017 at 6:58 PM, Ayoub Zaki  wrote:

>
>
> On 13.09.2017 19:55, Khem Raj wrote:
>
>
>
> On Wed, Sep 13, 2017 at 12:27 AM, Ayoub Zaki 
> wrote:
>
>> I ran into the same problem:
>>
>> ENABLE_UART = "1" is not enough you should also add INSTALL_append= "
>> rpi-config" to your local.conf and Serial port will be enabled.
>>
>
> this should be automatically pulled in if you built a sdcard image.
>
> I'm using Wic so it does not work unless I extend the machine config with :
> MACHINE_EXTRA_RRECOMMENDS += " bcm2835-bootfiles rpi-config"
>

That is correct. It is because the sdcard generation class includes this
dependency when building an sdcard.

BTW: bcm2835-bootfiles depends on rpi-config.

About wic, this sounds like an issue anyway. wic uses IMAGE_BOOT_FILES.
This variable includes the blobs provided by bcm28350-bootfiles and, in the
same place, the config gets deployed (due to the dependency above). But in
the wic case nobody triggers the compilation of these packages making wic
to just ignore that specific entry in IMAGE_BOOT_FILES. This sounds like a
bug to me.

If you agree could you create an issue in github and maybe help us fix it
as well? At this point I think bcm2835-bootfiles should be
a MACHINE_ESSENTIAL_EXTRA_RDEPENDS.

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

Re: [yocto] [meta-qt4][PATCH 1/2] qt4-4.8.7.inc: use a supported builtin type for Uchar

2017-09-14 Thread Alexander Kanavin


On 09/14/2017 03:09 PM, Max Krummenacher wrote:

cope with icu 59's changed use of uchar.
http://site.icu-project.org/download/59#TOC-ICU4C-char16_t

4.8.7-r0/recipe-sysroot/usr/include/unicode/umachine.h:347:13: error: 
'char16_t' does not name a type; did you mean 'wchar_t'?
  typedef char16_t UChar;
  ^~~~
  wchar_t
...
4.8.7-r0/recipe-sysroot/usr/include/unicode/uversion.h:167:55: error: 'UChar' 
does not name a type; did you mean 'UChar32'?
  u_versionFromUString(UVersionInfo versionArray, const UChar *versionString);


Thanks; pushed both patches.

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

[yocto] [meta-qt4][PATCH 2/2] qt4: Add patch to allow builds of webkit with gcc v7++

2017-09-14 Thread Max Krummenacher

Change configure logic, so that only gcc 3.3 and older does
not build webkit and gcc 3.2 and older additionally not
build QtXmlPatterns.

Signed-off-by: Max Krummenacher 
---
 recipes-qt4/qt4/qt4-4.8.7.inc   |  2 +-
 .../qt4-4.8.7/{gcc-6.patch => gcc-version.patch}| 21 ++---
 recipes-qt4/qt4/qt4-native.inc  |  2 +-
 3 files changed, 20 insertions(+), 5 deletions(-)
 rename recipes-qt4/qt4/qt4-4.8.7/{gcc-6.patch => gcc-version.patch} (62%)

diff --git a/recipes-qt4/qt4/qt4-4.8.7.inc b/recipes-qt4/qt4/qt4-4.8.7.inc
index 7720463..40558aa 100644
--- a/recipes-qt4/qt4/qt4-4.8.7.inc
+++ b/recipes-qt4/qt4/qt4-4.8.7.inc
@@ -27,7 +27,7 @@ SRC_URI = 
"http://download.qt-project.org/official_releases/qt/4.8/${PV}/qt-ever
file://0034-Fix-kmap2qmap-build-with-clang.patch \
file://0035-Add-nios2-support.patch \
file://0036-qt-everywhere-opensource-src-4.8.7-gcc6.patch \
-   file://gcc-6.patch \
+   file://gcc-version.patch \
file://Fix-QWSLock-invalid-argument-logs.patch \
file://add_check_for_aarch64_32.patch \
file://0001-QWS-fix-24-bit-RGB-BGR-handling.patch \
diff --git a/recipes-qt4/qt4/qt4-4.8.7/gcc-6.patch 
b/recipes-qt4/qt4/qt4-4.8.7/gcc-version.patch
similarity index 62%
rename from recipes-qt4/qt4/qt4-4.8.7/gcc-6.patch
rename to recipes-qt4/qt4/qt4-4.8.7/gcc-version.patch
index b0ce9cd..9c5dd48 100644
--- a/recipes-qt4/qt4/qt4-4.8.7/gcc-6.patch
+++ b/recipes-qt4/qt4/qt4-4.8.7/gcc-version.patch
@@ -6,14 +6,29 @@ RP 2016/5/26
 
 Index: qt-everywhere-opensource-src-4.8.7/configure
 ===
+
+Amend this and change the logic to assume all compilers are suitable
+exept 3.3x resp. 3.2x and older ones.
+Signed-off-by: Max Krummenacher 
+
 --- qt-everywhere-opensource-src-4.8.7.orig/configure
 +++ qt-everywhere-opensource-src-4.8.7/configure
-@@ -7756,7 +7756,7 @@ case "$XPLATFORM" in
+@@ -7757,15 +7757,15 @@
  *-g++*)
# Check gcc's version
case "$(${QMAKE_CONF_COMPILER} -dumpversion)" in
 -  5*|4*|3.4*)
-+  6*|5*|4*|3.4*)
-   ;;
+-  ;;
  3.3*)
  canBuildWebKit="no"
+ ;;
+-  *)
++  3.2*|3.1*|3.0*|2*)
+   canBuildWebKit="no"
+   canBuildQtXmlPatterns="no"
+   ;;
++  *)
++  ;;
+   esac
+   ;;
+ solaris-cc*)
diff --git a/recipes-qt4/qt4/qt4-native.inc b/recipes-qt4/qt4/qt4-native.inc
index c0d6b3c..08aa61d 100644
--- a/recipes-qt4/qt4/qt4-native.inc
+++ b/recipes-qt4/qt4/qt4-native.inc
@@ -18,7 +18,7 @@ SRC_URI = 
"http://download.qt-project.org/official_releases/qt/4.8/${PV}/qt-ever
   file://0015-configure-add-nostrip-for-debug-packages.patch  \

file://0021-configure-make-qt4-native-work-with-long-building-pa.patch \
   file://0036-qt-everywhere-opensource-src-4.8.7-gcc6.patch \
-  file://gcc-6.patch \
+  file://gcc-version.patch \
file://g++.conf \
file://linux.conf \
   file://qt-everywhere-opensource-src-4.8.6-QTBUG-22829.patch \
-- 
2.9.4

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

[yocto] [meta-qt4][PATCH 1/2] qt4-4.8.7.inc: use a supported builtin type for Uchar

2017-09-14 Thread Max Krummenacher

cope with icu 59's changed use of uchar.
http://site.icu-project.org/download/59#TOC-ICU4C-char16_t

4.8.7-r0/recipe-sysroot/usr/include/unicode/umachine.h:347:13: error: 
'char16_t' does not name a type; did you mean 'wchar_t'?
 typedef char16_t UChar;
 ^~~~
 wchar_t
...
4.8.7-r0/recipe-sysroot/usr/include/unicode/uversion.h:167:55: error: 'UChar' 
does not name a type; did you mean 'UChar32'?
 u_versionFromUString(UVersionInfo versionArray, const UChar *versionString);

Signed-off-by: Max Krummenacher 
---
 recipes-qt4/qt4/qt4-4.8.7.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-qt4/qt4/qt4-4.8.7.inc b/recipes-qt4/qt4/qt4-4.8.7.inc
index 4bade85..7720463 100644
--- a/recipes-qt4/qt4/qt4-4.8.7.inc
+++ b/recipes-qt4/qt4/qt4-4.8.7.inc
@@ -46,7 +46,7 @@ UPSTREAM_CHECK_REGEX = "(?P\d+(\.\d+)+)/"
 S = "${WORKDIR}/qt-everywhere-opensource-src-${PV}"
 
 # workaround for class std::auto_ptr' is deprecated with gcc-6
-CXXFLAGS += "-std=gnu++98 -Wno-deprecated"
+CXXFLAGS += "-std=gnu++98 -Wno-deprecated -DUCHAR_TYPE=wchar_t"
 
 # disable webkit for mips64 n32 temporarily that fails to compile,
 # qt upstream defect:
-- 
2.9.4

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

Re: [yocto] [meta-selinux][PATCH 04/21] libsemanage: uprev to 2.7 (20170804)

2017-09-14 Thread wenzong fan




On 09/14/2017 08:07 AM, Mark Hatle wrote:

On 9/12/17 9:19 PM, Mark Hatle wrote:

On 9/12/17 9:06 PM, wenzong fan wrote:

On 09/12/2017 06:59 PM, Chanho Park wrote:

Hi,

I can't apply this patch on top of the master branch. Which revision did
you make the patches?


Oops, that's my fault. I did a "sed -i -e 's/Subject: [/Subject:
[meta-selinux][/g' 00*" to add prefix for mail subjects, that also
changed the removed patch files in libsemanage.

I'll send v2.

Thanks
Wenzong


I don't see the original set of patches in my archives.  When you rebase, please
rebase on top of mgh/master-next.


My mailer finally loaded the original set.  I saw the same problems, but was
able to get them merged.

I have updated 'mgh/master-next'.  Please verify the contents include all of
your changes.


All my changes are there now.



I tried to build a system and boot it, but it didn't work.  I'm guessing I
forgot something simple, but I can't make master-next into master without
knowing I can boot..  Any clue would be useful.  Thanks!


My configuration is:

bblayers.conf:

oe-core (master) & meta-selinux (mgh/master-next)


local.conf:

IMAGE_FEATURES_append = " debug-tweaks ssh-server-openssh"

DISTRO_FEATURES_append = " opengl x11 wayland acl xattr pam selinux"

PREFERRED_PROVIDER_virtual/refpolicy = "refpolicy-mls"
PREFERRED_VERSION_refpolicy-mls = "2.20170204"


Above configs are OK, you can simply use:

DISTRO = "poky-selinux"
PREFERRED_VERSION_refpolicy-mls ?= "2.20170204"




I ran QEMU using:


runqemu qemux86 core-image-selinux ext4 nographic




Please run QEMU with:

$ runqemu qemux86 core-image-selinux ext4 nographic 
bootparams="selinux=1 enforcing=0"




Trying to login I get:

qemux86 login: root
[   23.960609] kauditd_printk_skb: 13 callbacks suppressed
Cannot execute /bin/sh: Permission denied
[   23.973922] audit: type=1400 audit(1505347190.805:29): avc:  denied  {
execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0
[   23.975463] audit: type=1400 audit(1505347190.813:30): avc:  denied  {
execute } for  pid=671 comm="login" name="bash.bash" dev="vda" ino=8163
scontext=system_u:system_r:local_login_t:s0-s15:c0.c1023
tcontext=system_u:object_r:bin_t:s0 tclass=file permissive=0




This should be blocked by refpolicy-mls, please boot with "selinux=1 
enforcing=0" to verify if SELinux tools work. For example:


$ sestatus

OR:
$ semanage login -l
Actually this doesn't work since runtime dependencies, I commented off 
this from setools_4.1.1.bb:


# TODO: depends on meta-python, disable the RDEPENDS for now:
# RDEPENDS_${PN} += "python-networkx python-enum34 python-decorator 
python-setuptools"


For community， we need to discuss if we can get meta-selinux depend on 
meta-python by default? Or just get users to do that?


Thanks
Wenzong




--Mark





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

Re: [yocto] [PATCH] libwww-perl: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Burton, Ross

Can you resend these patches putting the layer name in the subject?

Ross

On 14 September 2017 at 10:09, Huang Qiyu 
wrote:

> Signed-off-by: Huang Qiyu 
> ---
>  meta-cgl-common/recipes-perl/perl/libwww-perl_6.05.bb | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta-cgl-common/recipes-perl/perl/libwww-perl_6.05.bb
> b/meta-cgl-common/recipes-perl/perl/libwww-perl_6.05.bb
> index b365948..4d17b3a 100644
> --- a/meta-cgl-common/recipes-perl/perl/libwww-perl_6.05.bb
> +++ b/meta-cgl-common/recipes-perl/perl/libwww-perl_6.05.bb
> @@ -1,4 +1,5 @@
>  DESCRIPTION = "libwww-perl provides a simple and consistent API to the
> World Wide Web"
> +HOMEPAGE = "http://search.cpan.org/dist/libwww-perl/;
>  SECTION = "libs"
>  LICENSE = "GPLv2"
>  LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=
> 4d92cd373abda3937c2bc47fbc49d690"
> --
> 2.7.4
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Perforce fetcher ignores module and label

2017-09-14 Thread Katu Txakur

Hi Andrew,

Have you had time to look at this? I tried to go back to the old perforce
fetcher but I got a license error and I couldn't work around it.

Regards,
Katu

2017-08-31 18:54 GMT+01:00 Andrew Bradford :

> Hi Katu,
>
> On 08/28 17:43, Katu Txakur wrote:
> > Thanks for looking at this. See my recipe below. I've left the bits
> related
> > to systemd service but I don't think they matter for this. I'm using an
> old
> > implementation of Perforce (2010) in case this matters. I've tried going
> > back to the old perforce.py fetcher but I get a license error... do you
> > know if it would be easy to revert to the old version in my bitbake
> folder
> > until we make this work?
>
> Sorry, I've been swamped this week and haven't been able to look into
> this yet.  This coming weekend is a holiday weekend in the USA, too.
> But I plan to look at this early next week, hope that's OK.
>
> We should be able to create a patch series to revert my changes so you
> can go back to the old perforce fetcher.  It might also be worth
> investigating how to take the current perforce fetcher and enable some
> of the use cases that you have (but we can do this after we successfully
> revert).
>
> I'll try to send a patch to you next week for the reverting.
> Thanks,
> Andrew
>
> > DESCRIPTION = "Dummy recipe to fetch from Perforce"
> > SECTION = "PerforceRecipes"
> > LICENSE = "CLOSED"
> > PR = "r0"
> >
> > inherit cmake
> > DEPENDS = "boost alsa-tools"
> >
> > P4USER = "myuser"
> > P4PASSWD = ""
> > P4PORT = "192.168.1.55:1666"
> > FETCHCMD_p4 = "/usr/local/bin/p4"
> >
> > SRC_URI = " \
> > p4://${P4USER}:${P4PASSWD}@myrepo/myfolder/...; \
> > file://perforce-recipe.service \
> > "
> > SRCREV = "${AUTOREV}"
> > S = "${WORKDIR}/p4"
> >
> > do_install_append () {
> > install -d ${D}${systemd_unitdir}/system
> > install -m 0644 ../perforce-recipe.service
> ${D}${systemd_unitdir}/system
> > }
> >
> > NATIVE_SYSTEMD_SUPPORT = "1"
> > SYSTEMD_PACKAGES = "perforce-recipe"
> > SYSTEMD_SERVICE_${PN} = "perforce-recipe.service"
> >
> > SYSTEMD_AUTO_ENABLE = "disable"
> >
> > FILES_${PN} = "${systemd_unitdir} ${bindir}"
> >
> >
> > 2017-08-28 15:27 GMT+01:00 Andrew Bradford  >:
> >
> > > Hi Katu,
> > >
> > > On 08/28 08:56, Katu Txakur wrote:
> > > > 2017-08-11 13:52 GMT+01:00 Andrew Bradford <
> and...@bradfordembedded.com
> > > >:
> > > > On 08/11 11:34, Katu Txakur wrote:
> > > > > > 2017-08-07 12:17 GMT+01:00 Andrew Bradford <
> > > and...@bradfordembedded.com
> > > > > >:
> > > > > > > On 08/02 10:28, Paul Eggleton wrote:
> > > > > > > > On Wednesday, 2 August 2017 9:40:10 AM CEST Katu Txakur
> wrote:
> > > > > > > > > I'm still having problems fetching from Perforce. Is there
> any
> > > > > > > > > documentation based on the latest implementation of the
> > > > > > > > > poky/bitbake/lib/bb/fetch2/perforce.py file?
> > > > > > >
> > > > > > > There's some documentation now in the official Yocto Project
> > > > > > > documentation location for bitbake fetchers [1].  Prior to my
> > > changes
> > > > > > > there was very little if any documentation, afaik.
> > > > > > >
> > > > > > > [1]: http://www.yoctoproject.org/docs/2.3.1/bitbake-user-
> > > > > > > manual/bitbake-user-manual.html#perforce-fetcher
> > > > > > >
> > > > > > > > > 2017-07-25 10:05 GMT+01:00 Katu Txakur <
> katutxaku...@gmail.com
> > > >:
> > > > > > > > > > I'm upgrading a recipe that fetches the source code from
> > > > > Perforce.
> > > > > > > > > >
> > > > > > > > > > The old recipe was:
> > > > > > > > > >
> > > > > > > > > > SRC_URI = " \
> > > > > > > > > >   p4://${P4USER}:${P4PASSWD}:${P4HOST}:${P4PORT}@Depot
> /path/
> > > pe
> > > > > > > > > > rforce/...;module=local/path/relativeto/p4;label=${
> > > P4CHANGELIST}
> > > > > \
> > > > > > > > > >   "
> > > > > > > > > >
> > > > > > > > > > With the new version of /lib/bb/fetch2/perforce.py, I
> had to
> > > set
> > > > > > > P4PORT
> > > > > > > > > > outside SRC_URI, leaving the recipe with:
> > > > > > > > > >
> > > > > > > > > > SRC_URI = " \
> > > > > > > > > >   p4://${P4USER}:${P4PASSWD}@Depot/path/perforce/...;
> module=
> > > > > > > > > > local/path/relativeto/p4;label=${P4CHANGELIST} \
> > > > > > > > > >   "
> > > > > > > > > >
> > > > > > > > > > The Perforce fetcher kind of works, but it seems to be
> > > ignoring
> > > > > the
> > > > > > > > > > "module" and the "label" attributes. After reading the
> Python
> > > > > script
> > > > > > > I can
> > > > > > > > > > see that after the "@", only the substring before the
> first
> > > ";"
> > > > > is
> > > > > > > used.
> > > > > > >
> > > > > > > Sorry for not making the label change more clear, but you
> should be
> > > > > able
> > > > > > > to simply set SRCREV="labelname" and have the functionality you
> > > desire.
> > > > > > > However, we don't use labels very often internally, so the use
> of
> > > > > labels
> > > > > > > in SRCREV isn't tested that often

[yocto] [PATCH] qtxmlpatterns: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qtxmlpatterns_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtxmlpatterns_git.bb 
b/recipes-qt/qt5/qtxmlpatterns_git.bb
index 7c18079..f4f46f1 100644
--- a/recipes-qt/qt5/qtxmlpatterns_git.bb
+++ b/recipes-qt/qt5/qtxmlpatterns_git.bb
@@ -2,6 +2,7 @@ require qt5.inc
 require qt5-git.inc
 require qt5-ptest.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPL3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
-- 
2.7.4



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

[yocto] [PATCH] qtquick1: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qtquick1_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtquick1_git.bb b/recipes-qt/qt5/qtquick1_git.bb
index eaa3661..c1bbc8a 100644
--- a/recipes-qt/qt5/qtquick1_git.bb
+++ b/recipes-qt/qt5/qtquick1_git.bb
@@ -2,6 +2,7 @@ require qt5.inc
 require qt5-git.inc
 require qt5-ptest.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPLv21;md5=4bfd28363f541b10d9f024181b8df516 \
-- 
2.7.4



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

[yocto] [PATCH] qttools: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qttools_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qttools_git.bb b/recipes-qt/qt5/qttools_git.bb
index 32d65d6..151b4df 100644
--- a/recipes-qt/qt5/qttools_git.bb
+++ b/recipes-qt/qt5/qttools_git.bb
@@ -1,6 +1,7 @@
 require qt5.inc
 require qt5-git.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPL3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
-- 
2.7.4



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

[yocto] [PATCH] qtscript: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qtscript_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtscript_git.bb b/recipes-qt/qt5/qtscript_git.bb
index 9061c3c..9fe2358 100644
--- a/recipes-qt/qt5/qtscript_git.bb
+++ b/recipes-qt/qt5/qtscript_git.bb
@@ -1,6 +1,7 @@
 require qt5.inc
 require qt5-git.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPLv21;md5=4bfd28363f541b10d9f024181b8df516 \
-- 
2.7.4



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

[yocto] [PATCH] qtsvg: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qtsvg_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtsvg_git.bb b/recipes-qt/qt5/qtsvg_git.bb
index 40854e0..e3bd840 100644
--- a/recipes-qt/qt5/qtsvg_git.bb
+++ b/recipes-qt/qt5/qtsvg_git.bb
@@ -1,6 +1,7 @@
 require qt5.inc
 require qt5-git.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPLv21;md5=4bfd28363f541b10d9f024181b8df516 \
-- 
2.7.4



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

[yocto] [PATCH] qtdeclarative: Add HOMEPAGE info into recipe file.

2017-09-14 Thread Huang Qiyu

Signed-off-by: Huang Qiyu 
---
 recipes-qt/qt5/qtdeclarative_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-qt/qt5/qtdeclarative_git.bb 
b/recipes-qt/qt5/qtdeclarative_git.bb
index 12e5f4e..2cc969a 100644
--- a/recipes-qt/qt5/qtdeclarative_git.bb
+++ b/recipes-qt/qt5/qtdeclarative_git.bb
@@ -2,6 +2,7 @@ require qt5.inc
 require qt5-git.inc
 require qt5-ptest.inc
 
+HOMEPAGE = "http://www.qt.io;
 LICENSE = "GFDL-1.3 & BSD & ( GPL-3.0 & The-Qt-Company-GPL-Exception-1.0 | 
The-Qt-Company-Commercial ) & ( GPL-2.0+ | LGPL-3.0 | The-Qt-Company-Commercial 
)"
 LIC_FILES_CHKSUM = " \
 file://LICENSE.LGPL3;md5=e6a600fd5e1d9cbde2d983680233ad02 \
-- 
2.7.4



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

Re: [yocto] DEBUG: automake-native: class native found in blacklist, disable icecc ?

2017-09-14 Thread Yusuke Mitsuki

Hi Riko

It seems you use,
poky: pyro
meta-openembedded:master

I think that you should checkout meta-openembedded to pyro branch.

You can get by command like a follows,

$ cd meta-openembedded
$ git checkout -b pyro origin/pyro

Otherwise, checkout poky to master...

I hope your helps.

2017/08/03 0:05 "Riko Ho" :

> Still got the same error after installing it? Any other clues?
> On Aug 2, 2017 9:53 PM, "Khem Raj"  wrote:
>
>> On Tue, Aug 1, 2017 at 11:42 PM, Riko Ho  wrote:
>> > Could it be this one ?
>> >
>> > https://www.devmanuals.net/install/ubuntu/ubuntu-12-04-lts-
>> precise-pangolin/install-libthread-queue-perl.html
>> >
>>
>> yes
>>
>> > Thanks
>> >
>> >
>> > On 02/08/17 14:38, Khem Raj wrote:
>> >
>> > apply the solutions they may work for ubuntu
>> >
>> > On Tue, Aug 1, 2017 at 11:33 PM, Riko Ho 
>> wrote:
>> >
>> > Dear Yocto Team Member,
>> >
>> > I'm building with Ubuntu 16
>> >
>> >
>> > On 02/08/17 14:31, Khem Raj wrote:
>> >
>> > On Tue, Aug 1, 2017 at 11:18 PM, Riko Ho 
>> wrote:
>> >
>> > Dear Yocto Team Member,
>> >
>> > That's the branch :
>> >
>> > ==
>> >
>> > meta-poky
>> > meta-yocto-bsp= "pyro:e5aa1ac23669a45491de9ecffac491c01e70203f"
>> > openembedded-core = "master:2fd0757ae7fd63bc93a4ce8579c6ba0cdbb4c1cd"
>> > meta-openembedded
>> > meta-oe
>> > meta-xfce
>> > meta-gnome
>> > meta-python
>> > meta-multimedia
>> > meta-networking   = "master:b063789560bfb9c60a7a15277b5b3a9839b5ba74"
>> > meta-browser  =
>> > "firefox-52.1.2esr-2:c79cf6c7811afd2cd167e8967e3c29b1e797371e"
>> > meta-ti   = "master:872d418f6e503dea66e3533f43e7a17618183982"
>> >
>> > Initialising tasks: 100%
>> > |###
>> #|
>> > Time: 0:00:08
>> > NOTE: Executing SetScene Tasks
>> > NOTE: Executing RunQueue Tasks
>> > ERROR: automake-native-1.15-r0 do_compile: oe_runmake failed
>> > ERROR: automake-native-1.15-r0 do_compile: Function failed: do_compile
>> (log
>> > file is located at
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291)
>> > ERROR: Logfile of failure stored in:
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291
>> > Log data follows:
>> > | DEBUG: Executing shell function do_compile
>> > | NOTE: Using icecc
>> > | NOTE: make -j 10
>> > | ERROR: oe_runmake failed
>> > | : && /home/bianchi77/poky/build/tmp/hosttools/mkdir -p doc && {
>> > PATH='/home/bianchi77/poky/build/tmp/work/x86_64-linux/autom
>> ake-native/1.15-r0/build/t/wrap:'$PATH
>> > && export PATH; } && /usr/bin/env perl ../automake-1.15/doc/help2man
>> > --output=doc/automake-1.15.1 automake-1.15
>> > | help2man: can't get `--help' info from automake-1.15
>> >
>> > What OS do you run on build machine ?
>> > if its archlinux then apply this patch to automake
>> >
>> > https://gist.github.com/xywei/03b546054f0d2e2f76c5ac530c88268a
>> >
>> > otherwise if its centos7 then install
>> >
>> > yum install perl-Thread-Queue
>> >
>> >
>> >
>> > | Try `--no-discard-stderr' if option outputs to stderr
>> > | Makefile:3687: recipe for target 'doc/automake-1.15.1' failed
>> > | make: *** [doc/automake-1.15.1] Error 255
>> > | ERROR: Function failed: do_compile (log file is located at
>> > /home/bianchi77/poky/build/tmp/work/x86_64-linux/automake-
>> native/1.15-r0/temp/log.do_compile.9291)
>> > ERROR: Task
>> > (virtual:native:/home/bianchi77/poky/meta/recipes-devtools/
>> automake/automake_1.15.bb:do_compile)
>> > failed with exit code '1'
>> > NOTE: Tasks Summary: Attempted 845 tasks of which 844 didn't need to be
>> > rerun and 1 failed.
>> >
>> > Summary: 1 task failed:
>> >
>> > virtual:native:/home/bianchi77/poky/meta/recipes-devtools/
>> automake/automake_1.15.bb:do_compile
>> > Summary: There were 4 WARNING messages shown.
>> > Summary: There were 2 ERROR messages shown, returning a non-zero exit
>> code.
>> > bianchi77@bianchi77-HP-Pavilion-dv6-Notebook-PC:~/poky/build$
>> >
>> > How can I fix that automake error ?
>> >
>> > I tried to run bitbake core-image-minimal for it.
>> > Thanks,
>> >
>> > On 31/07/17 21:26, Burton, Ross wrote:
>> >
>> > Then the branch you checked out.  git branch will tell you.
>> >
>> > Ross
>> >
>> > On 31 July 2017 at 14:17, Riko Ho  wrote:
>> >
>> > Git clone ...
>> >
>> > On Jul 31, 2017 9:16 PM, "Burton, Ross"  wrote:
>> >
>> > How did you get poky?
>> >
>> > Ross
>> >
>> > On 31 July 2017 at 14:14, Riko Ho  wrote:
>> >
>> > How can I see my branch?
>> >
>> > On Jul 31, 2017 9:12 PM, "Burton, Ross"  wrote:
>> >
>> > On 31 July 2017 at 03:33, Riko Ho  wrote:
>> >
>> > Is my auto make disabled with icecc ?
>> >
>> > How to

Re: [yocto] DEBUG: automake-native: class native found in blacklist, disable icecc ?

2017-09-14 Thread Yasushi SHOJI

Hi,

On Thu, Aug 3, 2017 at 12:01 AM, Riko Ho  wrote:
> Still got the same error after installing it? Any other clues?

Did you try the patch posted by Khem Raj?

https://gist.github.com/xywei/03b546054f0d2e2f76c5ac530c88268a

I had the same problem on my Debian Unstable but the patch worked for me.

I wonder why it's not merged yet, though.
-- 
   yashi
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

38 matches

Mail list logo