Re: [yocto] meta-mono: breaking as libglade removed
On 31/03/2018 16:37, Andreas Müller wrote: On Fri, Mar 30, 2018 at 11:19 AM, Alex Lennon wrote: Hi, libglade seems to have been removed which is breaking meta-mono builds. What's best to fix this? Should I be adding the recipe into meta-mono? Thanks, Alex As the one who removed it - so feel responsible... 1.You could add libglade to meta-mono but I think there some additional dependencies which need to be added too 2. Checked configure script of gtk-sharp-2.12.45: Seems libglade is an optional dependency. I think it should be good enough to remove it from dependencies. My suggestion would be 2. Andreas Thanks Andreas. I've build successfully with option (2) and will keep an eye on it to see if anything breaks. Cheers! Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Custom image type and CONVERSION_CMD images softlink problem
Hi.
I am working with a project that has a custom image type, "sdimg". The
image works fine but it is when I try to apply CONVERSION_CMDs that I
see some interesting things.
The image output is:
${IMGDEPLOYDIR}/${IMAGE_NAME}.$suffix
There is also a soft-link:
ln -sfn "${IMAGE_NAME}.$suffix"
"${DEPLOY_DIR_IMAGE}/${IMAGE_BASENAME}-${MACHINE}.$suffix"
Now the interesting part comes when I try this:
IMAGE_FSTYPES += "sdimg.gz"
This results in a empty gz file, but I already know why and that is
because the "normal" image does not contain IMAGE_NAME_SUFFIX in the
output name, on which the CONVERSION_CMDs rely on [1].
So instead of changing the image name I was hoping that this should
work (default is ".rootfs" in image_types.bbclass):
IMAGE_NAME_SUFFIX_sdimg = ""
But above only partly works. It will generate a proper "gz" version of
"sdimg" but it fails to create a soft-link, that is
${IMAGE_BASENAME}-${MACHINE}.sdimg.gz -> ${IMAGE_NAME}.sdimg.gz. And I
have traced down on why. It is because image.bbclass still reads
IMAGE_NAME_SUFFIX as ".rootfs" in create_symlinks[2] even though I
have set it to something else for my specific image type (override).
I have a couple of workarounds for this already but still wanted to
report this and see what the community thinks about this. I would
expect what I am trying to do, to work. That is to set
IMAGE_NAME_SUFFIX to empty for the custom image.
But you might be of another opinion.
[1].
https://github.com/openembedded/openembedded-core/blob/master/meta/classes/image_types.bbclass#L284
[2].
https://github.com/openembedded/openembedded-core/blob/master/meta/classes/image.bbclass#L592-L614
--
Med Vänliga Hälsningar / Best Regards
Mirza Krak
email: mi...@mkrak.org
web: http://mkrak.org
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding other languages to yocto build
On 03/30/2018 07:42 AM, Srinivasan, Raja wrote: > friends, > > ? > > anyone using ada, objective c, c#, swift or any other such languages. if so > can you point me to a recipe. my interest is in the order listed. looking for > an alternative to C/C++ I searched the layer index[1] for "ada" and found https://github.com/Lucretia/meta-ada Be warned, the last commit is five years old, but hopefully it helps answer some of your questions. Philip [1] http://layers.openembedded.org > > > TIA > > srini > > > > CONFIDENTIALITY NOTICE: This email message and any attachments are > confidential and may be privileged and are meant to be read by the intended > recipient only. If you are not the intended recipient, please notify sender > immediately and destroy all copies of this message and any attachments > without reading or disclosing their contents. Thank you > > Disclaimer > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast Ltd, an innovator in Software as a Service > (SaaS) for business. Providing a safer and more useful place for your human > generated data. Specializing in; Security, archiving and compliance. To find > out more visit the Mimecast website. > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding other languages to yocto build
Thanks a bunch. srini -Original Message- From: Philip Balister [mailto:phi...@balister.org] Sent: Sunday, April 1, 2018 1:09 PM To: Srinivasan, Raja ; yocto@yoctoproject.org Subject: Re: [yocto] adding other languages to yocto build On 03/30/2018 07:42 AM, Srinivasan, Raja wrote: > friends, > > ? > > anyone using ada, objective c, c#, swift or any other such languages. > if so can you point me to a recipe. my interest is in the order > listed. looking for an alternative to C/C++ I searched the layer index[1] for "ada" and found https://github.com/Lucretia/meta-ada Be warned, the last commit is five years old, but hopefully it helps answer some of your questions. Philip [1] http://layers.openembedded.org > > > TIA > > srini > > > > CONFIDENTIALITY NOTICE: This email message and any attachments are > confidential and may be privileged and are meant to be read by the > intended recipient only. If you are not the intended recipient, please > notify sender immediately and destroy all copies of this message and > any attachments without reading or disclosing their contents. Thank > you > > Disclaimer > > The information contained in this communication from the sender is > confidential. It is intended solely for use by the recipient and others > authorized to receive it. If you are not the recipient, you are hereby > notified that any disclosure, copying, distribution or taking action in > relation of the contents of this information is strictly prohibited and may > be unlawful. > > This email has been scanned for viruses and malware, and may have been > automatically archived by Mimecast Ltd, an innovator in Software as a Service > (SaaS) for business. Providing a safer and more useful place for your human > generated data. Specializing in; Security, archiving and compliance. To find > out more visit the Mimecast website. > > > CONFIDENTIALITY NOTICE: This email message and any attachments are confidential and may be privileged and are meant to be read by the intended recipient only. If you are not the intended recipient, please notify sender immediately and destroy all copies of this message and any attachments without reading or disclosing their contents. Thank you Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi] Has anybody run VC4 + X + recent meta/masters lately
On Fri, Mar 30, 2018 at 6:45 AM, Andreas Müller wrote: > After party hangover: sddm and kde look horrible with this patch. > Should respect linear if requested explicitly - wonder if that slows > down horses... > Out of curiosity, are you going to follow up on this? Maybe with the mesa people? When I encountered this issue, my google-foo didn't yield anything. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/2] audit: fix pkgconfigdir
On 2018年03月28日 15:10, Anuj Mittal wrote:
Hi,
On 03/28/2018 02:55 PM, Kai Kang wrote:
Because 'libdir' is set with ${base_libdir} in recipe file of audit,
package config files(.pc) are installed to ${base_libdir}/pkgconfig that
variable pkgconfigdir is set with ${libdir}/pkgconfig in makefile.
Set pkgconfigdir directly to install .pc files to right directory.
Signed-off-by: Kai Kang
---
recipes-security/audit/audit_2.7.6.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes-security/audit/audit_2.7.6.bb
b/recipes-security/audit/audit_2.7.6.bb
index 5bfda7b..33b49c9 100644
--- a/recipes-security/audit/audit_2.7.6.bb
+++ b/recipes-security/audit/audit_2.7.6.bb
@@ -45,6 +45,7 @@ EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' \
PYINC='${STAGING_INCDIR}/$(PYLIBVER)' \
pyexecdir=${libdir}/python${PYTHON_BASEVERSION}/site-packages \
STDINC='${STAGING_INCDIR}' \
+ pkgconfigdir=${libdir}/pkgconfig \
"
SUMMARY_audispd-plugins = "Plugins for the audit event dispatcher"
@@ -64,7 +65,7 @@ FILES_audispd-plugins +=
"${sysconfdir}/audisp/audisp-remote.conf \
"
FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug"
FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}"
-FILES_${PN}-dev += "${base_libdir}/*.so ${base_libdir}/*.la
${base_libdir}/pkgconfig/*"
+FILES_${PN}-dev += "${base_libdir}/*.so ${base_libdir}/*.la"
Aren't these already part of FILES_${PN}-dev in bitbake.conf in oe-core?
Thanks for point out. It is a legacy patch added in 2012 and I will
remove it with V2.
--Kai
Thanks,
Anuj
--
Regards,
Neil | Kai Kang
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [Recipe reporting system] Upgradable recipe name list
This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package Version Upstream version Maintainer NoUpgradeReason --- -- webkitgtk 2.18.6 2.20.0Alexander Kanavin gcr 3.20.0 3.28.0Alexander Kanavin gnome-desktop33.26.2 3.28.0Alexander Kanavin libsecret 0.18.5 0.18.6Alexander Kanavin dtc 1.4.51.4.6 Alexander Kanavin bash-completion 2.7 2.8 Alexander Kanavin gobject-introspec... 1.54.1 1.56.0Alexander Kanavin sysprof 3.26.1 3.28.0Alexander Kanavin libidn1.33 1.34 Alexander Kanavin epiphany 3.26.6 3.28.0.1 Alexander Kanavin vala 0.38.8 0.40.2Alexander Kanavin gtk-doc 1.27 1.28 Alexander Kanavin libaio0.3.110 0.3.111 Alexander Kanavin lighttpd 1.4.48 1.4.49Alexander Kanavin procps3.3.12 3.3.13Alexander Kanavin meson 0.44.1 0.45.1Alexander Kanavin btrfs-tools 4.13.3 4.15.1Alexander Kanavin Waiting for resolution of h... babeltrace1.5.41.5.5 Alexander Kanavin icu 60.2 61.1 Alexander Kanavin apt 1.2.24 1.4.8 Aníbal Limón dpkg 1.18.24 1.19.0.5 Aníbal Limón apt-native1.2.24 1.4.8 Aníbal Limón gst-examples 0.0.1+gitX 0.0.1-new-commits... Anuj Mittal gstreamer1.0-rtsp... 1.12.4 1.14.0Anuj Mittal gstreamer1.0-plug... 1.12.4 1.14.0Anuj Mittal gst-validate 1.12.4 1.14.0Anuj Mittal gstreamer1.0-libav1.12.4 1.14.0Anuj Mittal gstreamer1.0-plug... 1.12.4 1.14.0Anuj Mittal gstreamer1.0-plug... 1.12.4 1.14.0Anuj Mittal gstreamer1.0-plug... 1.12.4 1.14.0Anuj Mittal gstreamer1.0 1.12.4 1.14.0Anuj Mittal gstreamer1.0-vaapi1.12.4 1.14.0Anuj Mittal gstreamer1.0-omx 1.12.4 1.14.0Anuj Mittal gstreamer1.0-python 1.12.4 1.14.0Anuj Mittal mkfontscale 1.1.21.1.3 Armin Kuster xeyes 1.1.11.1.2 Armin Kuster xinit 1.3.41.4.0 Armin Kuster xkbcomp 1.4.01.4.1 Armin Kuster bind 9.10.6 9.12.1Armin Kuster xprop 1.2.21.2.3 Armin Kuster xset 1.2.31.2.4 Armin Kuster xwininfo 1.1.31.1.4 Armin Kuster xf86-video-vesa 2.3.42.4.0 Armin Kuster libxcb1.12 1.13 Armin Kuster libxshmfence 1.2 1.3 Armin Kuster xkeyboard-config 2.22 2.23.1Armin Kuster calibrateproto0.0+gitX 0.0-new-commits-a... Armin Kuster xcb-proto 1.12 1.13 Armin Kuster util-macros 1.19.1 1.19.2Armin Kuster xserver-xorg 1.19.6 1.19.99.902 Armin Kuster xf86-input-libinput 0.26.0 0.27.0Armin Kuster curl 7.58.0 7.59.0Armin Kuster busybox 1.27.2 1.28.2Armin Kuster gnutls3.6.13.6.2 Armin Kuster libpcre2 10.3010.31 Armin Kuster kern-tools-native 0.2+gitX 0.2-new-commits-a... Bruce Ashfield linux-libc-headers4.15.7 4.15.15 Bruce A
[yocto] [meta-selinux][PATCH V2 0/2] Fix systemd configure error if audit enabled
V2:
* remove setting of FILES_${PN}-dev from recipe of audit which has been done in
bitbake.conf in oe-core.
Kai Kang (2):
enable-audit.bbclass: remove implement of packageconfig audit
audit: fix pkgconfigdir
classes/enable-audit.bbclass | 1 -
recipes-security/audit/audit_2.7.6.bb | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 1/2] enable-audit.bbclass: remove implement of packageconfig audit
enable-audit.bbclass is only used by systemd. And systemd has adapted to
use build tool meson and implement PACKAGECONFIG audit in recipe file of
systemd in oe-core.
So remove implement of PACKAGECONFIG audit from enable-audit.bbclass.
Signed-off-by: Kai Kang
---
classes/enable-audit.bbclass | 1 -
1 file changed, 1 deletion(-)
diff --git a/classes/enable-audit.bbclass b/classes/enable-audit.bbclass
index 5820a38..4538b0b 100644
--- a/classes/enable-audit.bbclass
+++ b/classes/enable-audit.bbclass
@@ -2,4 +2,3 @@
inherit selinux
PACKAGECONFIG_append = " ${@target_selinux(d, 'audit')}"
-PACKAGECONFIG[audit] = "--enable-audit,--disable-audit,audit,"
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 2/2] audit: fix pkgconfigdir
Because 'libdir' is set with ${base_libdir} in recipe file of audit,
package config files(.pc) are installed to ${base_libdir}/pkgconfig that
variable pkgconfigdir is set with ${libdir}/pkgconfig in makefile.
Set pkgconfigdir directly to install .pc files to right directory.
And remove setting of FILES_${PN}-dev which has been done in
bitbake.conf in oe-core.
Signed-off-by: Kai Kang
---
recipes-security/audit/audit_2.7.6.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/audit/audit_2.7.6.bb
b/recipes-security/audit/audit_2.7.6.bb
index 5bfda7b..d655e64 100644
--- a/recipes-security/audit/audit_2.7.6.bb
+++ b/recipes-security/audit/audit_2.7.6.bb
@@ -45,6 +45,7 @@ EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' \
PYINC='${STAGING_INCDIR}/$(PYLIBVER)' \
pyexecdir=${libdir}/python${PYTHON_BASEVERSION}/site-packages \
STDINC='${STAGING_INCDIR}' \
+ pkgconfigdir=${libdir}/pkgconfig \
"
SUMMARY_audispd-plugins = "Plugins for the audit event dispatcher"
@@ -64,7 +65,6 @@ FILES_audispd-plugins +=
"${sysconfdir}/audisp/audisp-remote.conf \
"
FILES_${PN}-dbg += "${libdir}/python${PYTHON_BASEVERSION}/*/.debug"
FILES_${PN}-python = "${libdir}/python${PYTHON_BASEVERSION}"
-FILES_${PN}-dev += "${base_libdir}/*.so ${base_libdir}/*.la
${base_libdir}/pkgconfig/*"
CONFFILES_auditd += "${sysconfdir}/audit/audit.rules"
RDEPENDS_auditd += "bash"
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-java][PATCH v2] ca-certificates-java: add recipe to generate trustStore
From: André Draszik
The OpenJDK-8 package currently comes with a trustStore
that was generated at OpenJDK-8-native build time from
*all* certificates available in the system, not just from
those that are marked as trusted.
This isn't right...
So this recipe hooks into the ca-certificates package and
(re-) creates the Java trustStore based on the
certificates trusted by the system, whenever they are
updated. This works both at image build time, as well as
during runtime on the target.
It works by installing a hook into ca-certificates'
$SYSROOT/etc/ca-certificates/update.d/ that is passed the
added/removed certificates as arguments. That hook is then
updating the Java trustStore and storing it in
$SYSROOT/etc/ssl/certs/java/cacerts.
The whole idea as well as the implementation of the hook
is borrowed from debian's ca-certificate-java package,
version 20170930 (the latest as of this commit).
Looking at the debian package, it appears like the same
binary trustStore ($SYSROOT/etc/ssl/certs/java/cacerts)
can be used by different versions of Java:
* OpenJDK-7, 8, 9
* Oracle Java 7, 8, 9
The Java sources here can be compiled by any compatible
Java compiler, but the resulting jar file should only be
run by one of the compatible Java versions mentioned
above, so as to create a trustStore that can be read by
any of the Java versions mentioned above. We try to ensure
this using PACKAGE_WRITE_DEPS during image build time,
and by trying to find a compatible Java version inside
${libdir_jvm} at runtime both during image build time and
on the target.
Given there is nothing that we can RDEPENDS on that would
satisfy any of the above Java versions (either JDK or JRE),
we simply RDEPENDS on java2-runtime, and test
PREFERRED_RPROVIDER_java2-runtime to be satisfactory.
Given I can only test OpenJDK/OpenJRE 8 at the moment, only
those are actually allowed at the moment, though. This can
easily be extended upon confirmation.
Final note - as per the debian package, there are three
cases when we can be called:
1) as part of update-ca-certificates -> add / remove certs as instructed
2) if first time install -> add all certs
3) package update -> do nothing
We have no way to easily distinguish between first time install
and package update in OE, so the distinction between cases 2)
and 3) isn't perfect.
Signed-off-by: André Draszik
---
v2:
* Works with rm_work enabled. We can't use STAGING_LIBDIR_JVM_NATIVE
in pkg_postinst as that is statically resolved to this recipe's
native sysroot, which is of no use when building an image.
Use the NATIVE_ROOT variable instead
* make the ca-certificates hook script less verbose (remove set -x)
---
...ficates-handle-SYSROOT-environment-variab.patch | 43 +
.../ca-certificates-java.hook.in | 64
.../ca-certificates-java_20170930.bb | 107 +
3 files changed, 214 insertions(+)
create mode 100644
recipes-core/ca-certificates-java/ca-certificates-java/0001-UpdateCertificates-handle-SYSROOT-environment-variab.patch
create mode 100755
recipes-core/ca-certificates-java/ca-certificates-java/ca-certificates-java.hook.in
create mode 100644
recipes-core/ca-certificates-java/ca-certificates-java_20170930.bb
diff --git
a/recipes-core/ca-certificates-java/ca-certificates-java/0001-UpdateCertificates-handle-SYSROOT-environment-variab.patch
b/recipes-core/ca-certificates-java/ca-certificates-java/0001-UpdateCertificates-handle-SYSROOT-environment-variab.patch
new file mode 100644
index 000..ca052ab
--- /dev/null
+++
b/recipes-core/ca-certificates-java/ca-certificates-java/0001-UpdateCertificates-handle-SYSROOT-environment-variab.patch
@@ -0,0 +1,43 @@
+From 70cdd3c139230aa05816e98cdc3e50ead713 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Andr=C3=A9=20Draszik?=
+Date: Tue, 27 Mar 2018 16:50:39 +0100
+Subject: [PATCH] UpdateCertificates: handle SYSROOT environment variable for
+ cacerts
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+We can now pass in the sysroot, so that the trustStore
+is written to /etc/ssl/certs/java/cacerts below $SYSROOT.
+
+Upstream-Status: Inappropriate [OE specific]
+Signed-off-by: André Draszik
+---
+ src/main/java/org/debian/security/UpdateCertificates.java | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/src/main/java/org/debian/security/UpdateCertificates.java
b/src/main/java/org/debian/security/UpdateCertificates.java
+index e4f8205..dba9a7b 100644
+--- a/src/main/java/org/debian/security/UpdateCertificates.java
b/src/main/java/org/debian/security/UpdateCertificates.java
+@@ -40,15 +40,19 @@ public class UpdateCertificates {
+
+ public static void main(String[] args) throws IOException,
GeneralSecurityException {
+ String passwordString = "changeit";
++String sysroot;
+ if (args.length == 2 && args[0].equals("-storepass")) {
+ passwordString =
