date:20170530

[yocto] [meta-cgl][PATCH 3/3] cluster-glue: update useradd parameters

2017-05-30 Thread jackie.huang

From: Jackie Huang 

Update useradd parameters for cluster-glue according
to spec file from source code:

https://github.com/ClusterLabs/cluster-glue/blob/master/cluster-glue-fedora.spec

And use HA_USER and HA_GROUP for easy maintenance.

Signed-off-by: Kai Kang 
Signed-off-by: Jackie Huang 
---
 .../recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb| 14 +++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb 
b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
index b5cf997..783469d 100644
--- a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
@@ -27,18 +27,26 @@ inherit autotools useradd pkgconfig systemd
 SYSTEMD_SERVICE_${PN} = "logd.service"
 SYSTEMD_AUTO_ENABLE = "disable"
 
+HA_USER = "hacluster"
+HA_GROUP = "haclient"
+
 S = "${WORKDIR}/Reusable-Cluster-Components-glue--glue-${PV}"
 
 PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
 PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir},--without-systemdsystemunitdir,systemd"
 
-EXTRA_OECONF = "--with-daemon-user=hacluster --with-daemon-group=haclient 
--disable-fatal-warnings"
+EXTRA_OECONF = "--with-daemon-user=${HA_USER} \
+--with-daemon-group=${HA_GROUP} \
+--disable-fatal-warnings \
+   "
 
 CACHED_CONFIGUREVARS="ac_cv_path_XML2CONFIG=0"
 
 USERADD_PACKAGES = "${PN}"
-USERADD_PARAM_${PN} = "--home-dir=${localstatedir}/lib/heartbeat -g haclient 
-r hacluster"
-GROUPADD_PARAM_${PN} = "-r haclient"
+USERADD_PARAM_${PN} = 
"--home-dir=${localstatedir}/lib/heartbeat/cores/${HA_USER} \
+   -g ${HA_GROUP} -r -s ${sbindir}/nologin -c 'cluster 
user' ${HA_USER} \
+  "
+GROUPADD_PARAM_${PN} = "-r ${HA_GROUP}"
 
 do_configure_prepend() {
 ln -sf ${PKG_CONFIG_SYSROOT_DIR}/usr/include/libxml2/libxml 
${PKG_CONFIG_SYSROOT_DIR}/usr/include/libxml
-- 
2.11.0

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

[yocto] [meta-cgl][PATCH 2/3] cluster-glue: fix the licenses

2017-05-30 Thread jackie.huang

From: Jackie Huang 

It includes LGPL 2.1 as well according to COPYING.LIB.

And point the LIC_FILES_CHKSUM to the checksums of the
license text in the source code.

Signed-off-by: Jackie Huang 
---
 meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb 
b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
index eed7262..b5cf997 100644
--- a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
@@ -3,7 +3,11 @@ the Heartbeat/Pacemaker cluster stack. In essence, Glue is 
everything that \
 is not the cluster messaging layer (Heartbeat), nor the cluster resource 
manager \
 (Pacemaker), nor a Resource Agent."
 
-LICENSE = "GPLv2"
+LICENSE = "GPLv2 & LGPLv2.1"
+LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
+file://COPYING.LIB;md5=243b725d71bb5df4a1e5920b344b86ad \
+"
+
 DEPENDS = "libxml2 libtool glib-2.0 bzip2 util-linux net-snmp openhpi"
 
 SRC_URI = " \
@@ -18,8 +22,6 @@ SRC_URI_append_libc-uclibc = " 
file://kill-stack-protector.patch"
 SRC_URI[md5sum] = "ec620466d6f23affa3b074b72bca7870"
 SRC_URI[sha256sum] = 
"feba102fa1e24b6be2005089ebe362b82d6567af60005cf371679b1b44ec503f"
 
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
-
 inherit autotools useradd pkgconfig systemd
 
 SYSTEMD_SERVICE_${PN} = "logd.service"
-- 
2.11.0

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

[yocto] [meta-cgl][PATCH 0/3] cluster-glue: several fixes

2017-05-30 Thread jackie.huang

From: Jackie Huang 

--
The following changes since commit c0afa706e9cdb650c0e8bb79f503743632350b00:

  core-image-cgl: Remove ROOTFS_PKGMANAGE_BOOTSTRAP (2017-05-24 14:19:13 +0200)

are available in the git repository at:

  https://github.com/jackiehjm/meta-cgl.git jhuang0/up_cluster-glue_170531_0
  https://github.com//tree/jhuang0/up_cluster-glue_170531_0

Jackie Huang (3):
  cluster-glue: inherit systemd
  cluster-glue: fix the licenses
  cluster-glue: update useradd parameters

 .../cluster-glue/cluster-glue_1.0.12.bb| 28 +-
 1 file changed, 22 insertions(+), 6 deletions(-)

-- 
2.11.0

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

[yocto] [meta-cgl][PATCH 1/3] cluster-glue: inherit systemd

2017-05-30 Thread jackie.huang

From: Jackie Huang 

inherit systemd and add PACKAGECONFIG to add proper
configure option and dependency when systemd is enabled.

Signed-off-by: Jackie Huang 
---
 meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb 
b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
index 9604bca..eed7262 100644
--- a/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-glue/cluster-glue_1.0.12.bb
@@ -20,10 +20,16 @@ SRC_URI[sha256sum] = 
"feba102fa1e24b6be2005089ebe362b82d6567af60005cf371679b1b44
 
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.GPLv2;md5=751419260aa954499f7abaabaa882bbe"
 
-inherit autotools useradd pkgconfig
+inherit autotools useradd pkgconfig systemd
+
+SYSTEMD_SERVICE_${PN} = "logd.service"
+SYSTEMD_AUTO_ENABLE = "disable"
 
 S = "${WORKDIR}/Reusable-Cluster-Components-glue--glue-${PV}"
 
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}"
+PACKAGECONFIG[systemd] = 
"--with-systemdsystemunitdir=${systemd_system_unitdir},--without-systemdsystemunitdir,systemd"
+
 EXTRA_OECONF = "--with-daemon-user=hacluster --with-daemon-group=haclient 
--disable-fatal-warnings"
 
 CACHED_CONFIGUREVARS="ac_cv_path_XML2CONFIG=0"
-- 
2.11.0

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

Re: [yocto] (no subject)

2017-05-30 Thread Андрей Кононов


you right, when i take qt5 from morty branch everything builded ok

>Вторник, 30 мая 2017, 22:02 +03:00 от Petter Mabäcker < pet...@technux.se >:
>
>Hi,
>After a quick look, it seems like the problem is related to the Upgrade to Qt 
>5.8 that was done in pyro.
>commit: 333949a Upgrade to Qt 5.8 (in meta-qt5)
>The above mentioned commit causes 
>'./dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0014-Add-IMX-GPU-support.patch'
> (in meta-freescale) to fail. So this patch needs to be updated to match the 
>Qt 5.8 changes (that affects qmake.conf).
>BR Petter
> 
>Petter Mabäcker

Technux 
>www.technux.se
>
>2017-05-30 07:19 skrev Андрей Кононов:
>>i'm trying to build
>>bitbake fsl-image-multimedia-full -k
>>using  pyro repository and my image include QT5 library, but get error. The 
>>same configuration on  morty builded without errors
>>Parsing recipes: 100% 
>>||
>> Time: 0:19:36
>>Parsing of 2258 .bb files complete (0 cached, 2258 parsed). 3050 targets, 506 
>>skipped, 0 masked, 0 errors.
>>NOTE: Resolving any missing task queue dependencies
>>Build Configuration:
>>BB_VERSION = "1.34.0"
>>BUILD_SYS = "x86_64-linux"
>>NATIVELSBSTRING = "linuxmint-18.1"
>>TARGET_SYS = "arm-poky-linux-gnueabi"
>>MACHINE = "imx6qpsabreauto"
>>DISTRO = "poky"
>>DISTRO_VERSION = "2.3"
>>TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
>>TARGET_FPU = "hard"
>>meta 
>>meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
>>meta-oe 
>>meta-gnome 
>>meta-multimedia = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
>>meta-freescale = "HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
>>meta-freescale-3rdparty = "HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
>>meta-freescale-distro = "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
>>meta-qt5 = "master:6605c48f3a900da26425ef31d83eb1c95d551531"
>>meta-ruby 
>>meta-networking 
>>meta-python 
>>meta-filesystems = "HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
>>Initialising tasks: 100% 
>>|#|
>> Time: 0:02:40
>>NOTE: Executing SetScene Tasks
>>NOTE: Executing RunQueue Tasks
>>ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Command Error: 'quilt 
>>--quiltrc 
>>/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
>> push' exited with 0 Output:
>>Applying patch 0014-Add-IMX-GPU-support.patch
>>patching file mkspecs/linux-oe-g++/qmake.conf
>>Hunk #1 FAILED at 39.
>>1 out of 1 hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
>>Patch 0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
>>ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed: 
>>patch_do_patch
>>ERROR: Logfile of failure stored in: 
>>/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
>>ERROR: Task 
>>(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
>> failed with exit code '1'
>>WARNING: ttf-arphic-uming-20080216-r6 do_populate_lic: ttf-arphic-uming: No 
>>generic license file exists for: Arphic-Public-License in any provider
>>NOTE: Tasks Summary: Attempted 5116 tasks of which 6 didn't need to be rerun 
>>and 1 failed.
>>Summary: 1 task failed:
>>/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
>>Summary: There were 2 WARNING messages shown.
>>Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>>-- 
>>Андрей Кононов
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-cgl][PATCH] openipmi: remove the bbappend

2017-05-30 Thread jackie.huang

From: Jackie Huang 

The recipe in meta-oe is version 2.0.22 now, in which
the perl modules are packaged in openipmi-perl,
so this bbappend is not needed any more.

Signed-off-by: Jackie Huang 
---
 meta-cgl-common/recipes-extended/openipmi/openipmi_2.0.21.bbappend | 2 --
 1 file changed, 2 deletions(-)
 delete mode 100644 
meta-cgl-common/recipes-extended/openipmi/openipmi_2.0.21.bbappend

diff --git a/meta-cgl-common/recipes-extended/openipmi/openipmi_2.0.21.bbappend 
b/meta-cgl-common/recipes-extended/openipmi/openipmi_2.0.21.bbappend
deleted file mode 100644
index 72e732b..000
--- a/meta-cgl-common/recipes-extended/openipmi/openipmi_2.0.21.bbappend
+++ /dev/null
@@ -1,2 +0,0 @@
-FILES_${PN} += "/usr/lib/perl5"
-FILES_${PN}-dbg += "/usr/lib/perl5/auto/OpenIPMI/.debug"
-- 
2.11.0

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

Re: [yocto] Kernel config fragments ignored

2017-05-30 Thread Bruce Ashfield


On 2017-05-30 9:15 PM, Paul D. DeRocco wrote:

From: Paul D. DeRocco

I ported a working build from Fido to Morty, made a few
tweaks in response
to error messages (mostly updating version numbers), but it's
not finding
my kernel configuration fragments. This is supposed to be an i386 arch
system, but it insists upon building an x86_64 kernel. The
.config file it
generates does not include my configuration fragments, which contain
things like CONFIG_64BIT=n and CONFIG_X86_32=y.


I'm still stumped by this, but I've debugged it further. My top level
chroma32-bsp-preempt-rt.scc file contains (among other things) the line

 include ktypes/preempt-rt/preempt-rt.scc nopatch

Building the kernel copies the following files into
tmp/work/chroma32_bsp-poky-linux/linux-yocto-rt/4.8.12+blahblah

 chroma32-bsp-user-config.cfg
 chroma32-bsp-user-features.scc (empty)

but it doesn't copy the following files anywhere

 chroma32-bsp-preempt-rt.scc
 chroma32-bsp.scc
 chroma32-bsp.cfg

so none of the values from either .cfg file appear in the resulting
.config file.

If I change the above line to

 include ktypes/standard/standard.scc nopatch

then tmp/work/chroma32_bsp-poky-linux/linux-yocto-rt/4.8.12+blahblah
contains

 chroma32-bsp-preempt-rt.scc
 chroma32-bsp-user-config.cfg
 chroma32-bsp-user-features.scc (empty)

and
tmp/work-shared/chroma32-bsp/kernel-source/.kernel-meta/configs/standard
contains

 chroma32-bsp.cfg
 chroma32-bsp-user-config.cfg

and everything in them is included in the .config file.

Both the preempt-rt.scc and standard.scc files pull in a lot of stuff, and
they are quite different from each other. What difference between the two
could account for my config fragments being ignored when I use the first
one?


It wouldn't be the difference.

Is this something that I can configure and build myself ? I changed
the processing model between those releases, but I tested migration
of a few BSPs and they all worked.

So something different is happening here.

I can't say what is is just by reading the description, but if I could
build something like you are describing, I can figure out what's happening.

Bruce








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

Re: [yocto] Kernel config fragments ignored

2017-05-30 Thread Paul D. DeRocco

> From: Paul D. DeRocco
> 
> I ported a working build from Fido to Morty, made a few 
> tweaks in response
> to error messages (mostly updating version numbers), but it's 
> not finding
> my kernel configuration fragments. This is supposed to be an i386 arch
> system, but it insists upon building an x86_64 kernel. The 
> .config file it
> generates does not include my configuration fragments, which contain
> things like CONFIG_64BIT=n and CONFIG_X86_32=y.

I'm still stumped by this, but I've debugged it further. My top level
chroma32-bsp-preempt-rt.scc file contains (among other things) the line

include ktypes/preempt-rt/preempt-rt.scc nopatch

Building the kernel copies the following files into
tmp/work/chroma32_bsp-poky-linux/linux-yocto-rt/4.8.12+blahblah

chroma32-bsp-user-config.cfg
chroma32-bsp-user-features.scc (empty)

but it doesn't copy the following files anywhere

chroma32-bsp-preempt-rt.scc
chroma32-bsp.scc
chroma32-bsp.cfg

so none of the values from either .cfg file appear in the resulting
.config file.

If I change the above line to

include ktypes/standard/standard.scc nopatch

then tmp/work/chroma32_bsp-poky-linux/linux-yocto-rt/4.8.12+blahblah
contains

chroma32-bsp-preempt-rt.scc
chroma32-bsp-user-config.cfg
chroma32-bsp-user-features.scc (empty)

and
tmp/work-shared/chroma32-bsp/kernel-source/.kernel-meta/configs/standard
contains

chroma32-bsp.cfg
chroma32-bsp-user-config.cfg

and everything in them is included in the .config file.

Both the preempt-rt.scc and standard.scc files pull in a lot of stuff, and
they are quite different from each other. What difference between the two
could account for my config fragments being ignored when I use the first
one?

-- 

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

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

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Bruce Ashfield

On Tue, May 30, 2017 at 6:52 PM, Alejandro Hernandez <
alejandro.hernan...@linux.intel.com> wrote:

> Hey Andy,
>
>
> On 05/30/2017 05:32 PM, Andre McCurdy wrote:
>
>> On Tue, May 30, 2017 at 1:12 PM, Alejandro Hernandez
>>  wrote:
>>
>>> Hey Leo,
>>>
>>> Nope, this change only applies to qemuARM, the other ARM based BSPs are
>>> based on > ARMv6
>>>
>>> Alejandro
>>>
>>>
>>> On 05/30/2017 02:59 PM, Leonardo Sandoval wrote:
>>>
 Alex,

 is this change only applies to qemu arm? I wonder if the native arm arch
 needs a similar series.

 Leo

 On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:

> The SMP kernel config presents issues on qemuarm because:
>
> CONFIG_SMP=y
> Dependencies Missing:
> - CPU_V6K or CPU_V7:
>   These are selected by setting:
>   CONFIG_ARCH_MULTI_V7=y
>   or
>   CONFIG_ARCH_MULTI_V6=y
>
> But our QEMU + ARM BSPs are based on armv4/v5 hence they are
> incompatible with CONFIG_SMP.
>
 Maybe time to think (again) about updating OE's qemu ARM builds to
>> ARMv7.
>>
> I believe qemu has deep issues with newer ARMs, and thats why it's been
> kept like that.


Qemu itself should be fine with the newer ARMs .. but we've just targeted a
lowest common
denominator (and simple) ARM arch for this target. Since the primary goal
isn't testing the ISA or arch
specifics via qemuarm/qemuarm64 (rather, sanity, base arch support, etc).

That being said, as long as a newer platform/board was chosen that had full
disk support
(something that the qemuarma9 lacks), then it is feasible to do an update
to something
newer. Alternatively, we could keep the platform the same and update the
CPU definition .. but
there's not a huge value in that.

But if we did bring in something newer, we'd have to drop the existing
qemuarm and document that
we aren't doing any coverage on the older ARM arches.

Bruce


>
>
>> This patch fixes the script, and avoids offering SMP to the user
> when the created BSP is based on QEMU + ARM.
>
>
 [YOCTO #11426]
>
> Signed-off-by: Alejandro Hernandez  el.com>
> ---
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_
> 4.1.bbappend
> | 1 +
>
> .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
> | 1
> +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_
> 4.4.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_
> 4.8.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend
> | 1 +
>.../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend
> | 1 +
>9 files changed, 9 insertions(+)
>
> diff --git
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-dev.bbappend
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-dev.bbappend
> index 7e3ce5ba12d..11105ebcc26 100644
> ---
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-dev.bbappend
> +++
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-dev.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>{{ if need_new_kbranch == "n": }}
>KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>+{{ if qemuarch != "arm": }}
>{{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP
> support? (y/n)" default:"y"}}
>{{ if smp == "y": }}
>KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-tiny_4.1.bbappend
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-tiny_4.1.bbappend
> index 81392ce38ac..ad77a662682 100644
> ---
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-tiny_4.1.bbappend
> +++
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/
> linux/linux-yocto-tiny_4.1.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>{{ if need_new_kbranch == "n": }}
>KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>+{{ if qemuarch != "arm": }}
>{{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
> support? (y/n)" default:"y"}}
>{{ if smp == "y": }}
>KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Andre McCurdy

On Tue, May 30, 2017 at 3:52 PM, Alejandro Hernandez
 wrote:
> Hey Andy,
> On 05/30/2017 05:32 PM, Andre McCurdy wrote:
>> On Tue, May 30, 2017 at 1:12 PM, Alejandro Hernandez
>>  wrote:
>>>
>>> Hey Leo,
>>>
>>> Nope, this change only applies to qemuARM, the other ARM based BSPs are
>>> based on > ARMv6
>>>
>>> Alejandro
>>>
>>> On 05/30/2017 02:59 PM, Leonardo Sandoval wrote:

 Alex,

 is this change only applies to qemu arm? I wonder if the native arm arch
 needs a similar series.

 Leo

 On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:
>
> The SMP kernel config presents issues on qemuarm because:
>
> CONFIG_SMP=y
> Dependencies Missing:
> - CPU_V6K or CPU_V7:
>   These are selected by setting:
>   CONFIG_ARCH_MULTI_V7=y
>   or
>   CONFIG_ARCH_MULTI_V6=y
>
> But our QEMU + ARM BSPs are based on armv4/v5 hence they are
> incompatible with CONFIG_SMP.
>>
>> Maybe time to think (again) about updating OE's qemu ARM builds to ARMv7.
>
> I believe qemu has deep issues with newer ARMs, and thats why it's been kept
> like that.

I think the stated reason is that since almost no real world
ARMv4/ARMv5 based projects track new releases of OE, the ARM qemu
targets are held back to ensure that ARMv4/ARMv5 continue to get some
test coverage (the fear being that if these targets don't get tested
via the OE qemuarm builds they won't get tested at all).
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Alejandro Hernandez


Hey Andy,


On 05/30/2017 05:32 PM, Andre McCurdy wrote:

On Tue, May 30, 2017 at 1:12 PM, Alejandro Hernandez
 wrote:

Hey Leo,

Nope, this change only applies to qemuARM, the other ARM based BSPs are
based on > ARMv6

Alejandro


On 05/30/2017 02:59 PM, Leonardo Sandoval wrote:

Alex,

is this change only applies to qemu arm? I wonder if the native arm arch
needs a similar series.

Leo

On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:

The SMP kernel config presents issues on qemuarm because:

CONFIG_SMP=y
Dependencies Missing:
- CPU_V6K or CPU_V7:
  These are selected by setting:
  CONFIG_ARCH_MULTI_V7=y
  or
  CONFIG_ARCH_MULTI_V6=y

But our QEMU + ARM BSPs are based on armv4/v5 hence they are
incompatible with CONFIG_SMP.

Maybe time to think (again) about updating OE's qemu ARM builds to ARMv7.
I believe qemu has deep issues with newer ARMs, and thats why it's been 
kept like that.



This patch fixes the script, and avoids offering SMP to the user
when the created BSP is based on QEMU + ARM.




[YOCTO #11426]

Signed-off-by: Alejandro Hernandez 
---
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
| 1 +

.../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend | 1
+
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend
| 1 +
   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend
| 1 +
   9 files changed, 9 insertions(+)

diff --git
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
index 7e3ce5ba12d..11105ebcc26 100644
---
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
+++
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
   {{ if need_new_kbranch == "n": }}
   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
   +{{ if qemuarch != "arm": }}
   {{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP
support? (y/n)" default:"y"}}
   {{ if smp == "y": }}
   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
index 81392ce38ac..ad77a662682 100644
---
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
+++
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
   {{ if need_new_kbranch == "n": }}
   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
   +{{ if qemuarch != "arm": }}
   {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
support? (y/n)" default:"y"}}
   {{ if smp == "y": }}
   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
index 29ad17b2009..9b5f8016841 100644
---
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
+++
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
   {{ if need_new_kbranch == "n": }}
   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
   +{{ if qemuarch != "arm": }}
   {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
support? (y/n)" default:"y"}}
   {{ if smp == "y": }}
   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
index a73b1aa132f..2fc992992cf 100644
---
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
+++
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
   {{ if need_new_kbranch == "n": }}
   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
   +{{ if qemuarch != "arm": }}
   {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
support? (y/n)" default:"y"}}
   {{ if smp

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Andre McCurdy

On Tue, May 30, 2017 at 1:12 PM, Alejandro Hernandez
 wrote:
> Hey Leo,
>
> Nope, this change only applies to qemuARM, the other ARM based BSPs are
> based on > ARMv6
>
> Alejandro
>
>
> On 05/30/2017 02:59 PM, Leonardo Sandoval wrote:
>>
>> Alex,
>>
>> is this change only applies to qemu arm? I wonder if the native arm arch
>> needs a similar series.
>>
>> Leo
>>
>> On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:
>>>
>>> The SMP kernel config presents issues on qemuarm because:
>>>
>>> CONFIG_SMP=y
>>> Dependencies Missing:
>>>- CPU_V6K or CPU_V7:
>>>  These are selected by setting:
>>>  CONFIG_ARCH_MULTI_V7=y
>>>  or
>>>  CONFIG_ARCH_MULTI_V6=y
>>>
>>> But our QEMU + ARM BSPs are based on armv4/v5 hence they are
>>> incompatible with CONFIG_SMP.

Maybe time to think (again) about updating OE's qemu ARM builds to ARMv7.

>>> This patch fixes the script, and avoids offering SMP to the user
>>> when the created BSP is based on QEMU + ARM.
>>>
>>
>>
>>> [YOCTO #11426]
>>>
>>> Signed-off-by: Alejandro Hernandez 
>>> ---
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>>> | 1 +
>>>
>>> .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend | 1
>>> +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend
>>> | 1 +
>>>   .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend
>>> | 1 +
>>>   9 files changed, 9 insertions(+)
>>>
>>> diff --git
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>>> index 7e3ce5ba12d..11105ebcc26 100644
>>> ---
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>>> +++
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>>> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>>>   {{ if need_new_kbranch == "n": }}
>>>   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>>>   +{{ if qemuarch != "arm": }}
>>>   {{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP
>>> support? (y/n)" default:"y"}}
>>>   {{ if smp == "y": }}
>>>   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
>>> diff --git
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>>> index 81392ce38ac..ad77a662682 100644
>>> ---
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>>> +++
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>>> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>>>   {{ if need_new_kbranch == "n": }}
>>>   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>>>   +{{ if qemuarch != "arm": }}
>>>   {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
>>> support? (y/n)" default:"y"}}
>>>   {{ if smp == "y": }}
>>>   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
>>> diff --git
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
>>> index 29ad17b2009..9b5f8016841 100644
>>> ---
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
>>> +++
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
>>> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>>>   {{ if need_new_kbranch == "n": }}
>>>   KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>>>   +{{ if qemuarch != "arm": }}
>>>   {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP
>>> support? (y/n)" default:"y"}}
>>>   {{ if smp == "y": }}
>>>   KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
>>> diff --git
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>>> index a73b1aa132f..2fc992992cf 100644
>>> ---
>>> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>>> +++
>>> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>>> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Alejandro Hernandez


Hey Leo,

Nope, this change only applies to qemuARM, the other ARM based BSPs are 
based on > ARMv6


Alejandro

On 05/30/2017 02:59 PM, Leonardo Sandoval wrote:

Alex,

is this change only applies to qemu arm? I wonder if the native arm arch
needs a similar series.

Leo

On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:

The SMP kernel config presents issues on qemuarm because:

CONFIG_SMP=y
Dependencies Missing:
   - CPU_V6K or CPU_V7:
 These are selected by setting:
 CONFIG_ARCH_MULTI_V7=y
 or
 CONFIG_ARCH_MULTI_V6=y

But our QEMU + ARM BSPs are based on armv4/v5 hence they are
incompatible with CONFIG_SMP.

This patch fixes the script, and avoids offering SMP to the user
when the created BSP is based on QEMU + ARM.





[YOCTO #11426]

Signed-off-by: Alejandro Hernandez 
---
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend   | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend  | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend  | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend  | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend   | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend  | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend   | 1 +
  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend   | 1 +
  9 files changed, 9 insertions(+)

diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
index 7e3ce5ba12d..11105ebcc26 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
  {{ if need_new_kbranch == "n": }}
  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
  
+{{ if qemuarch != "arm": }}

  {{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP support? (y/n)" 
default:"y"}}
  {{ if smp == "y": }}
  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
index 81392ce38ac..ad77a662682 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
  {{ if need_new_kbranch == "n": }}
  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
  
+{{ if qemuarch != "arm": }}

  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? (y/n)" 
default:"y"}}
  {{ if smp == "y": }}
  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
index 29ad17b2009..9b5f8016841 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
  {{ if need_new_kbranch == "n": }}
  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
  
+{{ if qemuarch != "arm": }}

  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? (y/n)" 
default:"y"}}
  {{ if smp == "y": }}
  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
index a73b1aa132f..2fc992992cf 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
  {{ if need_new_kbranch == "n": }}
  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
  
+{{ if qemuarch != "arm": }}

  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? (y/n)" 
default:"y"}}
  {{ if smp == "y": }}
  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Leonardo Sandoval

Alex,

is this change only applies to qemu arm? I wonder if the native arm arch
needs a similar series.

Leo

On Tue, 2017-05-30 at 11:44 -0700, Alejandro Hernandez wrote:
> The SMP kernel config presents issues on qemuarm because:
> 
> CONFIG_SMP=y
> Dependencies Missing:
>   - CPU_V6K or CPU_V7:
> These are selected by setting:
> CONFIG_ARCH_MULTI_V7=y
> or
> CONFIG_ARCH_MULTI_V6=y
> 
> But our QEMU + ARM BSPs are based on armv4/v5 hence they are
> incompatible with CONFIG_SMP.
> 
> This patch fixes the script, and avoids offering SMP to the user
> when the created BSP is based on QEMU + ARM.
> 



> [YOCTO #11426]
> 
> Signed-off-by: Alejandro Hernandez 
> ---
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend   | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend  | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend  | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend  | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend   | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend  | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend   | 1 
> +
>  .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend   | 1 
> +
>  9 files changed, 9 insertions(+)
> 
> diff --git 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
>  
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
> index 7e3ce5ba12d..11105ebcc26 100644
> --- 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
> +++ 
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>  {{ if need_new_kbranch == "n": }}
>  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>  
> +{{ if qemuarch != "arm": }}
>  {{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP 
> support? (y/n)" default:"y"}}
>  {{ if smp == "y": }}
>  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
>  
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
> index 81392ce38ac..ad77a662682 100644
> --- 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
> +++ 
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>  {{ if need_new_kbranch == "n": }}
>  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>  
> +{{ if qemuarch != "arm": }}
>  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
> (y/n)" default:"y"}}
>  {{ if smp == "y": }}
>  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
>  
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
> index 29ad17b2009..9b5f8016841 100644
> --- 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
> +++ 
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>  {{ if need_new_kbranch == "n": }}
>  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>  
> +{{ if qemuarch != "arm": }}
>  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
> (y/n)" default:"y"}}
>  {{ if smp == "y": }}
>  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
>  
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
> index a73b1aa132f..2fc992992cf 100644
> --- 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
> +++ 
> b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
> @@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
>  {{ if need_new_kbranch == "n": }}
>  KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
>  
> +{{ if qemuarch != "arm": }}
>  {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
> (y/n)" default:"y"}}
>  {{ if smp == "y": }}
>  KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
> diff --git 
> a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
>  
> b/scripts/lib/bsp/substrate/target/arch/qemu/r

Re: [yocto] (no subject)

2017-05-30 Thread Petter Mabäcker

 

Hi, 

After a quick look, it seems like the problem is related to
the Upgrade to Qt 5.8 that was done in pyro. 

commit: 333949a Upgrade
to Qt 5.8 (in meta-qt5) 

The above mentioned commit causes
'./dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase/0014-Add-IMX-GPU-support.patch'
(in meta-freescale) to fail. So this patch needs to be updated to match
the Qt 5.8 changes (that affects qmake.conf). 

BR Petter 

Petter
Mabäcker

Technux 
www.technux.se

2017-05-30 07:19
skrev Андрей Кононов: 

> i'm trying to build
> bitbake
fsl-image-multimedia-full -k
> using PYRO repository and my image
include QT5 library, but get error. The same configuration on MORTY
builded without errors 
> 
> Parsing recipes: 100%
||
Time: 0:19:36
> Parsing of 2258 .bb files complete (0 cached, 2258
parsed). 3050 targets, 506 skipped, 0 masked, 0 errors.
> NOTE:
Resolving any missing task queue dependencies 
> 
> Build
Configuration:
> BB_VERSION = "1.34.0"
> BUILD_SYS = "x86_64-linux"
>
NATIVELSBSTRING = "linuxmint-18.1"
> TARGET_SYS =
"arm-poky-linux-gnueabi"
> MACHINE = "imx6qpsabreauto"
> DISTRO =
"poky"
> DISTRO_VERSION = "2.3"
> TUNE_FEATURES = "arm armv7a vfp thumb
neon callconvention-hard cortexa9"
> TARGET_FPU = "hard"
> meta 
>
meta-poky = "HEAD:31389f8b0088a8a83aa5e50f11359b39934e4640"
> meta-oe 
>
meta-gnome 
> meta-multimedia =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
> meta-freescale =
"HEAD:a65d13c315db447adda68b47faeb4c0afd0655b8"
>
meta-freescale-3rdparty =
"HEAD:1f37698ac62945b6531a316ec1232af23cc6c050"
> meta-freescale-distro
= "HEAD:cd5c7a2539f40004f74126e9fdf08254fd9a6390"
> meta-qt5 =
"master:6605c48f3a900da26425ef31d83eb1c95d551531"
> meta-ruby 
>
meta-networking 
> meta-python 
> meta-filesystems =
"HEAD:5e82995148a2844c6f483ae5ddd1438d87ea9fb7" 
> 
> Initialising
tasks: 100%
|#|
Time: 0:02:40
> NOTE: Executing SetScene Tasks
> NOTE: Executing
RunQueue Tasks
> ERROR: qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch:
Command Error: 'quilt --quiltrc
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/recipe-sysroot-native/etc/quiltrc
push' exited with 0 Output:
> Applying patch
0014-Add-IMX-GPU-support.patch
> patching file
mkspecs/linux-oe-g++/qmake.conf
> Hunk #1 FAILED at 39.
> 1 out of 1
hunk FAILED -- rejects in file mkspecs/linux-oe-g++/qmake.conf
> Patch
0014-Add-IMX-GPU-support.patch does not apply (enforce with -f)
> ERROR:
qtbase-5.8.0+gitAUTOINC+49dc9aa409-r0 do_patch: Function failed:
patch_do_patch
> ERROR: Logfile of failure stored in:
/media/barsuk/ext4.720/pyro/rootfs.systemd.qp/tmp/work/cortexa9hf-neon-mx6qdl-poky-linux-gnueabi/qtbase/5.8.0+gitAUTOINC+49dc9aa409-r0/temp/log.do_patch.8895
>
ERROR: Task
(/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch)
failed with exit code '1'
> WARNING: ttf-arphic-uming-20080216-r6
do_populate_lic: ttf-arphic-uming: No generic license file exists for:
Arphic-Public-License in any provider
> NOTE: Tasks Summary: Attempted
5116 tasks of which 6 didn't need to be rerun and 1 failed. 
> 
>
Summary: 1 task failed:
>
/media/barsuk/ext4.720/pyro/sources/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_patch
>
Summary: There were 2 WARNING messages shown.
> Summary: There were 2
ERROR messages shown, returning a non-zero exit code. 
> 
> -- 
> Андрей
Кононов
 -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

2017-05-30 Thread Alejandro Hernandez

The SMP kernel config presents issues on qemuarm because:

CONFIG_SMP=y
Dependencies Missing:
  - CPU_V6K or CPU_V7:
These are selected by setting:
CONFIG_ARCH_MULTI_V7=y
or
CONFIG_ARCH_MULTI_V6=y

But our QEMU + ARM BSPs are based on armv4/v5 hence they are
incompatible with CONFIG_SMP.

This patch fixes the script, and avoids offering SMP to the user
when the created BSP is based on QEMU + ARM.

[YOCTO #11426]

Signed-off-by: Alejandro Hernandez 
---
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend   | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend  | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend  | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend  | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.1.bbappend   | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.10.bbappend  | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.4.bbappend   | 1 +
 .../target/arch/qemu/recipes-kernel/linux/linux-yocto_4.8.bbappend   | 1 +
 9 files changed, 9 insertions(+)

diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
index 7e3ce5ba12d..11105ebcc26 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
 {{ if need_new_kbranch == "n": }}
 KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
 
+{{ if qemuarch != "arm": }}
 {{ input type:"boolean" name:"smp" prio:"30" msg:"Would you like SMP support? 
(y/n)" default:"y"}}
 {{ if smp == "y": }}
 KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
index 81392ce38ac..ad77a662682 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.1.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
 {{ if need_new_kbranch == "n": }}
 KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
 
+{{ if qemuarch != "arm": }}
 {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
(y/n)" default:"y"}}
 {{ if smp == "y": }}
 KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
index 29ad17b2009..9b5f8016841 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.10.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
 {{ if need_new_kbranch == "n": }}
 KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
 
+{{ if qemuarch != "arm": }}
 {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
(y/n)" default:"y"}}
 {{ if smp == "y": }}
 KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
index a73b1aa132f..2fc992992cf 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.4.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
 {{ if need_new_kbranch == "n": }}
 KBRANCH_{{=machine}}  = "{{=existing_kbranch}}"
 
+{{ if qemuarch != "arm": }}
 {{ input type:"boolean" name:"smp" prio:"30" msg:"Do you need SMP support? 
(y/n)" default:"y"}}
 {{ if smp == "y": }}
 KERNEL_FEATURES_append_{{=machine}} += " cfg/smp.scc"
diff --git 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
index 7d40671fd43..868d12af04b 100644
--- 
a/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
+++ 
b/scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/linux-yocto-tiny_4.8.bbappend
@@ -45,6 +45,7 @@ COMPATIBLE_MACHINE_{{=machine}} = "{{=machine}}"
 {{ if need_new_kbranch == "n": }}
 KBRANCH_{{=machine}}  =

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

2017-05-30 Thread Khem Raj

On Tue, May 30, 2017 at 10:25 AM, Andre McCurdy  wrote:
> On Tue, May 30, 2017 at 10:15 AM, Paul Barker  wrote:
>> On 30 May 2017 5:08 p.m., "Khem Raj"  wrote:
>>
>> On Tue, May 30, 2017 at 12:57 AM, Martin Jansa 
>> wrote:
>>> * use latest revision in rpi-4.11.y branch
>>> * using AUTOREV causes bitbake to run git ls-remote on the github.com
>>> repository in order
>>>   to convert AUTOREV to currently latest SRCREV even when you don't use
>>> linux-raspberrypi_dev
>>>   at all, just happen to have meta-raspberrypi layer in your
>>> bblayers.conf, that's bad for
>>>   people who want to be able to build without network access (completely
>>> from premirror)
>>>
>>
>> These branches get rebased often so locking SRCREV caused another
>> kind of problem. what we can do is.
>>
>> 1. Let user like you override the SRCREC via a bbappend or conf file.
>> so change the assignment to ?=
>> 2. Delete the recipe completely. We lose some of upstream testing.
>>
>> We should be able to skip the recipe if it isn't selected as the preferred
>> version and/or provider of "virtual/kernel". I'm out at the minute so can't
>> look at it now but will try to take a look later this week.
>
> The linux-yocto-dev.bb recipe contains an example of doing that.
>

ah perfect. Thats what we need here

http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-kernel/linux/linux-yocto-dev.bb?h=master#n28

please rename the recipe to be linux-raspberrypi-dev.bb and add the magic
above and send a v2

>> --
>> ___
>> 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] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

2017-05-30 Thread Andre McCurdy

On Tue, May 30, 2017 at 10:15 AM, Paul Barker  wrote:
> On 30 May 2017 5:08 p.m., "Khem Raj"  wrote:
>
> On Tue, May 30, 2017 at 12:57 AM, Martin Jansa 
> wrote:
>> * use latest revision in rpi-4.11.y branch
>> * using AUTOREV causes bitbake to run git ls-remote on the github.com
>> repository in order
>>   to convert AUTOREV to currently latest SRCREV even when you don't use
>> linux-raspberrypi_dev
>>   at all, just happen to have meta-raspberrypi layer in your
>> bblayers.conf, that's bad for
>>   people who want to be able to build without network access (completely
>> from premirror)
>>
>
> These branches get rebased often so locking SRCREV caused another
> kind of problem. what we can do is.
>
> 1. Let user like you override the SRCREC via a bbappend or conf file.
> so change the assignment to ?=
> 2. Delete the recipe completely. We lose some of upstream testing.
>
> We should be able to skip the recipe if it isn't selected as the preferred
> version and/or provider of "virtual/kernel". I'm out at the minute so can't
> look at it now but will try to take a look later this week.

The linux-yocto-dev.bb recipe contains an example of doing that.

> --
> ___
> 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] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

2017-05-30 Thread Paul Barker

On 30 May 2017 5:08 p.m., "Khem Raj"  wrote:

On Tue, May 30, 2017 at 12:57 AM, Martin Jansa 
wrote:
> * use latest revision in rpi-4.11.y branch
> * using AUTOREV causes bitbake to run git ls-remote on the github.com
repository in order
>   to convert AUTOREV to currently latest SRCREV even when you don't use
linux-raspberrypi_dev
>   at all, just happen to have meta-raspberrypi layer in your
bblayers.conf, that's bad for
>   people who want to be able to build without network access (completely
from premirror)
>

These branches get rebased often so locking SRCREV caused another
kind of problem. what we can do is.

1. Let user like you override the SRCREC via a bbappend or conf file.
so change the assignment to ?=
2. Delete the recipe completely. We lose some of upstream testing.


We should be able to skip the recipe if it isn't selected as the preferred
version and/or provider of "virtual/kernel". I'm out at the minute so can't
look at it now but will try to take a look later this week.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW22’17

2017-05-30 Thread Jolley, Stephen K

Current Dev Position: Preparing for YP 2.4 M1

Next Deadline: YP 2.4 M1 Cut off is June 12, 2017


SWAT team rotation: Juro -> Anibal on May 26, 2017.

SWAT team rotation: Anibal -> Todor on June 2, 2017.

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

·Morty 2.2.2 build is in for QA. Thanks to Ross for finding some 
selftest issues (and also RP)

·Krogoth build remain broken. Mingw autobuilder config issue is being 
worked by Joshua, RP has root caused selftest issue and should be resolved.

·There have been a spate of CVE fixes into master, need to consider 
these for pyro 2.3.1 release which ideally will follow 2.2.2 into QA.

·Patches are flowing into master but rate limited due to team 
travel/vacation. We’re continuing to see patch quality issues which is limiting 
the flow.

·Have some exciting performance improvements coming for oe-selftest and 
rpm and other package generation parallelization.


Planned upcoming dot releases:

YP 2.1.3 Cut off May 22, 2017 - Running late due to issues.

YP 2.1.3 Release by June 3, 2017

YP 2.3.1 Cut off May 30, 2017

YP 2.3.1 Release by June 9, 2017

YP 2.2.2 Cut off June 5, 2017 - Put into QA early.

YP 2.2.2 Release by June, 16 2017

YP 2.3.2 Cut off Aug 7, 2017

YP 2.3.2 Release by Aug. 18, 2017


Key YP 2.4 Dates are:

YP 2.4 M1 Cut off is June 12, 2017

YP 2.4 M1 Release by June 23, 2017

YP 2.4 M2 Cut off is July 17, 2017

YP 2.4 M2 Release by July 28, 2017

YP 2.4 M3 Cut off is Aug. 21, 2017

YP 2.4 M3 Release by Sept. 1, 2017

YP 2.4 M4 (Final) Cut off is Sept. 18, 2017

YP 2.4 M4 (Final) Release by Oct. 20, 2017


Tracking Metrics:

WDD 2797 (last week 2697)

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.4_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.4_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.4_Features

[If anyone has suggestions for other information you’d like to see on this 
weekly status update, let us know!]

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•   Work Telephone:(503) 712-0534
•Cell:   (208) 244-4460
• Email:stephen.k.jol...@intel.com

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

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

2017-05-30 Thread Khem Raj

On Tue, May 30, 2017 at 12:57 AM, Martin Jansa  wrote:
> * use latest revision in rpi-4.11.y branch
> * using AUTOREV causes bitbake to run git ls-remote on the github.com 
> repository in order
>   to convert AUTOREV to currently latest SRCREV even when you don't use 
> linux-raspberrypi_dev
>   at all, just happen to have meta-raspberrypi layer in your bblayers.conf, 
> that's bad for
>   people who want to be able to build without network access (completely from 
> premirror)
>

These branches get rebased often so locking SRCREV caused another
kind of problem. what we can do is.

1. Let user like you override the SRCREC via a bbappend or conf file.
so change the assignment to ?=
2. Delete the recipe completely. We lose some of upstream testing.

> Signed-off-by: Martin Jansa 
> ---
>  recipes-kernel/linux/linux-raspberrypi_dev.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi_dev.bb 
> b/recipes-kernel/linux/linux-raspberrypi_dev.bb
> index 239d630..06771b9 100644
> --- a/recipes-kernel/linux/linux-raspberrypi_dev.bb
> +++ b/recipes-kernel/linux/linux-raspberrypi_dev.bb
> @@ -3,7 +3,7 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-dev:"
>  LINUX_VERSION ?= "4.11"
>  LINUX_RPI_DEV_BRANCH ?= "rpi-4.11.y"
>
> -SRCREV = "${AUTOREV}"
> +SRCREV = "3b3178eb6c0ddea0a6856f16f52b5d2c21ed9299"
>  SRC_URI = 
> "git://github.com/raspberrypi/linux.git;protocol=git;branch=${LINUX_RPI_DEV_BRANCH}
>  \
> 
> file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
>  "
> --
> 2.13.0
>
> --
> ___
> 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] Include meta-qt5 in an eSDK build ?

2017-05-30 Thread Jan-Simon Möller

Any pointers if it is possible to build the eSDK with meta-qt5 ?

-- 

Dipl.-Ing.
Jan-Simon Möller

jansimon.moel...@gmx.de
On Thursday 25 May 2017 20:27:09 Jan-Simon Möller wrote:
> Hi !
> How can I build an eSDK that includes meta-qt5 ?
> 
> The examples I found use the 'traditional' sdk and
> add the classes from meta-qt5.
> 
> But I have not seen the eSDK being used, yet.

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

Re: [yocto] How to install dbg package and not its dependencies?

2017-05-30 Thread Petter Mabäcker

 

Hi, 

If the problem is the footprint, then you can add below line
in the libexample recipe: 

INHIBIT_PACKAGE_DEBUG_SPLIT = "1" 

This
will prevent the build system from adding any debug info in the
libexample-dbg package. 

BR Petter 

[1] -
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-INHIBIT_PACKAGE_DEBUG_SPLIT


Petter Mabäcker

Technux

www.technux.se

2017-05-30 04:17 skrev Ngọc Thi
Huỳnh: 

> I have both app-example-DBG & app-example in IMAGE_INSTALL
and the result is app-example-dbg & app-example & libexample-dbg &
libexample are included in the final image. 
> 
> Huỳnh Ngọc Thi
> 
>
-so61pi 
> 
> On Mon, May 29, 2017 at 9:58 PM, Leonardo Sandoval
 wrote:
> 
>> On Sun,
2017-05-28 at 17:23 +0700, Ngọc Thi Huỳnh wrote:
>> > Hi everyone,
>>
>
>> >
>> > Let's say I have app-example package which depends on
libexample.
>> >
>> > When I add app-example-dbg to IMAGE_INSTALL,
libexample-dbg package is
>> > automatically included in the final image
which makes the image size
>> > become bigger.
>> >
>> what about
installing the non-dbg ones?
>> 
>>> 
>> > In this case, is there a way
to prevent libexample-dbg from being
>> > installed?
>> >
>> >
>> >
Thanks,
>> >
>> > Thi Huynh
>> > > --
>> >
___
>> > yocto mailing
list
>> > yocto@yoctoproject.org
>> >
https://lists.yoctoproject.org/listinfo/yocto [1]
 

Links:
--
[1]
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Show cmake warnings as yocto warnings

2017-05-30 Thread Baumann, Michael

Hello,

I am using cmake in my recipes (poky 2.1.2). Is there a way to display cmake 
warnings as yocto warnings?
I can see the cmake warning in the log.do_configure file of my package but it 
is not displayed prominent during bitbake.

Cheers and many thanks in advance,
Michael
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] CMake project not building; building from local git repo possible

2017-05-30 Thread Belisko Marek

Hi Jakob,

On Tue, May 30, 2017 at 11:53 AM, Jakob Hasse
 wrote:
> Hi Marek,
>
> On 30.05.2017 11:37, Belisko Marek wrote:
>>
>> Hi Jakob,
>>
>> On Tue, May 30, 2017 at 11:28 AM, Jakob Hasse
>>  wrote:
>>>
>>> Hi Marek,
>>
>> please don't top post http://www.idallen.com/topposting.html :)
>>>
>>> Thanks for your answer!
>>> I did use a local repo folder since I find it more convenient to make
>>> quick
>>> changes that way, as it is the case right now.
>>
>> Source is fetched only once then it's keep in downloads directory so
>> better use then local repo.
>>>
>>> I applied your changes but I still get the same bitbake errors as before,
>>> as
>>> shown below. The CMake Error log says:
>>> ...
>>> error: unrecognized command line option '-Wmissing-variable-declarations'
>>> ...
>>> error: unrecognized command line option '-Wshorten-64-to-32'
>>
>> Can you give me some more info about poky version, target you're building
>> ...
>
>
> Build Configuration:
> BB_VERSION= "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "arm-dey-linux-gnueabi"
> MACHINE   = "ccimx6ulstarter"
> DISTRO= "dey"
> DISTRO_VERSION= "2.2-r1"
> TUNE_FEATURES = "arm armv7ve vfp thumb neon callconvention-hard
> cortexa7"
> TARGET_FPU= "hard"
>
> We're using the digi embedded yocto here. I think I'll contact their
> support, too.
I think this would be the best ;) as it's probably custom patched build system.
> The arm-dey-linux-gnueabi looks like a normal arm-linux-gnueabi-gcc.
> Please tell me if you think you need more info.
>
> Cheers,
>
> Jakob
>
> --
> Jakob Hasse
> Software Developement
>
> E: jakob.ha...@smart-home-technology.ch
> T: +41 44 552 02 66
>
> Smart Home Technology GmbH
> www.smart-home-technology.ch
>

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

2017-05-30 Thread Martin Jansa

* use latest revision in rpi-4.11.y branch
* using AUTOREV causes bitbake to run git ls-remote on the github.com 
repository in order
  to convert AUTOREV to currently latest SRCREV even when you don't use 
linux-raspberrypi_dev
  at all, just happen to have meta-raspberrypi layer in your bblayers.conf, 
that's bad for
  people who want to be able to build without network access (completely from 
premirror)

Signed-off-by: Martin Jansa 
---
 recipes-kernel/linux/linux-raspberrypi_dev.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_dev.bb 
b/recipes-kernel/linux/linux-raspberrypi_dev.bb
index 239d630..06771b9 100644
--- a/recipes-kernel/linux/linux-raspberrypi_dev.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_dev.bb
@@ -3,7 +3,7 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-dev:"
 LINUX_VERSION ?= "4.11"
 LINUX_RPI_DEV_BRANCH ?= "rpi-4.11.y"
 
-SRCREV = "${AUTOREV}"
+SRCREV = "3b3178eb6c0ddea0a6856f16f52b5d2c21ed9299"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=${LINUX_RPI_DEV_BRANCH}
 \

file://0001-build-arm64-Add-rules-for-.dtbo-files-for-dts-overla.patch \
 "
-- 
2.13.0

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

Re: [yocto] CMake project not building; building from local git repo possible

2017-05-30 Thread Jakob Hasse


Hi Marek,

On 30.05.2017 11:37, Belisko Marek wrote:

Hi Jakob,

On Tue, May 30, 2017 at 11:28 AM, Jakob Hasse
 wrote:

Hi Marek,

please don't top post http://www.idallen.com/topposting.html :)

Thanks for your answer!
I did use a local repo folder since I find it more convenient to make quick
changes that way, as it is the case right now.

Source is fetched only once then it's keep in downloads directory so
better use then local repo.

I applied your changes but I still get the same bitbake errors as before, as
shown below. The CMake Error log says:
...
error: unrecognized command line option '-Wmissing-variable-declarations'
...
error: unrecognized command line option '-Wshorten-64-to-32'

Can you give me some more info about poky version, target you're building ...


Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "arm-dey-linux-gnueabi"
MACHINE   = "ccimx6ulstarter"
DISTRO= "dey"
DISTRO_VERSION= "2.2-r1"
TUNE_FEATURES = "arm armv7ve vfp thumb neon 
callconvention-hard   cortexa7"

TARGET_FPU= "hard"

We're using the digi embedded yocto here. I think I'll contact their 
support, too.

The arm-dey-linux-gnueabi looks like a normal arm-linux-gnueabi-gcc.
Please tell me if you think you need more info.

Cheers,
Jakob

--
Jakob Hasse
Software Developement

E: jakob.ha...@smart-home-technology.ch
T: +41 44 552 02 66

Smart Home Technology GmbH
www.smart-home-technology.ch

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

Re: [yocto] CMake project not building; building from local git repo possible

2017-05-30 Thread Belisko Marek

Hi Jakob,

On Tue, May 30, 2017 at 11:28 AM, Jakob Hasse
 wrote:
> Hi Marek,
please don't top post http://www.idallen.com/topposting.html :)
>
> Thanks for your answer!
> I did use a local repo folder since I find it more convenient to make quick
> changes that way, as it is the case right now.
Source is fetched only once then it's keep in downloads directory so
better use then local repo.
>
> I applied your changes but I still get the same bitbake errors as before, as
> shown below. The CMake Error log says:
> ...
> error: unrecognized command line option '-Wmissing-variable-declarations'
> ...
> error: unrecognized command line option '-Wshorten-64-to-32'
Can you give me some more info about poky version, target you're building ...
> ...
>
> I tried to coment out the addition of the corresponding flags (in
> cmake/CFlags.cmake) with no improvement.
>
> Now I compiled with another arm-gcc version (digi embedded version of
> arm-gcc, 6.2.0) and I get a different error -.- :
> | DEBUG: Executing python function sysroot_cleansstate
> | DEBUG: Python function sysroot_cleansstate finished
> | DEBUG: Executing shell function do_configure
> | CMake Error: The source directory
> "/home/jakob/workspace/newuvalue/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/stlink/0.1-r0/git"
> does not appear to contain CMakeLists.txt.
> | Specify --help for usage, or press the help button on the CMake GUI.
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_configure (log file is located at
> /home/jakob/workspace/newuvalue/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/stlink/0.1-r0/temp/log.do_configure.3539)
>
> I have no idea why, but in the original source folder the CMakeLists.txt is
> there...
>
> Cheers,
> Jakob
>
>
> On 29.05.2017 21:24, Belisko Marek wrote:
>>
>> Hi Jakob,
>>
>> On Mon, May 29, 2017 at 6:29 PM, Jakob Hasse
>>  wrote:
>>>
>>> Hello,
>>>
>>> I have two issues:
>>>
>>> 1.
>>> I innocently tried to include an open source version of the ST Link tools
>>> (https://github.com/texane/stlink) into my yocto image.
>>> I created a recipe fetching from git and got the error:
>>>
>>> | CMake Error at CMakeLists.txt:105 (install):
>>> |   install TARGETS given unknown argument "/lib".
>>> |
>>> |
>>> | CMake Error at CMakeLists.txt:135 (install):
>>> |   install TARGETS given unknown argument "/lib".
>>> |
>>> |
>>> | CMake Error at usr/lib/pkgconfig/CMakeLists.txt:12 (install):
>>> |   install FILES given unknown argument "/lib/pkgconfig/".
>>> |
>>> |
>>> | CMake Error at include/CMakeLists.txt:9 (install):
>>> |   install FILES given unknown argument "/lib".
>>> |
>>> |
>>> | CMake Error at include/CMakeLists.txt:12 (install):
>>> |   install FILES given unknown argument "/lib/stlink".
>>>
>>> I'm not sure whether it's a CMake problem since the project compiles
>>> absolutely fine on my host machine with native target (the binary also
>>> works
>>> fine in my case).
>>> Also, the CMake error log shows me errors about unrecognized CFlags
>>> (-Wmissing-variable-declarations, -Wshorten-64-to-32) which confuse me
>>> somewhat given the errors above.
>>> Then I checked out the source and changed the CMake file to exclude
>>> corresponding flags - with no difference, errors still remain.
>>> My recipe now looks like this:
>>>
>>> # comment
>>> SUMMARY = "ST-Link firmware flasher"
>>> DESCRIPTION = ""
>>> SECTION = "examples"
>>> LICENSE = "MIT"
>>> LIC_FILES_CHKSUM =
>>> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>>>
>>> DEPENDS = "libusb pkgconfig"
>>>
>>> SRC_URI = "file://stlink.tar.gz"
>>
>> Why don't use git protocol instead of link to fetched sources?
>>>
>>> FILES_${PN} += "${bindir}/st-flash"
>>>
>>> S = "${WORKDIR}/git"
>>
>> Here is my updated recipe:
>>
>> # comment
>> SUMMARY = "ST-Link firmware flasher"
>> DESCRIPTION = ""
>> SECTION = "examples"
>> LICENSE = "MIT"
>> LIC_FILES_CHKSUM =
>> "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>>
>> DEPENDS = "libusb pkgconfig"
>>
>> SRCREV = "55c057296ad15fa6de9909206098bd4eed8f6311"
>>
>> PV = "1.3.1+git${SRCPV}"
>>
>> SRC_URI = "git://github.com/texane/stlink.git"
>>
>> SRC_URI[md5sum] = "99fa2b1de041f62b7285a8f1870c891b"
>> SRC_URI[sha256sum] =
>> "8545752efe2be13c6dbadec48c93cd72be448147f38f0fe44050c0416827ca37"
>>
>> S = "${WORKDIR}/git"
>>
>> inherit cmake
>>
>> Also it is necessary to patch a stlink before to pass configuration phase
>> like:
>> diff --git a/CMakeLists.txt b/CMakeLists.txt
>> index afa7fde..4d2db6c 100644
>> --- a/CMakeLists.txt
>> +++ b/CMakeLists.txt
>> @@ -1,9 +1,10 @@
>>   cmake_minimum_required(VERSION 2.8.7)
>>   project(stlink C)
>> +SET(CMAKE_INSTALL_PREFIX /usr/)
>>   set(PROJECT_DESCRIPTION "Open source version of the
>> STMicroelectronics Stlink Tools")
>>   set(STLINK_UDEV_RULES_DIR "/etc/udev/rules.d" CACHE PATH "Udev rules
>> directory")
>>   set(STLINK_MODPROBED_DIR "/etc/modprobe.d" CACHE PATH "modprobe.d
>> directory")
>> -set(STLINK_LIBRARY_PATH "li

Re: [yocto] CMake project not building; building from local git repo possible

2017-05-30 Thread Jakob Hasse


Hi Marek,

Thanks for your answer!
I did use a local repo folder since I find it more convenient to make 
quick changes that way, as it is the case right now.


I applied your changes but I still get the same bitbake errors as 
before, as shown below. The CMake Error log says:

...
error: unrecognized command line option '-Wmissing-variable-declarations'
...
error: unrecognized command line option '-Wshorten-64-to-32'
...

I tried to coment out the addition of the corresponding flags (in 
cmake/CFlags.cmake) with no improvement.


Now I compiled with another arm-gcc version (digi embedded version of 
arm-gcc, 6.2.0) and I get a different error -.- :

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| CMake Error: The source directory 
"/home/jakob/workspace/newuvalue/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/stlink/0.1-r0/git" 
does not appear to contain CMakeLists.txt.

| Specify --help for usage, or press the help button on the CMake GUI.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/jakob/workspace/newuvalue/tmp/work/cortexa7hf-neon-dey-linux-gnueabi/stlink/0.1-r0/temp/log.do_configure.3539)


I have no idea why, but in the original source folder the CMakeLists.txt 
is there...


Cheers,
Jakob

On 29.05.2017 21:24, Belisko Marek wrote:

Hi Jakob,

On Mon, May 29, 2017 at 6:29 PM, Jakob Hasse
 wrote:

Hello,

I have two issues:

1.
I innocently tried to include an open source version of the ST Link tools
(https://github.com/texane/stlink) into my yocto image.
I created a recipe fetching from git and got the error:

| CMake Error at CMakeLists.txt:105 (install):
|   install TARGETS given unknown argument "/lib".
|
|
| CMake Error at CMakeLists.txt:135 (install):
|   install TARGETS given unknown argument "/lib".
|
|
| CMake Error at usr/lib/pkgconfig/CMakeLists.txt:12 (install):
|   install FILES given unknown argument "/lib/pkgconfig/".
|
|
| CMake Error at include/CMakeLists.txt:9 (install):
|   install FILES given unknown argument "/lib".
|
|
| CMake Error at include/CMakeLists.txt:12 (install):
|   install FILES given unknown argument "/lib/stlink".

I'm not sure whether it's a CMake problem since the project compiles
absolutely fine on my host machine with native target (the binary also works
fine in my case).
Also, the CMake error log shows me errors about unrecognized CFlags
(-Wmissing-variable-declarations, -Wshorten-64-to-32) which confuse me
somewhat given the errors above.
Then I checked out the source and changed the CMake file to exclude
corresponding flags - with no difference, errors still remain.
My recipe now looks like this:

# comment
SUMMARY = "ST-Link firmware flasher"
DESCRIPTION = ""
SECTION = "examples"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

DEPENDS = "libusb pkgconfig"

SRC_URI = "file://stlink.tar.gz"

Why don't use git protocol instead of link to fetched sources?

FILES_${PN} += "${bindir}/st-flash"

S = "${WORKDIR}/git"

Here is my updated recipe:

# comment
SUMMARY = "ST-Link firmware flasher"
DESCRIPTION = ""
SECTION = "examples"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

DEPENDS = "libusb pkgconfig"

SRCREV = "55c057296ad15fa6de9909206098bd4eed8f6311"

PV = "1.3.1+git${SRCPV}"

SRC_URI = "git://github.com/texane/stlink.git"

SRC_URI[md5sum] = "99fa2b1de041f62b7285a8f1870c891b"
SRC_URI[sha256sum] =
"8545752efe2be13c6dbadec48c93cd72be448147f38f0fe44050c0416827ca37"

S = "${WORKDIR}/git"

inherit cmake

Also it is necessary to patch a stlink before to pass configuration phase like:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index afa7fde..4d2db6c 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1,9 +1,10 @@
  cmake_minimum_required(VERSION 2.8.7)
  project(stlink C)
+SET(CMAKE_INSTALL_PREFIX /usr/)
  set(PROJECT_DESCRIPTION "Open source version of the
STMicroelectronics Stlink Tools")
  set(STLINK_UDEV_RULES_DIR "/etc/udev/rules.d" CACHE PATH "Udev rules
directory")
  set(STLINK_MODPROBED_DIR "/etc/modprobe.d" CACHE PATH "modprobe.d directory")
-set(STLINK_LIBRARY_PATH "lib/${CMAKE_LIBRARY_PATH}" CACHE PATH
"Target lib directory")
+set(STLINK_LIBRARY_PATH "${CMAKE_INSTALL_PREFIX}/lib" CACHE PATH
"Target lib directory")

  option(STLINK_GENERATE_MANPAGES "Generate manpages with pandoc" OFF)

diff --git a/include/CMakeLists.txt b/include/CMakeLists.txt
index 0b5a443..e0851e4 100644
--- a/include/CMakeLists.txt
+++ b/include/CMakeLists.txt
@@ -2,13 +2,16 @@ configure_file(
 "${PROJECT_SOURCE_DIR}/include/stlink/version.h.in"
 "${CMAKE_BINARY_DIR}/include/stlink/version.h"
  )
+
+SET(CMAKE_INSTALL_PREFIX /usr/)
+
  file(GLOB STLINK_HEADERS
 "stlink/*.h"
 "${CMAKE_BINARY_DIR}/include/stlink/*.h"
  )
  install(FILES ${CMAKE_SOURCE_DIR}/incl

[yocto] [meta-cgl][PATCH 3/3] cluster-glue: update useradd parameters

[yocto] [meta-cgl][PATCH 2/3] cluster-glue: fix the licenses

[yocto] [meta-cgl][PATCH 0/3] cluster-glue: several fixes

[yocto] [meta-cgl][PATCH 1/3] cluster-glue: inherit systemd

Re: [yocto] (no subject)

[yocto] [meta-cgl][PATCH] openipmi: remove the bbappend

Re: [yocto] Kernel config fragments ignored

Re: [yocto] Kernel config fragments ignored

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] (no subject)

[yocto] [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

[yocto] Yocto Project Status WW22’17

Re: [yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

Re: [yocto] Include meta-qt5 in an eSDK build ?

Re: [yocto] How to install dbg package and not its dependencies?

[yocto] Show cmake warnings as yocto warnings

Re: [yocto] CMake project not building; building from local git repo possible

[yocto] [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV

Re: [yocto] CMake project not building; building from local git repo possible

Re: [yocto] CMake project not building; building from local git repo possible

Re: [yocto] CMake project not building; building from local git repo possible

29 matches

Site Navigation

Mail list logo

Footer information