Re: [yocto] BBMASK issue
On Mon, Aug 22, 2016 at 6:50 PM, Takashi Matsuzawa wrote: > Hello Yocto. > > Now I am trying to customize an existing BSP to my need. > For this, I am adding following to my local.conf so that some of the recipes > in the BSP to be ignored. > > (local.conf) > BBMASK = "aaa|bbb|ccc" > BBMASK .= "|ddd|eee" > > However, it does not work since BSP itself has lines like below in its > layer. > > (somelayer.conf) > BBMASK = "xxx|yyy|xxx" > > The BSP definition of BBMASK seems to be overwriting my BBMASK definition in > my local.conf. > I wonder what is the best way so that the both definition are effective. > > I confirmed modifying BSP's definition as below works, but not sure if this > can be recommended as practice to everyone who provides layers for their > BSPs. > > BBMASK .= "|xxx|yyy|xxx" This isn't safe. It will only work if a default value for BBMASK is set elsewhere. If not, then you end up with a BBMASK which begins with "|", which effectively masks _every_ recipe. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] 答复: How to run a runqemu with intel-corei7-64?
Thanks. I was working on the qemux86-64 machine, but some test should be run on [intel-corei7-64] . I will try to use qemu. Best regards. On 19 August 2016 at 02:50, Richard Zhang mailto:richard.zh...@pica8.com>> wrote: After built an ‘intel-corei7-64’ image with Toaster, I try to run a runqemu, it can’t run. ERROR: unable to classify arg [intel-corei7-64]. Does intel-corei7-64 could be run with runqemu? Currently, not out of the box, although it should be possible if you run qemu directly. There is work ongoing to allow BSPs to extend runqemu so this could work, but for now if you wish to run images in qemu frequently then it's recommended to use the qemux86-64 machine, as it will include a few pieces (kernel modules, graphics drivers, etc) which increase performance inside qemu. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] BBMASK issue
On Mon, Aug 22, 2016 at 6:50 PM, Takashi Matsuzawa wrote: > Hello Yocto. > > Now I am trying to customize an existing BSP to my need. > For this, I am adding following to my local.conf so that some of the recipes > in the BSP to be ignored. > > (local.conf) > BBMASK = "aaa|bbb|ccc" > BBMASK .= "|ddd|eee" > > However, it does not work since BSP itself has lines like below in its > layer. > > (somelayer.conf) > BBMASK = "xxx|yyy|xxx" > > The BSP definition of BBMASK seems to be overwriting my BBMASK definition in > my local.conf. > I wonder what is the best way so that the both definition are effective. You can enforce it with something like BBMASK_forcevariable = "aaa|bbb|ccc" BBMASK_append = "|ddd|eee" However, I would suggest that BSP layer should append and not override as it seems to be doing. Otherwise it will be hard for that BSP to adapt. > > I confirmed modifying BSP's definition as below works, but not sure if this > can be recommended as practice to everyone who provides layers for their > BSPs. > > BBMASK .= "|xxx|yyy|xxx" > > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] BBMASK issue
Hello Yocto. Now I am trying to customize an existing BSP to my need. For this, I am adding following to my local.conf so that some of the recipes in the BSP to be ignored. (local.conf) BBMASK = "aaa|bbb|ccc" BBMASK .= "|ddd|eee" However, it does not work since BSP itself has lines like below in its layer. (somelayer.conf) BBMASK = "xxx|yyy|xxx" The BSP definition of BBMASK seems to be overwriting my BBMASK definition in my local.conf. I wonder what is the best way so that the both definition are effective. I confirmed modifying BSP's definition as below works, but not sure if this can be recommended as practice to everyone who provides layers for their BSPs. BBMASK .= "|xxx|yyy|xxx" -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-qt4][PATCH 1/2] qt4-embedded.inc: provide PACKAGECONFIG for tslib
On 19 August 2016 at 09:42, Maxin B. John wrote: > (A quick grep in meta-qt4 for PACKAGECONFIG_CONFARGS returned zero results) > FWIW it's a relatively new feature: when PACKAGECONFIG is evaluated it writes the enabled/disabled values to PACKAGECONFIG_CONFARGS, which classes can then use to set the relevant variable. For now it also sets EXTRA_OECONF but that was meant to be changed now that we're unfrozen. Martin, would you be able to write and test the change to remove EXTRA_OECONF from the PACKAGECONFIG handling? Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] eSDK errors and sstate signature issues
Hi Manju, Sorry for the delayed reply. On Mon, 15 Aug 2016 17:43:23 Manjukumar Harthikote Matha wrote: > I am trying to build Yocto eSDK with OE_core and meta-xilinx layers. > > Having issues while extracting the eSDK, it warns quite a bit on > signature mismatch. Can this happen due to the fact that I am using > external tool chain?? > > And eventually bails stating > ERROR: Unexpected tasks or setscene left over to be executed: > > meta-xilinx/recipes-kernel/linux/linux-xlnx_4.6.bb, do_fetch > meta-xilinx/recipes-kernel/linux/linux-xlnx_4.6.bb, do_unpack > meta-xilinx/recipes-kernel/linux/linux-xlnx_4.6.bb, do_kernel_configme > > > How do I go about investigating why set scene was corrupted or not > executed correctly while building kernel? So it looks like linux-xlnx is attempting to build for some reason and yet we don't expect it to be because it's locked. It may or may not be related to the use of an external toolchain - I'm not sure because it's not a scenario I have tested. Are the layers / toolchain you are using downloadable, i.e. could I reproduce the issue here? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [psplash][PATCH] psplash: add option to read startup message from file
Hi Richard, Sorry, we've clearly not been good at responding to this. I'm actually not sure who is maintaining psplash these days - Jussi/Ross, is it one of you? Cheers, Paul On Thu, 18 Aug 2016 09:09:30 Richard Leitner wrote: > Any comments/news on that patch from APRIL? > > On 04/15/2016 10:49 AM, Richard Leitner wrote: > > This patch adds an option to read the displayed message from a file. > > Additionally the maximum length for the read string can be defined. > > If both, a message (STARTUP_MSG) and a file (STARTUP_MSG_FILE) are > > defined the content of the file will be appended to the message. > > The string will be cutted after the given maximum number of chars. > > > > For these changes the following defines were introduced: > > PSPLASH_STARTUP_MSG_MAX_LEN ... maximum lenght of the complete message > > PSPLASH_STARTUP_MSG_FILE .. path to the file to read > > > > Signed-off-by: Richard Leitner -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Failing EXTERNALSRC and dangling symlinks
Hi Svein,
On Mon, 22 Aug 2016 11:57:16 Svein Seldal wrote:
> I am running on a customized Yocto tree based off Poky krogoth and I
> think I have stumbled upon a bug in bb.
>
> One of our recipes use EXTERNALSRC and EXTERNALSRC_BUILD, set from
> local.conf. When the recipe is built, two symlinks
> ${EXTERNALSRC}/oe-logs and ${EXTERNALSRC}/oe-workdir is created in the
> source tree.
>
> If the build output tmp/ later is deleted, these two symlinks becomes
> dangling links. Re-running bitbake will cause it to fail. First it warns
> of this during parsing, and later it will crash bb (see below).
>
> Removing these symlinks when deleting tmp/ ensures bitbake will not crash.
>
> I suppose this is a bug?
It is - it should be fixed by this patch:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2a849e7e9be6040bd76b76c24263f63f8f693753
Could you apply this and check if it fixes the issue? If so we'll backport it.
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-mingw with latest Yocto
I'm having trouble to build my project with meta-mingw. It looks like the
current master branch is too old to build with Yocto 2.1. So I changed
little bit such as,
Changed file names
binutils-cross-canadian_2.25%.bbappend to
binutils-cross-canadian_2.26%.bbappend
gmp_6.0.0.bbappend to gmp_6.1.0.bbappend
Added a line at x86_64-mingw32.conf
PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial =
"nativesdk-mingw-w64-runtime"
Added BBCLASSEXTEND="nativesdk" for gdb, lttng, and liburcu
But I'm still facing errors.
configure: error: Configuration x86_64-pokysdk-mingw32 is unsupported.
When it builds
x86_64-nativesdk-mingw32-pokysdk-mingw32/nativesdk-gcc-runtime/5.3.0-r0
Anyone using meta-mingw on Yocto 2.1 resolved this issue?
p.s. - I'm using uclibc for the target image. Is this can be the reason of
the error?
Thanks,
*- Austin*
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH v2] PublishArtifacts.py: fix filecheck to work under dash (or other POSIX shell)
On Mon, 2016-08-22 at 07:52 -0700, Bill Randle wrote:
> An earlier patch (ed3857990) to check for existing msd5sum files
> worked
> fine when tested under bash, but failed with an error message about
> [[
> not found when run under dash. Updated the test to not rely on
> bashisms.
Pushed to master, thanks!
Joshua
>
> Signed-off-by: Bill Randle
> ---
>
> V2: use POSIX shell expansion for simplified test (thanks Joshua)
>
> lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> index d8b554f..e738521 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> @@ -260,7 +260,7 @@ class PublishArtifacts(ShellCommand):
> cmd = ""
> if os.environ.get('GEN_IMG_MD5') == "True":
> cmd += "for x in `find " + deploy_dir + " -maxdepth 5
> -type f`;"
> -cmd += "do if [[ $x != *.md5sum ]]; then md5sum $x >> "
> + "$x.md5sum; fi; done;"
> +cmd += "do if [ ${x##*.} != md5sum ]; then md5sum $x >>
> " + "$x.md5sum; fi; done;"
> return cmd
>
> def getDeployNames(self, artifact, buildername):
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-autobuilder][PATCH v2] PublishArtifacts.py: fix filecheck to work under dash (or other POSIX shell)
An earlier patch (ed3857990) to check for existing msd5sum files worked
fine when tested under bash, but failed with an error message about [[
not found when run under dash. Updated the test to not rely on bashisms.
Signed-off-by: Bill Randle
---
V2: use POSIX shell expansion for simplified test (thanks Joshua)
lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py
b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py
index d8b554f..e738521 100644
--- a/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py
+++ b/lib/python2.7/site-packages/autobuilder/buildsteps/PublishArtifacts.py
@@ -260,7 +260,7 @@ class PublishArtifacts(ShellCommand):
cmd = ""
if os.environ.get('GEN_IMG_MD5') == "True":
cmd += "for x in `find " + deploy_dir + " -maxdepth 5 -type f`;"
-cmd += "do if [[ $x != *.md5sum ]]; then md5sum $x >> " +
"$x.md5sum; fi; done;"
+cmd += "do if [ ${x##*.} != md5sum ]; then md5sum $x >> " +
"$x.md5sum; fi; done;"
return cmd
def getDeployNames(self, artifact, buildername):
--
2.5.5
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: fix file check to work under dash
On Mon, 2016-08-22 at 11:28 +0100, Joshua Lock wrote:
On Sat, 2016-08-20 at 15:50 -0700, Bill Randle wrote:
An earlier patch (ed3857990) to check for existing msd5sum files
worked
fine when tested under bash, but failed with an error message about
[[
not found when run under dash. Updated the test to not rely on
bashisms.
Signed-off-by: Bill Randle
mailto:william.c.ran...@intel.com>>
---
lib/python2.7/site-
packages/autobuilder/buildsteps/PublishArtifacts.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/python2.7/site-
packages/autobuilder/buildsteps/PublishArtifacts.py
b/lib/python2.7/site-
packages/autobuilder/buildsteps/PublishArtifacts.py
index d8b554f..58048f0 100644
--- a/lib/python2.7/site-
packages/autobuilder/buildsteps/PublishArtifacts.py
+++ b/lib/python2.7/site-
packages/autobuilder/buildsteps/PublishArtifacts.py
@@ -259,8 +259,9 @@ class PublishArtifacts(ShellCommand):
def generateMD5cmd(self, artifact, deploy_dir):
cmd = ""
if os.environ.get('GEN_IMG_MD5') == "True":
+# crufty test for existing md5sum file required for dash
shell
cmd += "for x in `find " + deploy_dir + " -maxdepth 5
-type f`;"
-cmd += "do if [[ $x != *.md5sum ]]; then md5sum $x >> "
+ "$x.md5sum; fi; done;"
+cmd += "do echo ${x} | grep -q '\.md5sum'; if [ $? -ne 0
]; then md5sum $x >> " + "$x.md5sum; fi; done;"
return cmd
Rather than a "crufty" test, how about using POSIX sh parameter
expansion, i.e.
$ foo="blah.bar"
$ if [ ${foo##*.} == bar ]; then echo "bar!"; fi
bar!
Therefore, the patch would be something like (untested):
cmd += "if [ ${x##*.} == .md5sum ]; then md5sum $x >> $x.md5sum; fi"
Regards,
Joshua
Good suggestion! The correct (tested) patch would be:
if [ ${x##*.} != md5sum ]; then md5sum $x >> $x.md5sum; fi"
Updated patch coming shortly.
-Bill
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to run a runqemu with intel-corei7-64?
On 19 August 2016 at 02:50, Richard Zhang wrote: > After built an ‘intel-corei7-64’ image with Toaster, I try to run a > runqemu, it can’t run. > > ERROR: unable to classify arg [intel-corei7-64]. > > Does intel-corei7-64 could be run with runqemu? > > Currently, not out of the box, although it should be possible if you run qemu directly. There is work ongoing to allow BSPs to extend runqemu so this could work, but for now if you wish to run images in qemu frequently then it's recommended to use the qemux86-64 machine, as it will include a few pieces (kernel modules, graphics drivers, etc) which increase performance inside qemu. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 5/5] refpolicy_common.inc: add refpolicy minimum banner at selinux config.
From: Shrikant Bobade
Signed-off-by: Shrikant Bobade
---
recipes-security/refpolicy/refpolicy_common.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-security/refpolicy/refpolicy_common.inc
b/recipes-security/refpolicy/refpolicy_common.inc
index e1eac50..a9dc466 100644
--- a/recipes-security/refpolicy/refpolicy_common.inc
+++ b/recipes-security/refpolicy/refpolicy_common.inc
@@ -158,6 +158,7 @@ install_config () {
# disabled - No SELinux policy is loaded.
SELINUX=${DEFAULT_ENFORCING}
# SELINUXTYPE= can take one of these values:
+# minimum - Minimum Security protection.
# standard - Standard Security protection.
# mls - Multi Level Security protection.
# targeted - Targeted processes are protected.
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 4/5] selinux-labeldev: add systemd service file support
From: Shrikant Bobade
add systemd service file for handling selinux labeldev, this change improves
handling of systemd service functionality like:status check, debug etc.
compared to sysvinit compatibility mode scripts.
Signed-off-by: Shrikant Bobade
---
.../selinux/selinux-labeldev/selinux-labeldev.service | 11 +++
recipes-security/selinux/selinux-labeldev_0.1.bb | 5 -
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644
recipes-security/selinux/selinux-labeldev/selinux-labeldev.service
diff --git a/recipes-security/selinux/selinux-labeldev/selinux-labeldev.service
b/recipes-security/selinux/selinux-labeldev/selinux-labeldev.service
new file mode 100644
index 000..d45ecbc
--- /dev/null
+++ b/recipes-security/selinux/selinux-labeldev/selinux-labeldev.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=SELinux init for /dev service loading
+DefaultDependencies=no
+Before=sysinit.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/selinux-labeldev.sh
+
+[Install]
+WantedBy=multi-user.target
diff --git a/recipes-security/selinux/selinux-labeldev_0.1.bb
b/recipes-security/selinux/selinux-labeldev_0.1.bb
index b692bb2..8eb5db4 100644
--- a/recipes-security/selinux/selinux-labeldev_0.1.bb
+++ b/recipes-security/selinux/selinux-labeldev_0.1.bb
@@ -10,7 +10,10 @@ ${PN}_RDEPENDS = " \
policycoreutils-setfiles \
"
-SRC_URI = "file://${BPN}.sh"
+SRC_URI = "file://${BPN}.sh \
+ file://${BPN}.service \
+ "
+
SELINUX_SCRIPT_DST = "0${BPN}"
require selinux-initsh.inc
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 3/5] selinux-autorelabel: add systemd service file support
From: Shrikant Bobade
add systemd service file for handling selinux autorelabel, this change
improves handling of systemd service functionality like:status check,
re-run, debug etc. compared to sysvinit compatibility mode scripts.
Signed-off-by: Shrikant Bobade
---
.../selinux/selinux-autorelabel/selinux-autorelabel.service | 11 +++
recipes-security/selinux/selinux-autorelabel_0.1.bb | 5 -
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644
recipes-security/selinux/selinux-autorelabel/selinux-autorelabel.service
diff --git
a/recipes-security/selinux/selinux-autorelabel/selinux-autorelabel.service
b/recipes-security/selinux/selinux-autorelabel/selinux-autorelabel.service
new file mode 100644
index 000..9520f6e
--- /dev/null
+++ b/recipes-security/selinux/selinux-autorelabel/selinux-autorelabel.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=SELinux autorelabel service loading
+DefaultDependencies=no
+Before=sysinit.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/selinux-autorelabel.sh
+
+[Install]
+WantedBy=multi-user.target
diff --git a/recipes-security/selinux/selinux-autorelabel_0.1.bb
b/recipes-security/selinux/selinux-autorelabel_0.1.bb
index 2664863..4eb2b4e 100644
--- a/recipes-security/selinux/selinux-autorelabel_0.1.bb
+++ b/recipes-security/selinux/selinux-autorelabel_0.1.bb
@@ -11,7 +11,10 @@ ${PN}_RDEPENDS = " \
policycoreutils-setfiles \
"
-SRC_URI = "file://${BPN}.sh"
+SRC_URI = "file://${BPN}.sh \
+ file://${BPN}.service \
+ "
+
INITSCRIPT_PARAMS = "start 01 S ."
require selinux-initsh.inc
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 2/5] selinux-init: add systemd service file support
From: Shrikant Bobade
add systemd service file for handling selinux initialization, this change
improves handling of systemd service functionality like:status check, debug
etc. compared to sysvinit compatibility mode scripts.
Signed-off-by: Shrikant Bobade
---
recipes-security/selinux/selinux-init/selinux-init.service | 11 +++
recipes-security/selinux/selinux-init_0.1.bb | 5 -
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 recipes-security/selinux/selinux-init/selinux-init.service
diff --git a/recipes-security/selinux/selinux-init/selinux-init.service
b/recipes-security/selinux/selinux-init/selinux-init.service
new file mode 100644
index 000..93cc6ce
--- /dev/null
+++ b/recipes-security/selinux/selinux-init/selinux-init.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=SELinux init service loading
+DefaultDependencies=no
+Before=sysinit.target
+
+[Service]
+Type=oneshot
+ExecStart=/usr/bin/selinux-init.sh
+
+[Install]
+WantedBy=multi-user.target
diff --git a/recipes-security/selinux/selinux-init_0.1.bb
b/recipes-security/selinux/selinux-init_0.1.bb
index 54932e8..38b5900 100644
--- a/recipes-security/selinux/selinux-init_0.1.bb
+++ b/recipes-security/selinux/selinux-init_0.1.bb
@@ -14,7 +14,10 @@ ${PN}_RDEPENDS = " \
policycoreutils-setfiles \
"
-SRC_URI = "file://${BPN}.sh"
+SRC_URI = "file://${BPN}.sh \
+ file://${BPN}.service \
+ "
+
INITSCRIPT_PARAMS = "start 01 S ."
require selinux-initsh.inc
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-selinux][PATCH 1/5] selinux-initsh.inc: add systemd support
From: Shrikant Bobade
add support for systemd service file and handling of script required by
systemd service file.
Signed-off-by: Shrikant Bobade
---
recipes-security/selinux/selinux-initsh.inc | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/recipes-security/selinux/selinux-initsh.inc
b/recipes-security/selinux/selinux-initsh.inc
index f7348bb..bcdd449 100644
--- a/recipes-security/selinux/selinux-initsh.inc
+++ b/recipes-security/selinux/selinux-initsh.inc
@@ -13,11 +13,21 @@ CONFFILES_${PN} +=
"${sysconfdir}/init.d/${SELINUX_SCRIPT_DST}"
PACKAGE_ARCH ?= "${MACHINE_ARCH}"
-inherit update-rc.d
+inherit update-rc.d systemd
+
+SYSTEMD_SERVICE_${PN} = "${SELINUX_SCRIPT_SRC}.service"
do_install () {
install -d ${D}${sysconfdir}/init.d/
install -m 0755 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.sh
${D}${sysconfdir}/init.d/${SELINUX_SCRIPT_DST}
+
+ install -d ${D}${systemd_unitdir}/system
+ install -m 0644 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.service
${D}${systemd_unitdir}/system
+
+ if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false',
d)}; then
+ install -d ${D}${bindir}
+ install -m 0755 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.sh
${D}${bindir}
+ fi
}
sysroot_stage_all_append () {
--
1.9.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] nightly-wic.conf: add build for qemux86
On Fri, 2016-08-19 at 10:53 -0700, Bill Randle wrote:
> [YOCTO #10166]
Pushed to master, thanks.
Joshua
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly-wic.conf | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/buildset-config.controller/nightly-wic.conf b/buildset-
> config.controller/nightly-wic.conf
> index 47565ba..59ea34c 100644
> --- a/buildset-config.controller/nightly-wic.conf
> +++ b/buildset-config.controller/nightly-wic.conf
> @@ -9,6 +9,12 @@ steps: [{'SetDest':{}},
> {'RunPreamble':{}},
> {'GetDistroVersion':{'distro': 'poky'}},
> {'CreateBBLayersConf':{'buildprovider':'yocto'}},
> +{'CreateAutoConf':{'machine':'qemux86'}},
> +{'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> +{'BuildImages':{'images':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'directdisk',
> 'target_img':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'directdisk-gpt',
> 'target_img':'core-image-sato'}},
> +{'CreateWicImages':{'wic_img_type':'mkefidisk',
> 'target_img':'core-image-sato'}},
> {'CreateAutoConf':{'machine':'genericx86'}},
> {'BuildImages':{'images':'syslinux syslinux-native parted-
> native gptfdisk-native dosfstools-native mtools-native'}},
> {'BuildImages':{'images':'core-image-sato'}},
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] add support for building the eclipse-poky-neon plugin
On Fri, 2016-08-19 at 12:04 -0700, Bill Randle wrote:
> Add configs to build the eclipse poky neon plugin and drop support
> for the
> kepler branch. Also, generate md5sums for the eclipse plugin
> artifacts.
> (Note: building neon requires java 1.8.0.)
>
> [YOCTO #9940]
Pushed to master, thanks.
Joshua
>
> Signed-off-by: Bill Randle
> ---
> buildset-config.controller/nightly.conf | 6 +-
>
> buildset-config.controller/eclipse-plugin-neon.conf | 11
> +++
> buildset-config.controller/yoctoAB.conf | 4
> ++--
> .../site-packages/autobuilder/buildsteps/PublishArtifacts.py | 11
> ---
> 4 files changed, 26 insertions(+), 10 deletions(-)
> create mode 100644 buildset-config.controller/eclipse-plugin-
> neon.conf
>
> diff --git a/buildset-config.controller/nightly.conf b/buildset-
> config.controller/nightly.conf
> index c16c147..0f9dd4e 100644
> --- a/buildset-config.controller/nightly.conf
> +++ b/buildset-config.controller/nightly.conf
> @@ -23,14 +23,14 @@
> {'repourl':'git://git.yoctoproject.org/eclipse-poky',
> 'checkout':False,
> 'branch':'luna-master'}},
> -{'eclipse-poky-kepler':
> -{'repourl':'git://git.yoctoproject.org/eclipse-poky',
> - 'checkout':False,
> - 'branch':'kepler-master'}},
> {'eclipse-poky-mars':
> {'repourl':'git://git.yoctoproject.org/eclipse-poky',
> 'checkout':False,
> 'branch':'mars-master'}},
> +{'eclipse-poky-neon':
> +{'repourl':'git://git.yoctoproject.org/eclipse-poky',
> + 'checkout':False,
> + 'branch':'neon-master'}},
> {'meta-qt4':
> {'repourl':'git://git.yoctoproject.org/meta-qt4',
> 'branch':'master'}},
> @@ -103,7 +103,7 @@
> 'nightly-mips64': {}, 'nightly-arm64':
> {},
> 'nightly-rpm-non-rpm': {}, 'nightly-deb-
> non-deb': {}},
> 'schedulerNames_nowait' : {'nightly-
> uclibc':{}, 'build-appliance': {},
> - 'eclipse-plugin-kepler': {}, 'eclipse-
> plugin-mars': {},
> + 'eclipse-plugin-neon': {}, 'eclipse-
> plugin-mars': {},
> 'eclipse-plugin-luna': {}, 'nightly-non-
> gpl3': {},
> 'nightly-oecore': {}, 'nightly-
> world':{},'nightly-wic':{},
> 'nightly-world-lsb':{}, 'nightly-intel-
> gpl': {},
>
> diff --git a/buildset-config.controller/yoctoAB.conf b/buildset-
> config.controller/yoctoAB.conf
> index 0f9ba0c..fe9750b 100644
> --- a/buildset-config.controller/yoctoAB.conf
> +++ b/buildset-config.controller/yoctoAB.conf
> @@ -1,6 +1,6 @@
> [BuildSets]
> -order: ['nightly', 'eclipse-plugin-mars',
> -'eclipse-plugin-kepler', 'eclipse-plugin-luna',
> +order: ['nightly', 'eclipse-plugin-neon', 'eclipse-plugin-mars',
> +'eclipse-plugin-luna',
> 'nightly-arm', 'nightly-arm64', 'nightly-arm-lsb',
> 'nightly-mips', 'nightly-mips64', 'nightly-mips-lsb',
> 'nightly-ppc', 'nightly-ppc-lsb', 'nightly-no-x11',
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> index 1a938fc..d8b554f 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> @@ -96,10 +96,15 @@ class PublishArtifacts(ShellCommand):
> command=command+"mv " + adt_dev_dest +
> "/rootfs/qemux86-64 " + adt_dev_dest + "/rootfs/qemux86_64;"
> elif "eclipse-plugin" in artifact:
> artifact_base = artifact.replace("eclipse-
> plugin-", "")
> +deploy_dir =
> os.path.join(os.path.join(self.workerdir, buildername),
> "build/scripts")
> +# create md5sums only for the zip files
> +if os.environ.get('GEN_IMG_MD5') == "True":
> +command += "for x in `ls " + deploy_dir +
> "/*.zip`;"
> +command += "do md5sum $x >> " + "$x.md5sum;
> done;"
> command=command+"mkdir -p " + DEST + "/eclipse-
> plugin/"+ artifact_base +";"
> -command=command+"cp -R --no-dereference --
> preserve=links " + \
> - os.path.join(os.path.join(self.
> workerdir, buildername),
> - "build/scripts/org.
> *.zip") + \
> +command=command+"cp --no-dereference --
> preserve=links " + \
> + os.path.join(deploy_dir,
> "org.*.zip") + \
> + " " + os.path.join(deploy_dir,
> "org.*.md5sum") + \
>
Re: [yocto] [yocto-autobuilder][PATCH] SendQAEmail.py: cleanup email formatting
On Fri, 2016-08-19 at 09:27 -0700, Bill Randle wrote: > "-e" option is not required and gets inserted into email text if > present. Pushed to master, thanks. Joshua > > Signed-off-by: Bill Randle > --- > lib/python2.7/site-packages/autobuilder/buildsteps/SendQAEmail.py | > 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/python2.7/site- > packages/autobuilder/buildsteps/SendQAEmail.py b/lib/python2.7/site- > packages/autobuilder/buildsteps/SendQAEmail.py > index 3691cc6..1bb2893 100644 > --- a/lib/python2.7/site- > packages/autobuilder/buildsteps/SendQAEmail.py > +++ b/lib/python2.7/site- > packages/autobuilder/buildsteps/SendQAEmail.py > @@ -95,7 +95,7 @@ Please begin QA on this build as soon as > possible.''' % (rel_name, self.getPrope > > email_header += "Subject: " + mailsubject + "\n" > > -mailcmd = 'echo -e "' + email_header + "\n" + email_base > + '\n' + email_body + '\n' + mailsig + ' " | sendmail -t' > +mailcmd = 'echo "' + email_header + "\n" + email_base + > '\n' + email_body + '\n' + mailsig + ' " | sendmail -t' > > self.command = mailcmd > else: -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH v2] enable use of kvm with qemux86*
On Wed, 2016-08-17 at 18:49 -0700, Bill Randle wrote:
> When used with corresponding oe-core patch, this will enable the use
> of kvm when running qemux86* images on a x86* host that supports kvm.
> On the same build machine, for an x86_64 testimage run, the with and
> without times are:
> without kvm:
> core-image-sato-1.0-r0 do_testimage: Ran 43 tests in 728.726s
> core-image-sato-sdk-1.0-r0 do_testimage: Ran 52 tests in
> 1090.838s
> with kvm:
> core-image-sato-1.0-r0 do_testimage: Ran 43 tests in 60.255s
> core-image-sato-sdk-1.0-r0 do_testimage: Ran 52 tests in 71.719s
>
> [YOCTO #9298]
Pushed to master, thanks.
Joshua
>
> Signed-off-by: Bill Randle
> ---
>
> Change for v2: propagate the new variable to the workers.
>
> config/autobuilder.conf.example | 3 +++
> lib/python2.7/site-packages/autobuilder/buildsteps/CreateAutoConf.py
> | 2 ++
> 2 files changed, 5 insertions(+)
>
> diff --git a/config/autobuilder.conf.example
> b/config/autobuilder.conf.example
> index 9179d14..96bc4c6 100644
> --- a/config/autobuilder.conf.example
> +++ b/config/autobuilder.conf.example
> @@ -60,6 +60,9 @@ RESOLVE_TRIGGERED_HEAD = True
> DEVKERNEL_MUT_REPO = "{'git://git.yoctoproject.org/poky-
> contrib':['stage/master_under_test', 'sgw/mut']}"
> DEVKERNEL = "linux-yocto-dev"
>
> +[TestSettings]
> +QEMU_USE_KVM = "True"
> +
> [ADTREPO Settings]
> ADTREPO_POPULATE = False
> ADTREPO_DEV_POPULATE = True
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> b/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> index 8817d69..2b086e1 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/CreateAutoConf.py
> @@ -264,6 +264,8 @@ class CreateAutoConf(ShellCommand):
> if self.initmgr == "sysvinit systemd":
> fout = fout + 'DISTRO_FEATURES_append = "
> systemd"\n'
> fout = fout + 'VIRTUAL-RUNTIME_init_manager =
> "sysvinit"\n'
> +if os.environ.get("QEMU_USE_KVM") == "True":
> +fout = fout + 'QEMU_USE_KVM = "True"\n'
> if self.atextappend:
> fout = fout + self.atextappend
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder][PATCH] PublishArtifacts.py: fix file check to work under dash
On Sat, 2016-08-20 at 15:50 -0700, Bill Randle wrote:
> An earlier patch (ed3857990) to check for existing msd5sum files
> worked
> fine when tested under bash, but failed with an error message about
> [[
> not found when run under dash. Updated the test to not rely on
> bashisms.
>
> Signed-off-by: Bill Randle
> ---
> lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> index d8b554f..58048f0 100644
> --- a/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> +++ b/lib/python2.7/site-
> packages/autobuilder/buildsteps/PublishArtifacts.py
> @@ -259,8 +259,9 @@ class PublishArtifacts(ShellCommand):
> def generateMD5cmd(self, artifact, deploy_dir):
> cmd = ""
> if os.environ.get('GEN_IMG_MD5') == "True":
> +# crufty test for existing md5sum file required for dash
> shell
> cmd += "for x in `find " + deploy_dir + " -maxdepth 5
> -type f`;"
> -cmd += "do if [[ $x != *.md5sum ]]; then md5sum $x >> "
> + "$x.md5sum; fi; done;"
> +cmd += "do echo ${x} | grep -q '\.md5sum'; if [ $? -ne 0
> ]; then md5sum $x >> " + "$x.md5sum; fi; done;"
> return cmd
Rather than a "crufty" test, how about using POSIX sh parameter
expansion, i.e.
$ foo="blah.bar"
$ if [ ${foo##*.} == bar ]; then echo "bar!"; fi
bar!
Therefore, the patch would be something like (untested):
cmd += "if [ ${x##*.} == .md5sum ]; then md5sum $x >> $x.md5sum; fi"
Regards,
Joshua
>
> def getDeployNames(self, artifact, buildername):
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Failing EXTERNALSRC and dangling symlinks
I am running on a customized Yocto tree based off Poky krogoth and I
think I have stumbled upon a bug in bb.
One of our recipes use EXTERNALSRC and EXTERNALSRC_BUILD, set from
local.conf. When the recipe is built, two symlinks
${EXTERNALSRC}/oe-logs and ${EXTERNALSRC}/oe-workdir is created in the
source tree.
If the build output tmp/ later is deleted, these two symlinks becomes
dangling links. Re-running bitbake will cause it to fail. First it warns
of this during parsing, and later it will crash bb (see below).
Removing these symlinks when deleting tmp/ ensures bitbake will not crash.
I suppose this is a bug?
Best regards,
Svein Seldal
(EXTERNALSRC="/srv/user/yocto/sp-core-image/src")
WARNING: Unable to get checksum for sp SRC_URI entry oe-logs: [Errno 2]
No such file or directory: '/home/user/yocto/sp-core-image/src/oe-logs'
WARNING: Unable to get checksum for sp SRC_URI entry oe-workdir: [Errno
2] No such file or directory:
'/home/user/yocto/sp-core-image/src/oe-workdir'
ERROR: sp-99.8.0-r0 do_compile: Build of do_compile failed
ERROR: sp-99.8.0-r0 do_compile: Traceback (most recent call last):
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/build.py", line
567, in exec_task
return _exec_task(fn, task, d, quieterr)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/build.py", line
541, in _exec_task
event.fire(TaskSucceeded(task, logfn, localdata), localdata)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/event.py", line
171, in fire
fire_class_handlers(event, d)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/event.py", line
110, in fire_class_handlers
execute_handler(name, handler, event, d)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/event.py", line
82, in execute_handler
ret = handler(event)
File
"/home/user/yocto/sp-core-image/src/poky/meta/classes/sstate.bbclass",
line 946, in sstate_eventhandler
bb.siggen.dump_this_task(sstatepkg + '_' + taskname + ".tgz"
".siginfo", d)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/siggen.py", line
348, in dump_this_task
bb.parse.siggen.dump_sigtask(fn, task, outfile, "customfile:" +
referencestamp)
File
"/home/user/yocto/sp-core-image/src/poky/meta/lib/oe/sstatesig.py", line
182, in dump_sigtask
super(bb.siggen.SignatureGeneratorBasicHash, self).dump_sigtask(fn,
task, stampbase, runtime)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/siggen.py", line
303, in dump_sigtask
computed_taskhash = calc_taskhash(data)
File
"/home/user/yocto/sp-core-image/src/poky/bitbake/lib/bb/siggen.py", line
548, in calc_taskhash
data = data + c[1]
TypeError: cannot concatenate 'str' and 'NoneType' objects
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] debug version of a package
On 21 August 2016 at 16:55, Andy Ng wrote: > Hi, > > How do I trigger the build of the debug version of a single package? > Binaries are (almost) always built with debug symbols, there's nothing that needs to be done there. The unstripped debug binaries are typically packaged into "-dbg" package, while stripped versions of those binaries go into other packages. To get debug binaries onto an image, you can either add the specific -dbg packages with IMAGE_INSTALL_append or add all debug packages with image features: EXTRA_IMAGE_FEATURES += "tools-debug dbg-pkgs" Jussi > Thank you > Andy > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
