[yocto] [meta-security][master][warrior][PATCH 0/3] python-scapy:solved the conflict with python3-scapy

2019-06-10 Thread Zang Ruochen
-Remove redundant sed operations.

-Rename conflicting files to resolve conflicts.


Zang Ruochen (3):
  [yocto][meta-security][master][warrior][PATCH 1/3] python-scapy: Remove
redundant sed operations
  [yocto][meta-security][master][warrior][PATCH 2/3] python-scapy: solved
the conflict with python3-scapy
  [yocto][meta-security][master][warrior][PATCH 3/3] python3-scapy: solved
the conflict with python-scapy

 recipes-security/scapy/python-scapy.inc   | 7 ---
 recipes-security/scapy/python-scapy_2.4.2.bb  | 5 +
 recipes-security/scapy/python3-scapy_2.4.2.bb | 4 
 3 files changed, 9 insertions(+), 7 deletions(-)

-- 
2.20.1



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


[yocto] [meta-security][master][warrior][PATCH 3/3] python3-scapy: solved the conflict with python-scapy

2019-06-10 Thread Zang Ruochen
-Rename the following file to resolve the conflict with python-scapy:
Rename /usr/bin/UTscapy to /usr/bin/UTscapy3
Rename /usr/bin/scapy to /usr/bin/scapy3

Signed-off-by: Zang Ruochen 
---
 recipes-security/scapy/python3-scapy_2.4.2.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
b/recipes-security/scapy/python3-scapy_2.4.2.bb
index 83c79f4..abcaeeb 100644
--- a/recipes-security/scapy/python3-scapy_2.4.2.bb
+++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
@@ -3,3 +3,7 @@ require python-scapy.inc
 
 SRC_URI += "file://run-ptest"
 
+do_install_append() {
+mv ${D}${bindir}/scapy ${D}${bindir}/scapy3
+mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy3
+}
-- 
2.20.1



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


[yocto] [meta-security][master][warrior][PATCH 2/3] python-scapy: solved the conflict with python3-scapy

2019-06-10 Thread Zang Ruochen
-Rename the following file to resolve the conflict with python3-scapy:
Rename /usr/bin/UTscapy to /usr/bin/UTscapy2
Rename /usr/bin/scapy to /usr/bin/scapy2

Signed-off-by: Zang Ruochen 
---
 recipes-security/scapy/python-scapy_2.4.2.bb | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-security/scapy/python-scapy_2.4.2.bb 
b/recipes-security/scapy/python-scapy_2.4.2.bb
index 98db1fd..982620e 100644
--- a/recipes-security/scapy/python-scapy_2.4.2.bb
+++ b/recipes-security/scapy/python-scapy_2.4.2.bb
@@ -4,3 +4,8 @@ require python-scapy.inc
 SRC_URI += "file://run-ptest"
 
 RDEPENDS_${PN} += "${PYTHON_PN}-subprocess"
+
+do_install_append() {
+mv ${D}${bindir}/scapy ${D}${bindir}/scapy2
+mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy2
+}
-- 
2.20.1



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


[yocto] [meta-security][master][warrior][PATCH 1/3] python-scapy: Remove redundant sed operations

2019-06-10 Thread Zang Ruochen
-Remove redundant sed operations.

Signed-off-by: Zang Ruochen 
---
 recipes-security/scapy/python-scapy.inc | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/recipes-security/scapy/python-scapy.inc 
b/recipes-security/scapy/python-scapy.inc
index 99f30a7..baa69b2 100644
--- a/recipes-security/scapy/python-scapy.inc
+++ b/recipes-security/scapy/python-scapy.inc
@@ -12,13 +12,6 @@ SRC_URI = "git://github.com/secdev/scapy.git"
 
 inherit ptest
 
-do_install_append() {
-if [ "${PYTHON_PN}" = "python3" ]; then
-sed -i -e 's/python/python3/' ${D}${bindir}/scapy
-sed -i -e 's/python/python3/' ${D}${bindir}/UTscapy
-fi
-}
-
 do_install_ptest() {
 install -m 0644 ${S}/test/regression.uts ${D}${PTEST_PATH}
 sed -i 's,@PTEST_PATH@,${PTEST_PATH},' ${D}${PTEST_PATH}/run-ptest
-- 
2.20.1



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


Re: [yocto] [meta-security][master][warrior][PATCH 3/3] python3-scapy: solved the conflict with python-scapy

2019-06-10 Thread Adrian Bunk
On Mon, Jun 10, 2019 at 03:24:24PM +0800, Zang Ruochen wrote:
> -Rename the following file to resolve the conflict with python-scapy:
>   Rename /usr/bin/UTscapy to /usr/bin/UTscapy3
>   Rename /usr/bin/scapy to /usr/bin/scapy3
> 
> Signed-off-by: Zang Ruochen 
> ---
>  recipes-security/scapy/python3-scapy_2.4.2.bb | 4 
>  1 file changed, 4 insertions(+)
> 
> diff --git a/recipes-security/scapy/python3-scapy_2.4.2.bb 
> b/recipes-security/scapy/python3-scapy_2.4.2.bb
> index 83c79f4..abcaeeb 100644
> --- a/recipes-security/scapy/python3-scapy_2.4.2.bb
> +++ b/recipes-security/scapy/python3-scapy_2.4.2.bb
> @@ -3,3 +3,7 @@ require python-scapy.inc
>  
>  SRC_URI += "file://run-ptest"
>  
> +do_install_append() {
> +mv ${D}${bindir}/scapy ${D}${bindir}/scapy3
> +mv ${D}${bindir}/UTscapy ${D}${bindir}/UTscapy3
> +}

A proper solution would require using alternatives so that installing 
either the python2 or the python3 version would provide the binary.

But given that python2 is reaching end of life I would suggest to just 
rename the python2 binaries and keep the python3 binaries that will stay
long-term at their upstream names.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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


Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

2019-06-10 Thread Burton, Ross
On Sun, 9 Jun 2019 at 23:19, Ulf Samuelsson  wrote:
> When you have the same machine, and the recipes have variants
> which are DISTRO dependent the SSTATE_DIR can be messed up
>
> We never digged deep enough to find the cause,
> but when we separated the SSTATE to only have one DISTRO
> in the same SSTATE, the problem disappeared.

The recipes were actively broken then, because DISTRO is in the hash.
If the DISTRO changes, the hash changes.

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


Re: [yocto] Multiple MACHINEs and DISTROs: When to use own build dir, SSTATE_DIR, DL_DIR ?

2019-06-10 Thread Richard Purdie
On Mon, 2019-06-10 at 00:11 +0200, Ulf Samuelsson wrote:
> Den 2019-05-09 kl. 11:56, skrev Burton, Ross:
> > On Thu, 9 May 2019 at 10:47, Fabian Knapp  > > wrote:
> > 
> > we have multiple MACHINEs and DISTROs and Im wondering for
> > which
> > combinations I have to setup a dedicated build dir, SSTATE_DIR
> > and
> > DL_DIR.
> > 
> > Information in the form of:
> > 
> > Each (change of) MACHINE needs its dedicated SSTATE_DIR and
> > build
> > dir but can share DL_DIR.
> > 
> > 
> > You can always share DL_DIR and SSTATE_DIR.
> > 
> > Ross
> > 
> When you have the same machine, and the recipes have variants
> which are DISTRO dependent the SSTATE_DIR can be messed up
> 
> We never digged deep enough to find the cause,
> but when we separated the SSTATE to only have one DISTRO
> in the same SSTATE, the problem disappeared.

The system is designed to work sharing DISTROs within sstate. If there
is a problem I would very much like to see the issue investigated and
fixed and can help with that.

Any such problems that have been filed in the bugzilla have been
addressed and there haven't really need any for quite a while.

Cheers,

Richard


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


Re: [yocto] [meta-security] AppArmor 2.11 no longer available on Ubuntu archive (sumo branch)

2019-06-10 Thread akuster808



On 6/7/19 3:09 AM, Burton, Ross wrote:
> That is deliberate and by design, recipes shouldn't fetch from
> Debian/Ubuntu archives for this reason.
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-security/commit/?id=462d76700a3c2748067d4685db8985c511b1b46c
> is a patch to master that needs to be backported to warrior/thud/sumo.

working on propagating this change to the other branches.

- armin
>
> Ross
>
> On Fri, 7 Jun 2019 at 11:07, Smith, Peter1 (GE Renewable Energy)
>  wrote:
>> We are building with meta-security (from sumo branch) which currently uses 
>> v2.11 of AppArmor, it seems overnight that the source archive has been 
>> removed from the Ubuntu archives. Does anyone know if this is a deliberate 
>> action, or if not who to contact to get it put back.
>>
>>
>>
>> Peter Smith
>>
>>
>>
>> Senior Emerging Technologies Engineer
>>
>> Grid Solutions
>>
>> GE Renewable Energy
>>
>>
>>
>> -NON PUBLIC-
>>
>>
>>
>>
>>
>>
>>
>> --
>> ___
>> 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] [meta-security][master][warrior][PATCH 0/3] python-scapy:solved the conflict with python3-scapy

2019-06-10 Thread akuster808



On 6/10/19 12:24 AM, Zang Ruochen wrote:
> -Remove redundant sed operations.
>
> -Rename conflicting files to resolve conflicts.
merged to master.

working on warrior

thanks,
- armin
>
>
> Zang Ruochen (3):
>   [yocto][meta-security][master][warrior][PATCH 1/3] python-scapy: Remove
> redundant sed operations
>   [yocto][meta-security][master][warrior][PATCH 2/3] python-scapy: solved
> the conflict with python3-scapy
>   [yocto][meta-security][master][warrior][PATCH 3/3] python3-scapy: solved
> the conflict with python-scapy
>
>  recipes-security/scapy/python-scapy.inc   | 7 ---
>  recipes-security/scapy/python-scapy_2.4.2.bb  | 5 +
>  recipes-security/scapy/python3-scapy_2.4.2.bb | 4 
>  3 files changed, 9 insertions(+), 7 deletions(-)
>

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


[yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc1)

2019-06-10 Thread Poky Build User


A build flagged for QA (yocto-2.8_M1.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc1


Build hash information: 

bitbake: c4d90890547af642e99cc541af3415df3559563e
meta-gplv2: 168a5070bdf3bc45edb5bf2a1add9b7c081f5b64
meta-intel: c941d896c08d6d83694ba0af1fdf4f4dcb625e9f
meta-mingw: d17724b0eac76792a49e56213cba74e32edba48f
oecore: 86266dfcd70b8e3435d267538c3e6e4d69be829e
poky: 9910a3631ce953b8dd8f3d57d6e122c7fd8cb462



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


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


Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc1)

2019-06-10 Thread richard . purdie
On Mon, 2019-06-10 at 21:38 +, Poky Build User wrote:
> A build flagged for QA (yocto-2.8_M1.rc1) was completed on the
> autobuilder and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc1
> 

I've triggered an rc2 since one of the autobuilder workers messed up
the mips builds.

Cheers,

Richard

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


[yocto] [meta-anaconda][PATCH] .gitignore: add *.pyc and *.pyo

2019-06-10 Thread Chen Qi
The .gitignore needs to contain these two items, otherwise, we get
unstaged lib/oeqa/selftest/cases/__pycache__/ every time we run
oe-selftest.

Signed-off-by: Chen Qi 
---
 .gitignore | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitignore b/.gitignore
index b093583..c01df45 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,5 @@
+*.pyc
+*.pyo
 /*.patch
 *.swp
 *.orig
-- 
2.7.4

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


Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc1)

2019-06-10 Thread Yeoh, Ee Peng
Richard,

Thanks for informing! 

Best regards,
Yeoh Ee Peng 

-Original Message-
From: richard.pur...@linuxfoundation.org 
[mailto:richard.pur...@linuxfoundation.org] 
Sent: Tuesday, June 11, 2019 6:18 AM
To: Poky Build User ; yocto@yoctoproject.org
Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv 
; Yeoh, Ee Peng ; Chan, Aaron 
Chun Yew ; Ang, Chin Huat 
; akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, 
Sangeeta 
Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M1.rc1)

On Mon, 2019-06-10 at 21:38 +, Poky Build User wrote:
> A build flagged for QA (yocto-2.8_M1.rc1) was completed on the 
> autobuilder and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc1
> 

I've triggered an rc2 since one of the autobuilder workers messed up the mips 
builds.

Cheers,

Richard

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


[yocto] [meta-dpdk][PATCH] dpdk: Fix do_compile failure for qemux86 and qemux86-64

2019-06-10 Thread zhe.he
From: He Zhe 

DPDK_TARGET_MACHINE in bbappend in other layers forms the dpdk-internal variable
MACHINE_CFLAGS which is passed to dpdk compilation command line containing the
first -march parameter. And EXTRA_CFLAGS in dpdk.inc is passed to dpdk command
line containing the second -march parameter. By mistake, the first -march had
always overwritten the second one until the following commit of GCC v9.1.0
8c0f695d83d1 ("driver: Also prune joined switches with negation").

Since it was fixed, the second -march, which was core2 for qemux86-64 or
core2-32 for qemux86, began to take effect. But core2* does not have SSE4.2
feature which is required by some dpdk instruction optimization and thus cause
the following compilation failure.

9.1.0/include/smmintrin.h:179:1: error: inlining failed in call to always_inline
'_mm_blendv_epi8': target specific option mismatch
  179 | _mm_blendv_epi8 (__m128i __X, __m128i __Y, __m128i __M)
  | ^~~

This patch adds DPDK_EXTRA_CFLAGS to append appropriate -march, corei7 which is
minimum and clear and independent of host machine, to dpdk compilation command
line to overwrite all previous ones, without having to change dpdk source code.

Note that as we do not want to change the default tune core2* for qemux86*, this
patch just fixes the compilation error. It would probably not be able to run on
qemux86* with corei7 tune.

Signed-off-by: He Zhe 
---
 recipes-extended/dpdk/dpdk.inc | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index a0e081a..0275e0c 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -61,6 +61,9 @@ DPDK_RTE_TARGET_x86-64 = "x86_64-native-linuxapp-gcc"
 DPDK_RTE_TARGET_x86 = "i686-native-linuxapp-gcc"
 DPDK_RTE_TARGET_aarch64 = "arm64-${DPDK_TARGET_MACH}-linuxapp-gcc"
 export RTE_TARGET = "${DPDK_RTE_TARGET}"
+DPDK_EXTRA_CFLAGS = ""
+DPDK_EXTRA_CFLAGS_qemux86 ?= "-march=corei7"
+DPDK_EXTRA_CFLAGS_qemux86-64 ?= "-march=corei7"
 
 # The list of intel Comms platforms and their target machine
 # process mapping. The supported target machine is listed under
@@ -100,18 +103,18 @@ do_compile () {
 
cd ${S}/${RTE_TARGET}
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" \
   prefix=""  LDFLAGS="${TUNE_LDARGS}"  WERROR_FLAGS="-w" V=1
 
cd ${S}/examples/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
 
cd ${S}/test/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/test/$@/"
 }
 
-- 
2.7.4

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


[yocto] [meta-dpdk][PATCH] dpdk: mk: disable warning for packed member pointer

2019-06-10 Thread zhe.he
From: He Zhe 

Backport a patch from upstream to fix the following build failure.

x86_64-native-linuxapp-gcc/include/rte_ether.h:178:2: error:
converting a packed 'const struct ether_addr' pointer (alignment 1) to a 
'unaligned_uint16_t' {aka 'const short
 unsigned int'} pointer (alignment 2) may result in an unaligned pointer value 
[-Werror=address-of-packed-member]
|   178 |  const unaligned_uint16_t *ea_words = (const unaligned_uint16_t *)ea;
|   |  ^

Signed-off-by: He Zhe 
---
 ...disable-warning-for-packed-member-pointer.patch | 48 ++
 recipes-extended/dpdk/dpdk_17.11.3.bb  |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
new file mode 100644
index 000..70a8dec
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
@@ -0,0 +1,48 @@
+From a385972c3675dd2b4792ab5b3cf7a536e6f9846c Mon Sep 17 00:00:00 2001
+From: Reshma Pattan 
+Date: Thu, 2 May 2019 10:33:34 +0100
+Subject: [PATCH] mk: disable warning for packed member pointer
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+gcc 9 on Fedora 30 gives an error
+"taking address of packed member may result in an
+unaligned pointer value" warnings.
+
+For clang builds this warning is already disabled,
+so disable "-Waddress-of-packed-member" for gcc builds
+also.
+
+Snippet of build error:
+lib/librte_eal/linux/eal/eal_memalloc.c: In function ‘alloc_seg_walk’:
+lib/librte_eal/linux/eal/eal_memalloc.c:768:12: error:
+taking address of packed member of ‘struct rte_mem_config’ may result
+in an unaligned pointer value [-Werror=address-of-packed-member]
+  768 |  cur_msl = &mcfg->memsegs[msl_idx];
+  |^~~
+
+Signed-off-by: Reshma Pattan 
+Tested-by: David Marchand 
+Upstream-Status: Backport
+Signed-off-by: He Zhe 
+---
+ mk/toolchain/gcc/rte.vars.mk | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/mk/toolchain/gcc/rte.vars.mk b/mk/toolchain/gcc/rte.vars.mk
+index d8b99fa..b852fcf 100644
+--- a/mk/toolchain/gcc/rte.vars.mk
 b/mk/toolchain/gcc/rte.vars.mk
+@@ -87,5 +87,8 @@ WERROR_FLAGS += -Wimplicit-fallthrough=2
+ WERROR_FLAGS += -Wno-format-truncation
+ endif
+ 
++# disable packed member unalign warnings
++WERROR_FLAGS += -Wno-address-of-packed-member
++
+ export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
+ export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
+-- 
+2.7.4
+
diff --git a/recipes-extended/dpdk/dpdk_17.11.3.bb 
b/recipes-extended/dpdk/dpdk_17.11.3.bb
index 7fc89d2..af42ad8 100644
--- a/recipes-extended/dpdk/dpdk_17.11.3.bb
+++ b/recipes-extended/dpdk/dpdk_17.11.3.bb
@@ -12,4 +12,5 @@ SRC_URI += "\
 file://dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch \
 file://dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch \
 file://dpdk-17.11-Fix-strncpy-error-for-GCC8.patch \
+file://dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch \
 "
-- 
2.7.4

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


[yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

2019-06-10 Thread pokybuild


A build flagged for QA (yocto-2.8_M1.rc2) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2


Build hash information: 

bitbake: c4d90890547af642e99cc541af3415df3559563e
meta-gplv2: 168a5070bdf3bc45edb5bf2a1add9b7c081f5b64
meta-intel: c941d896c08d6d83694ba0af1fdf4f4dcb625e9f
meta-mingw: d17724b0eac76792a49e56213cba74e32edba48f
oecore: 86266dfcd70b8e3435d267538c3e6e4d69be829e
poky: 9910a3631ce953b8dd8f3d57d6e122c7fd8cb462



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


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


Re: [yocto] [meta-dpdk][PATCH] dpdk: mk: disable warning for packed member pointer

2019-06-10 Thread Mittal, Anuj
Thanks, I have included this for 18.11 as well and merged.

Thanks,

Anuj

On Tue, 2019-06-11 at 11:06 +0800, zhe...@windriver.com wrote:
> From: He Zhe 
> 
> Backport a patch from upstream to fix the following build failure.
> 
> x86_64-native-linuxapp-gcc/include/rte_ether.h:178:2: error:
> converting a packed 'const struct ether_addr' pointer (alignment 1)
> to a 'unaligned_uint16_t' {aka 'const short
>  unsigned int'} pointer (alignment 2) may result in an unaligned
> pointer value [-Werror=address-of-packed-member]
> >   178 |  const unaligned_uint16_t *ea_words = (const
> > unaligned_uint16_t *)ea;
> >   |  ^
> 
> Signed-off-by: He Zhe 
> ---
>  ...disable-warning-for-packed-member-pointer.patch | 48
> ++
>  recipes-extended/dpdk/dpdk_17.11.3.bb  |  1 +
>  2 files changed, 49 insertions(+)
>  create mode 100644 recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-
> warning-for-packed-member-pointer.patch
> 
> diff --git a/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-
> warning-for-packed-member-pointer.patch b/recipes-
> extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-
> pointer.patch
> new file mode 100644
> index 000..70a8dec
> --- /dev/null
> +++ b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-
> packed-member-pointer.patch
> @@ -0,0 +1,48 @@
> +From a385972c3675dd2b4792ab5b3cf7a536e6f9846c Mon Sep 17 00:00:00
> 2001
> +From: Reshma Pattan 
> +Date: Thu, 2 May 2019 10:33:34 +0100
> +Subject: [PATCH] mk: disable warning for packed member pointer
> +MIME-Version: 1.0
> +Content-Type: text/plain; charset=UTF-8
> +Content-Transfer-Encoding: 8bit
> +
> +gcc 9 on Fedora 30 gives an error
> +"taking address of packed member may result in an
> +unaligned pointer value" warnings.
> +
> +For clang builds this warning is already disabled,
> +so disable "-Waddress-of-packed-member" for gcc builds
> +also.
> +
> +Snippet of build error:
> +lib/librte_eal/linux/eal/eal_memalloc.c: In function
> ‘alloc_seg_walk’:
> +lib/librte_eal/linux/eal/eal_memalloc.c:768:12: error:
> +taking address of packed member of ‘struct rte_mem_config’ may
> result
> +in an unaligned pointer value [-Werror=address-of-packed-member]
> +  768 |  cur_msl = &mcfg->memsegs[msl_idx];
> +  |^~~
> +
> +Signed-off-by: Reshma Pattan 
> +Tested-by: David Marchand 
> +Upstream-Status: Backport
> +Signed-off-by: He Zhe 
> +---
> + mk/toolchain/gcc/rte.vars.mk | 3 +++
> + 1 file changed, 3 insertions(+)
> +
> +diff --git a/mk/toolchain/gcc/rte.vars.mk
> b/mk/toolchain/gcc/rte.vars.mk
> +index d8b99fa..b852fcf 100644
> +--- a/mk/toolchain/gcc/rte.vars.mk
>  b/mk/toolchain/gcc/rte.vars.mk
> +@@ -87,5 +87,8 @@ WERROR_FLAGS += -Wimplicit-fallthrough=2
> + WERROR_FLAGS += -Wno-format-truncation
> + endif
> + 
> ++# disable packed member unalign warnings
> ++WERROR_FLAGS += -Wno-address-of-packed-member
> ++
> + export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
> + export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
> +-- 
> +2.7.4
> +
> diff --git a/recipes-extended/dpdk/dpdk_17.11.3.bb b/recipes-
> extended/dpdk/dpdk_17.11.3.bb
> index 7fc89d2..af42ad8 100644
> --- a/recipes-extended/dpdk/dpdk_17.11.3.bb
> +++ b/recipes-extended/dpdk/dpdk_17.11.3.bb
> @@ -12,4 +12,5 @@ SRC_URI += "\
>  file://dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch \
>  file://dpdk-17.02-dpdk-fix-installation-warning-and-
> issue.patch \
>  file://dpdk-17.11-Fix-strncpy-error-for-GCC8.patch \
> +file://dpdk-17.11-mk-disable-warning-for-packed-member-
> pointer.patch \
>  "

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


Re: [yocto] [meta-dpdk][PATCH] dpdk: Fix do_compile failure for qemux86 and qemux86-64

2019-06-10 Thread Mittal, Anuj
On Tue, 2019-06-11 at 11:06 +0800, zhe...@windriver.com wrote:
> From: He Zhe 
> 
> DPDK_TARGET_MACHINE in bbappend in other layers forms the dpdk-
> internal variable
> MACHINE_CFLAGS which is passed to dpdk compilation command line
> containing the
> first -march parameter. And EXTRA_CFLAGS in dpdk.inc is passed to
> dpdk command
> line containing the second -march parameter. By mistake, the first
> -march had
> always overwritten the second one until the following commit of GCC
> v9.1.0
> 8c0f695d83d1 ("driver: Also prune joined switches with negation").
> 
> Since it was fixed, the second -march, which was core2 for qemux86-64 
> or
> core2-32 for qemux86, began to take effect. But core2* does not have
> SSE4.2
> feature which is required by some dpdk instruction optimization and
> thus cause
> the following compilation failure.
> 
> 9.1.0/include/smmintrin.h:179:1: error: inlining failed in call to
> always_inline
> '_mm_blendv_epi8': target specific option mismatch
>   179 | _mm_blendv_epi8 (__m128i __X, __m128i __Y, __m128i __M)
>   | ^~~
> 
> This patch adds DPDK_EXTRA_CFLAGS to append appropriate -march,
> corei7 which is
> minimum and clear and independent of host machine, to dpdk
> compilation command
> line to overwrite all previous ones, without having to change dpdk
> source code.
> 
> Note that as we do not want to change the default tune core2* for
> qemux86*, this
> patch just fixes the compilation error. It would probably not be able
> to run on
> qemux86* with corei7 tune.

I don't think overriding arch values in recipe is appropriate. Also the
recipe is setting COMPATIBLE_MACHINE to be null because of this reason.
If the MACHINE that we're building for doesn't support the features
required, then we shouldn't be building dpdk for it in my opinion.

Thanks,

Anuj

> 
> Signed-off-by: He Zhe 
> ---
>  recipes-extended/dpdk/dpdk.inc | 9 ++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-
> extended/dpdk/dpdk.inc
> index a0e081a..0275e0c 100644
> --- a/recipes-extended/dpdk/dpdk.inc
> +++ b/recipes-extended/dpdk/dpdk.inc
> @@ -61,6 +61,9 @@ DPDK_RTE_TARGET_x86-64 = "x86_64-native-linuxapp-
> gcc"
>  DPDK_RTE_TARGET_x86 = "i686-native-linuxapp-gcc"
>  DPDK_RTE_TARGET_aarch64 = "arm64-${DPDK_TARGET_MACH}-linuxapp-gcc"
>  export RTE_TARGET = "${DPDK_RTE_TARGET}"
> +DPDK_EXTRA_CFLAGS = ""
> +DPDK_EXTRA_CFLAGS_qemux86 ?= "-march=corei7"
> +DPDK_EXTRA_CFLAGS_qemux86-64 ?= "-march=corei7"
>  
>  # The list of intel Comms platforms and their target machine
>  # process mapping. The supported target machine is listed under
> @@ -100,18 +103,18 @@ do_compile () {
>  
>   cd ${S}/${RTE_TARGET}
>   oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu" 
> \
> -EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> -I${STAGING_INCDIR}" \
> +EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> ${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
>  CROSS="${TARGET_PREFIX}" \
>  prefix=""  LDFLAGS="${TUNE_LDARGS}"  WERROR_FLAGS="-
> w" V=1
>  
>   cd ${S}/examples/
>   oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu
> -fuse-ld=bfd" \
> -EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> -I${STAGING_INCDIR}" \
> +EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> ${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
>  CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
>  
>   cd ${S}/test/
>   oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu
> -fuse-ld=bfd" \
> -EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> -I${STAGING_INCDIR}" \
> +EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS}
> ${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
>  CROSS="${TARGET_PREFIX}" O="${S}/test/$@/"
>  }
>  

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