[OE-core] Qt on Wandboard-solo with Yocto -Problem
Hello,
If anyone can help me to sought out the this issue to built up Qt on
wandboard-Solo with yocto.
Based on the url
http://wiki.wandboard.org/index.php/Building_Qt5_using_yocto_on_Wandboard I
altered the local.conf and the bblayers.confand gave a bitbake
core-image-minimal with DISTRO_FEATURE_remove
I got the errors as posted http://pastebin.com/hsMhT9f8.
Then to circumvent the errors I removed the DISTRO_FEATURE_remove from the
local.conf
and gave a bitbake.with this i got the errors as posted
http://pastebin.com/QFu2Rw6G.
for the thirld time I tried to change the following
1) In /meta-fsl-arm/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
QT_CONFIG_FLAGS_append_mx6 = ${@base_contains('DISTRO_FEATURES', 'x11',
*'-xcb'*, ' -eglfs', d)}
I replaced -no-eglfs with -xcb
2)In /bin/fsl-community-bsp/sources/meta-qt5/recipes-qt/qt5/qtbase.in
QT_CONFIG_FLAGS += \
-reduce-relocations \
-shared \
* -silent \*
-no-pch \
-no-rpath \
-pkg-config \
${EXTRA_OECONF} \
-silent was deleted.
With this setup and without DISTRO_FEATURE_remove I gave i bitbake and was
encountered with the errors as posted http://pastebin.com/V2fMF785
Please suggest to resolve this issue.
Thanks
Nilesh kokane
--
“The contents of this e-mail message and any attachments are confidential
and are intended solely for addressee. The information may also be legally
privileged. This transmission is sent in trust, for the sole purpose of
delivery to the intended recipient. If you have received this transmission
in error, any use, reproduction or dissemination of this transmission is
strictly prohibited. If you are not the intended recipient, please
immediately notify the sender by reply e-mail or phone and delete this
message and its attachments, if any.”
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] strace: fix ptest execution failure
ptest needs runtest-TESTS target.
serial-tests is required to generate this target.
Signed-off-by: Chong Lu chong...@windriver.com
---
.../strace/strace-4.8/Makefile-ptest.patch | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/strace/strace-4.8/Makefile-ptest.patch
b/meta/recipes-devtools/strace/strace-4.8/Makefile-ptest.patch
index f5556b2..3a0eb39 100644
--- a/meta/recipes-devtools/strace/strace-4.8/Makefile-ptest.patch
+++ b/meta/recipes-devtools/strace/strace-4.8/Makefile-ptest.patch
@@ -1,11 +1,13 @@
strace: Add ptest
+Upstream-Status: Inappropriate
+
Signed-off-by: Gabriel Barbu gabriel.ba...@enea.com
-Upstream-Status: Pending
+Signed-off-by: Chong Lu chong...@windriver.com
--- old/tests/Makefile.am 2013-07-23 13:44:24.660481381 +0200
+++ new/tests/Makefile.am 2013-07-23 16:22:42.937654391 +0200
-@@ -9,3 +9,20 @@
+@@ -9,3 +9,21 @@
EXTRA_DIST = init.sh $(TESTS)
CLEANFILES = check.log
@@ -18,6 +20,7 @@ Upstream-Status: Pending
+ install -d $(DESTDIR)/$(TESTDIR)
+ cp $(BUILDDIR)/$(TESTDIR)/Makefile $(DESTDIR)/$(TESTDIR)
+ sed -i -e 's/^Makefile:/_Makefile:/' $(DESTDIR)/$(TESTDIR)/Makefile
++ sed -i -e 's/bash/sh/' $(DESTDIR)/$(TESTDIR)/Makefile
+ for file in $(check_PROGRAMS); do \
+ install $(BUILDDIR)/$(TESTDIR)/$$file $(DESTDIR)/$(TESTDIR); \
+ done
@@ -26,3 +29,13 @@ Upstream-Status: Pending
+ sed -i -e 's/$${srcdir=.}/./g' $(DESTDIR)/$(TESTDIR)/$$file; \
+ done
+ sed -i -e 's/$$srcdir/./g' $(DESTDIR)/$(TESTDIR)/net
+--- a/configure.ac
b/configure.ac
+@@ -6,7 +6,7 @@ AC_INIT([strace],
+ AC_CONFIG_SRCDIR([strace.c])
+ AC_CONFIG_AUX_DIR([.])
+ AC_CONFIG_HEADERS([config.h])
+-AM_INIT_AUTOMAKE([foreign dist-xz no-dist-gzip silent-rules])
++AM_INIT_AUTOMAKE([foreign dist-xz no-dist-gzip silent-rules serial-tests])
+ AM_MAINTAINER_MODE
+ AC_CANONICAL_HOST
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] perl: fix the output format of all tests
We should use PASS:|FAIL:|SKIP: testname to output results of ptest. Signed-off-by: Chong Lu chong...@windriver.com --- meta/recipes-devtools/perl/perl-5.20.0/run-ptest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/perl/perl-5.20.0/run-ptest b/meta/recipes-devtools/perl/perl-5.20.0/run-ptest index ed59b4b..1e2dd1b 100644 --- a/meta/recipes-devtools/perl/perl-5.20.0/run-ptest +++ b/meta/recipes-devtools/perl/perl-5.20.0/run-ptest @@ -1,2 +1,2 @@ #!/bin/sh -cd t ./TEST | sed -u -e 's/^\([^. \t]*\)\.\.\.\+ok/PASS: \1/' -e 's/^\([^. \t]*\)\.\.\.\+skipped/SKIP: \1/' -e 's/^\([^. \t]*\)\.\.\.\+\(.*\)/FAIL: \1\n\2/' +cd t ./TEST | sed -u -e 's|\(.*\) .* ok$|PASS: \1|' -e 's|\(.*\) .* skipped|SKIP: \1|' -e 's|\(.*\) \.\(.*\)|FAIL: \1|' -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] dbus: fix ptest issue
We use PTEST_ENABLED to decide whether build ptest package, so inherit
ptest.bbclass in dbus.inc in order to using PTEST_ENABLED variable.
Remove PACKAGES and ALLOW_EMPTY, since they have been defined in ptest.bbclass.
Signed-off-by: Chong Lu chong...@windriver.com
---
meta/recipes-core/dbus/dbus.inc | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index d38ba7e..6268103 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -8,10 +8,13 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
DEPENDS = expat virtual/libintl
RDEPENDS_dbus_class-native =
RDEPENDS_dbus_class-nativesdk =
-PACKAGES += ${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest', '', d)}
-ALLOW_EMPTY_dbus-ptest = 1
+inherit ptest
RDEPENDS_dbus-ptest_class-target = dbus-test-ptest
+do_install_ptest_base() {
+ rm -rf ${D}${PTEST_PATH}
+}
+
SRC_URI = http://dbus.freedesktop.org/releases/dbus/dbus-${PV}.tar.gz \
file://tmpdir.patch \
file://dbus-1.init \
--
1.9.1
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] fix several ptest issues
The following changes since commit 870bb8d35547b8313b3a487d7e8b914ab9470e64: local.conf.sample.extended: fix example for EXTRA_USERS_PARAMS (2014-08-04 17:38:24 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib chonglu/ptest http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/ptest Chong Lu (3): perl: fix the output format of all tests strace: fix ptest execution failure dbus: fix ptest issue meta/recipes-core/dbus/dbus.inc | 7 +-- meta/recipes-devtools/perl/perl-5.20.0/run-ptest| 2 +- .../strace/strace-4.8/Makefile-ptest.patch | 17 +++-- 3 files changed, 21 insertions(+), 5 deletions(-) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] wpa-supplicant: use PACKAGECONFIG for ssl selection
From: Yasir-Khan yasir_k...@mentor.com
Select between openssl or gnutls as ssl implementation via
PACKAGECONFIG instead of explicitly adding both via DEPENDS.
Signed-off-by: Yasir-Khan yasir_k...@mentor.com
---
.../wpa-supplicant/wpa-supplicant.inc | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
index d9c6532..3bbe832 100644
--- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
+++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
@@ -6,9 +6,13 @@ LICENSE = BSD
LIC_FILES_CHKSUM = file://COPYING;md5=ab87f20cd7e8c0d0a6539b34d3791d0e \
file://README;beginline=1;endline=56;md5=a07250b28e857455336bb59fc31cb845 \
file://wpa_supplicant/wpa_supplicant.c;beginline=1;endline=12;md5=e8e021e30f3a6ab7c341b66b86626a5a
-DEPENDS = gnutls dbus libnl openssl libgcrypt
+DEPENDS = dbus libnl libgcrypt
RRECOMMENDS_${PN} = wpa-supplicant-passphrase wpa-supplicant-cli
+PACKAGECONFIG[defaultval] += gnutls
+PACKAGECONFIG[gnutls] = ,,gnutls
+PACKAGECONFIG[ssl] = ,,openssl
+
inherit systemd
SYSTEMD_SERVICE_${PN} = wpa_supplicant.service
wpa_supplicant-nl80211@.service wpa_supplicant-wired@.service
@@ -36,6 +40,17 @@ CONFFILES_${PN} += ${sysconfdir}/wpa_supplicant.conf
do_configure () {
install -m 0755 ${WORKDIR}/defconfig-gnutls wpa_supplicant/.config
echo CFLAGS +=\-I${STAGING_INCDIR}/libnl3\ wpa_supplicant/.config
+
+ sed -i '/CONFIG_TLS/d' wpa_supplicant/.config
+ if echo ${PACKAGECONFIG} | grep -qw ssl; then
+ ssl=openssl
+ elif echo ${PACKAGECONFIG} | grep -qw gnutls; then
+ ssl=gnutls
+ fi
+ if [ -n $ssl ]; then
+ echo CONFIG_TLS = $ssl wpa_supplicant/.config
+ fi
+
}
export EXTRA_CFLAGS = ${CFLAGS}
--
1.7.9.5
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] blocking pie in recipes that build shared object files
On 08/04/2014 05:39 PM, Khem Raj wrote:
On 14-08-04 09:56:37, Peter A. Bigot wrote:
I've now hit two recipes in meta-openembedded that fail on armv7-a because
SECURITY_CFLAGS has -pie as an option that leaks into a link command
building a shared object file. This produces:
|
/prj/oe/omap/build-beaglebone-master/tmp/sysroots/beaglebone/usr/lib/Scrt1.o:
In function `_start':
|
/prj/oe/omap/build-beaglebone-master/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/eglibc/2.19-r0/eglibc-2.19/libc/csu/../ports/sysdeps/arm/start.S:128:
undefined reference to `main'
| collect2: error: ld returned 1 exit status
| error: command 'arm-poky-linux-gnueabi-gcc' failed with exit status 1
In openembedded-core meta/conf/distro/include/security_flags.inc provides a
bunch of package-specific overrides to use SECURITY_NO_PIE_CFLAGS for this
sort of package.
It's not clear to me how that should be accomplished for recipes that are
not part of openembedded-core. For
http://patches.openembedded.org/patch/77165/ for python-smbus in meta-python
I chose to override it in the bb file.
What is the best-practices solution to this problem?
may be add SECURITY_CFLAGS_pn-blah = ${SECURITY_NO_PIE_CFLAGS}
to layer.conf of given layer where recipe resides
Could do that. Is there precedent?
Looking into this more, the reason I'm hitting this is I'm using
DISTRO=poky-lsb, which gives me oe-core's
conf/distro/include/security_flags.inc automatically.
Now that I know more I'm uncomfortable about putting a distro-specific
workaround in each recipe patch I submit, and more uncomfortable about
creating new precedent by putting distro-specific workarounds in
layer.conf files. Updates to python-smbus in meta-python and rrdtool in
meta-oe are affected by this, plus the 42 package exceptions already
listed in security_flags.inc.
I'm going to stop using poky-lsb for now to hide the problem, but for
the future we need guidance on how to make recipes/layers compatible
with distros that want to enable security_flags.inc.
Peter
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] Add doc entry for ptest-pkgs in IMAGE_FEATURES list
Signed-off-by: Robert P. J. Day rpj...@crashcourse.ca
---
diff --git a/meta/classes/core-image.bbclass b/meta/classes/core-image.bbclass
index 1b36cba..67e11bf 100644
--- a/meta/classes/core-image.bbclass
+++ b/meta/classes/core-image.bbclass
@@ -30,6 +30,7 @@ LIC_FILES_CHKSUM =
file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d
# - dev-pkgs- development packages (headers, etc.) for all
installed packages in the rootfs
# - dbg-pkgs- debug symbol packages for all installed packages in
the rootfs
# - doc-pkgs- documentation packages for all installed packages in
the rootfs
+# - ptest-pkgs - ptest packages for all ptest-enabled recipes
# - read-only-rootfs- tweaks an image to support read-only rootfs
#
FEATURE_PACKAGES_x11 = packagegroup-core-x11
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/3] dbus: fix ptest issue
On Tue, 2014-08-05 at 16:33 +0800, Chong Lu wrote:
We use PTEST_ENABLED to decide whether build ptest package, so inherit
ptest.bbclass in dbus.inc in order to using PTEST_ENABLED variable.
Remove PACKAGES and ALLOW_EMPTY, since they have been defined in
ptest.bbclass.
Signed-off-by: Chong Lu chong...@windriver.com
---
meta/recipes-core/dbus/dbus.inc | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index d38ba7e..6268103 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -8,10 +8,13 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
DEPENDS = expat virtual/libintl
RDEPENDS_dbus_class-native =
RDEPENDS_dbus_class-nativesdk =
-PACKAGES += ${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest', '',
d)}
-ALLOW_EMPTY_dbus-ptest = 1
I don't think you've understood what this is doing, its conditionally
building the separate dbus-ptest recipe, if ptest is enabled.
Why is it separate? dbus-ptest needs glib and glib needs dbus. Your
patch doesn't seem to account for any of that.
fix ptest issue is far too vague as a summary of this patch too.
Cheers,
Richard
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/3] dbus: fix ptest issue
On 08/05/2014 05:53 PM, Richard Purdie wrote:
On Tue, 2014-08-05 at 16:33 +0800, Chong Lu wrote:
We use PTEST_ENABLED to decide whether build ptest package, so inherit
ptest.bbclass in dbus.inc in order to using PTEST_ENABLED variable.
Remove PACKAGES and ALLOW_EMPTY, since they have been defined in ptest.bbclass.
Signed-off-by: Chong Lu chong...@windriver.com
---
meta/recipes-core/dbus/dbus.inc | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus.inc b/meta/recipes-core/dbus/dbus.inc
index d38ba7e..6268103 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -8,10 +8,13 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
DEPENDS = expat virtual/libintl
RDEPENDS_dbus_class-native =
RDEPENDS_dbus_class-nativesdk =
-PACKAGES += ${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest', '', d)}
-ALLOW_EMPTY_dbus-ptest = 1
I don't think you've understood what this is doing, its conditionally
building the separate dbus-ptest recipe, if ptest is enabled.
Why is it separate? dbus-ptest needs glib and glib needs dbus. Your
patch doesn't seem to account for any of that.
fix ptest issue is far too vague as a summary of this patch too.
Cheers,
Richard
Hi Richard,
Previously, we use DISTRO_FEATURES to decide whether build ptest, but we
use PTEST_ENABLED now.
PTEST_ENABLED defined in ptest.bbclass. we did't inherit ptest in dbus
recipes, this cause we can't build dbus-ptest package.
Based on above reason, I just send this patch to fix this issue. Or do
you have a better way?
Best Regards
Chong
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/3] dbus: fix ptest issue
On Tuesday 05 August 2014 18:07:50 Chong Lu wrote:
On 08/05/2014 05:53 PM, Richard Purdie wrote:
On Tue, 2014-08-05 at 16:33 +0800, Chong Lu wrote:
We use PTEST_ENABLED to decide whether build ptest package, so inherit
ptest.bbclass in dbus.inc in order to using PTEST_ENABLED variable.
Remove PACKAGES and ALLOW_EMPTY, since they have been defined in
ptest.bbclass.
Signed-off-by: Chong Lu chong...@windriver.com
---
meta/recipes-core/dbus/dbus.inc | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus.inc
b/meta/recipes-core/dbus/dbus.inc index d38ba7e..6268103 100644
--- a/meta/recipes-core/dbus/dbus.inc
+++ b/meta/recipes-core/dbus/dbus.inc
@@ -8,10 +8,13 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=10dded3b58148f3f1fd804b26354af3e \
DEPENDS = expat virtual/libintl
RDEPENDS_dbus_class-native =
RDEPENDS_dbus_class-nativesdk =
-PACKAGES += ${@bb.utils.contains('PTEST_ENABLED', '1', 'dbus-ptest',
'', d)} -ALLOW_EMPTY_dbus-ptest = 1
I don't think you've understood what this is doing, its conditionally
building the separate dbus-ptest recipe, if ptest is enabled.
Why is it separate? dbus-ptest needs glib and glib needs dbus. Your
patch doesn't seem to account for any of that.
fix ptest issue is far too vague as a summary of this patch too.
Cheers,
Richard
Hi Richard,
Previously, we use DISTRO_FEATURES to decide whether build ptest, but we
use PTEST_ENABLED now.
PTEST_ENABLED defined in ptest.bbclass. we did't inherit ptest in dbus
recipes, this cause we can't build dbus-ptest package.
Based on above reason, I just send this patch to fix this issue. Or do
you have a better way?
If you mean that you're setting PTEST_ENABLED globally, you shouldn't be doing
that. PTEST_ENABLED is supposed to be used for recipes to *detect* whether
ptest should be enabled, so that e.g. we can disable it for the native class.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] wpa-supplicant: use PACKAGECONFIG for ssl selection
On Tue, Aug 05, 2014 at 02:02:21PM +0500, Yasir Khan wrote:
From: Yasir-Khan yasir_k...@mentor.com
Select between openssl or gnutls as ssl implementation via
PACKAGECONFIG instead of explicitly adding both via DEPENDS.
Signed-off-by: Yasir-Khan yasir_k...@mentor.com
---
.../wpa-supplicant/wpa-supplicant.inc | 17 -
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
index d9c6532..3bbe832 100644
--- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
+++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
@@ -6,9 +6,13 @@ LICENSE = BSD
LIC_FILES_CHKSUM = file://COPYING;md5=ab87f20cd7e8c0d0a6539b34d3791d0e \
file://README;beginline=1;endline=56;md5=a07250b28e857455336bb59fc31cb845 \
file://wpa_supplicant/wpa_supplicant.c;beginline=1;endline=12;md5=e8e021e30f3a6ab7c341b66b86626a5a
-DEPENDS = gnutls dbus libnl openssl libgcrypt
+DEPENDS = dbus libnl libgcrypt
RRECOMMENDS_${PN} = wpa-supplicant-passphrase wpa-supplicant-cli
+PACKAGECONFIG[defaultval] += gnutls
What is defaultval varflag?
We normally use PACKAGECONFIG ?= gnutls
+PACKAGECONFIG[gnutls] = ,,gnutls
+PACKAGECONFIG[ssl] = ,,openssl
+
inherit systemd
SYSTEMD_SERVICE_${PN} = wpa_supplicant.service
wpa_supplicant-nl80211@.service wpa_supplicant-wired@.service
@@ -36,6 +40,17 @@ CONFFILES_${PN} += ${sysconfdir}/wpa_supplicant.conf
do_configure () {
install -m 0755 ${WORKDIR}/defconfig-gnutls wpa_supplicant/.config
echo CFLAGS +=\-I${STAGING_INCDIR}/libnl3\ wpa_supplicant/.config
+
+ sed -i '/CONFIG_TLS/d' wpa_supplicant/.config
+ if echo ${PACKAGECONFIG} | grep -qw ssl; then
+ ssl=openssl
+ elif echo ${PACKAGECONFIG} | grep -qw gnutls; then
+ ssl=gnutls
+ fi
+ if [ -n $ssl ]; then
+ echo CONFIG_TLS = $ssl wpa_supplicant/.config
+ fi
Why don't you rename defconfig-gnutls to something generic and add
something like CONFIG_TLS = %ssl% there to replace it with one sed
call here based on selected implementation.
+
}
export EXTRA_CFLAGS = ${CFLAGS}
--
1.7.9.5
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] i guess there's no way to *conditionally* add tasks?
digging into ptest stuff, and i notice this in ptest.bbclass:
addtask configure_ptest_base after do_configure before do_compile
addtask compile_ptest_base after do_compile before do_install
addtask install_ptest_base after do_install before do_package
do_populate_sysroot
python () {
if not bb.data.inherits_class('native', d) and not
bb.data.inherits_class('cross', d):
d.setVarFlag('do_install_ptest_base', 'fakeroot', 1)
# Remove all '*ptest_base' tasks when ptest is not enabled
if not(d.getVar('PTEST_ENABLED', True) == 1):
for i in ['do_configure_ptest_base', 'do_compile_ptest_base',
'do_install_ptest_base']:
bb.build.deltask(i, d)
}
so i'm guessing there's no way to conditionally add task(s) to avoid
adding them, only to turn around and delete them, yes?
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] still some remnants of allegedly removed do_package_write task
yocto ref manual, 5.5.13 (Tasks), claims:
The do_package_write task has been removed. The task is no longer
needed.
but there still appear to be a few lingering references to it in
oe-core:
$ grep -rw do_package_write meta
meta/classes/rm_work.bbclass:*do_package_write*)
meta/recipes-core/meta/meta-ide-support.bb:do_populate_ide_support[recrdeptask]
= do_package_write
meta/recipes-core/meta/package-index.bb:do_package_write[noexec] = 1
meta/recipes-devtools/installer/adt-installer_1.0.bb:do_package_write[noexec]
= 1
meta/conf/documentation.conf:do_package_write[doc] = Creates the
actual packages and places them in the Package Feed area
$
assuming all packaging is now handled by the packaging-specific
tasks like do_package_write_{ipk,rpm,deb}, can those last few
references be deleted? (not the one in rm_work.bbclass, though, given
that it's a wildcard.)
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] perf: explicitly disable libunwind
* it's not included in DEPENDS and it's detected from sysroot
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta/recipes-kernel/perf/perf.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
index 222ae83..ea8599a 100644
--- a/meta/recipes-kernel/perf/perf.bb
+++ b/meta/recipes-kernel/perf/perf.bb
@@ -76,7 +76,7 @@ EXTRA_OEMAKE = \
CC=${CC} \
AR=${AR} \
perfexecdir=${libexecdir} \
- NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 ${SCRIPTING_DEFINES} \
+ NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 NO_LIBUNWIND=1
${SCRIPTING_DEFINES} \
'
EXTRA_OEMAKE += \
--
2.0.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] perf: fix indentation
* multiline variables should use spaces not tabs for indentation
* do_configure is also using wrong indentation, but I'm not fixing
this one (still hoping that we'll eventually fix styleguide to
use 4 spaces everywhere)
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta/recipes-kernel/perf/perf.bb | 54
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
index ea8599a..bfd210c 100644
--- a/meta/recipes-kernel/perf/perf.bb
+++ b/meta/recipes-kernel/perf/perf.bb
@@ -22,13 +22,13 @@ TUI_DEPENDS = ${@perf_feature_enabled('perf-tui', 'libnewt
slang', '',d)}
SCRIPTING_DEPENDS = ${@perf_feature_enabled('perf-scripting', 'perl python',
'',d)}
DEPENDS = virtual/kernel \
- virtual/${MLPREFIX}libc \
- ${MLPREFIX}elfutils \
- ${MLPREFIX}binutils \
- ${TUI_DEPENDS} \
- ${SCRIPTING_DEPENDS} \
- bison flex \
-
+virtual/${MLPREFIX}libc \
+${MLPREFIX}elfutils \
+${MLPREFIX}binutils \
+${TUI_DEPENDS} \
+${SCRIPTING_DEPENDS} \
+bison flex \
+
PROVIDES = virtual/perf
@@ -68,28 +68,28 @@ TUI_DEFINES = ${@perf_feature_enabled('perf-tui', '',
'NO_NEWT=1',d)}
# supported kernel.
LDFLAGS=-ldl -lutil
-EXTRA_OEMAKE = \
- '-C ${S}/tools/perf \
- O=${B} \
- CROSS_COMPILE=${TARGET_PREFIX} \
- ARCH=${ARCH} \
- CC=${CC} \
- AR=${AR} \
- perfexecdir=${libexecdir} \
- NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 NO_LIBUNWIND=1
${SCRIPTING_DEFINES} \
- '
+EXTRA_OEMAKE = '\
+-C ${S}/tools/perf \
+O=${B} \
+CROSS_COMPILE=${TARGET_PREFIX} \
+ARCH=${ARCH} \
+CC=${CC} \
+AR=${AR} \
+perfexecdir=${libexecdir} \
+NO_GTK2=1 ${TUI_DEFINES} NO_DWARF=1 NO_LIBUNWIND=1 ${SCRIPTING_DEFINES} \
+'
EXTRA_OEMAKE += \
- 'prefix=${prefix}' \
- 'bindir=${bindir}' \
- 'sharedir=${datadir}' \
- 'sysconfdir=${sysconfdir}' \
- 'perfexecdir=${libexecdir}/perf-core' \
- \
- 'ETC_PERFCONFIG=${@os.path.relpath(sysconfdir, prefix)}' \
- 'sharedir=${@os.path.relpath(datadir, prefix)}' \
- 'mandir=${@os.path.relpath(mandir, prefix)}' \
- 'infodir=${@os.path.relpath(infodir, prefix)}' \
+'prefix=${prefix}' \
+'bindir=${bindir}' \
+'sharedir=${datadir}' \
+'sysconfdir=${sysconfdir}' \
+'perfexecdir=${libexecdir}/perf-core' \
+\
+'ETC_PERFCONFIG=${@os.path.relpath(sysconfdir, prefix)}' \
+'sharedir=${@os.path.relpath(datadir, prefix)}' \
+'mandir=${@os.path.relpath(mandir, prefix)}' \
+'infodir=${@os.path.relpath(infodir, prefix)}' \
PARALLEL_MAKE =
--
2.0.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] image.bbclass: Adding loop back for machine name in hosts file
sujith h sujith.h-re5jqeeqqe8avxtiumw...@public.gmane.org writes:
Is it ok to read from /etc/hostname and then have that in the /etc/hosts
file, rather than using ${MACHINE}?
...
+ echo 127.0.1.1${MACHINE}
${IMAGE_ROOTFS}${sysconfdir}/hosts
I do not see how this can be done while building the image or the
packages. Both the hostname and the ip address can be configured at
runtime. As this can happen dynamically e.g. by DHCP and can change
at every boot or even at runtime, there is no generic way (e.g. by
firstboot mechanisms) to add such entries.
Enrico
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] i guess there's no way to *conditionally* add tasks?
Robert P. J. Day rpjday-L09J2beyid0N/h6p543...@public.gmane.org
writes:
addtask configure_ptest_base after do_configure before do_compile
addtask compile_ptest_base after do_compile before do_install
addtask install_ptest_base after do_install before do_package
do_populate_sysroot
...
# Remove all '*ptest_base' tasks when ptest is not enabled
if not(d.getVar('PTEST_ENABLED', True) == 1):
for i in ['do_configure_ptest_base', 'do_compile_ptest_base',
'do_install_ptest_base']:
bb.build.deltask(i, d)
so i'm guessing there's no way to conditionally add task(s) to avoid
adding them, only to turn around and delete them, yes?
I solved similar issues by including files conditionally; e.g. above
would be
---
ptest_inc = ${@['noop', 'ptest'][d.getVar('PTEST_ENABLED', True) == '1']}
include ptest-${ptest_inc}.inc
--- ptest-ptest.inc ---
addtask configure_ptest_base after do_configure before do_compile
addtask compile_ptest_base after do_compile before do_install
addtask install_ptest_base after do_install before do_package
do_populate_sysroot
Enrico
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] bluez5: Allow method calls over dbus for bluetooth daemon
From: Yasir-Khan yasir_k...@mentor.com This patch changes the dbus policy settings in order to allow calling methods over dbus. bluez5 and pulseaudio rely on this mechanism to configure media end points. Previously bluetoothd was failing to configure the media end points with error org.freedesktop.DBus.Error.AccessDenied, due to which bluetooth headset and smartphone were unable to connect in A2DP mode. Signed-off-by: Yasir-Khan yasir_k...@mentor.com --- .../bluez5/bluez5/bluetooth.conf |1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf b/meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf index e21e72e..26845bb 100644 --- a/meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf +++ b/meta/recipes-connectivity/bluez5/bluez5/bluetooth.conf @@ -11,6 +11,7 @@ allow own=org.bluez/ allow send_destination=org.bluez/ allow send_interface=org.bluez.Agent1/ +allow send_type=method_call/ /policy /busconfig -- 1.7.9.5 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] i guess there's no way to *conditionally* add tasks?
On Tuesday 05 August 2014 13:28:45 Enrico Scholz wrote:
Robert P. J. Day rpjday-L09J2beyid0N/h6p543...@public.gmane.org
writes:
addtask configure_ptest_base after do_configure before do_compile
addtask compile_ptest_base after do_compile before do_install
addtask install_ptest_base after do_install before do_package
do_populate_sysroot ...
# Remove all '*ptest_base' tasks when ptest is not enabled
if not(d.getVar('PTEST_ENABLED', True) == 1):
for i in ['do_configure_ptest_base', 'do_compile_ptest_base',
'do_install_ptest_base']:
bb.build.deltask(i, d)
so i'm guessing there's no way to conditionally add task(s) to avoid
adding them, only to turn around and delete them, yes?
I solved similar issues by including files conditionally; e.g. above
would be
---
ptest_inc = ${@['noop', 'ptest'][d.getVar('PTEST_ENABLED', True) == '1']}
include ptest-${ptest_inc}.inc
--- ptest-ptest.inc ---
addtask configure_ptest_base after do_configure before do_compile
addtask compile_ptest_base after do_compile before do_install
addtask install_ptest_base after do_install before do_package
do_populate_sysroot
The point is most of the time you shouldn't need to do this kind of thing
anymore since the introduction of addtask/deltask python functions.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Qt on Wandboard-solo with Yocto -Problem
On Tue, Aug 5, 2014 at 4:24 AM, Nilesh Kokane nilesh.kok...@mindastoneridge.com wrote: If anyone can help me to sought out the this issue to built up Qt on wandboard-Solo with yocto. Please wait until someone answer for few days before reposting something[1]. 1. https://www.ietf.org/rfc/rfc1855.txt -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] image.bbclass: Adding loop back for machine name in hosts file
Op 4 aug. 2014, om 15:57 heeft Sujith H sujit...@gmail.com het volgende geschreven: From: Sujith H sujith_harida...@mentor.com If hostname is not added to /etc/hosts file then rpcinfo command fails when hostname is passed as argument. This was observed when rpcinfo command was tested on freescale target. Below was the output observed without this change. Isn't this what nssmyhostname is for? -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] image.bbclass: Adding loop back for machine name in hosts file
On Tue, Aug 5, 2014 at 6:17 PM, Koen Kooi k...@dominion.thruhere.net wrote: Op 4 aug. 2014, om 15:57 heeft Sujith H sujit...@gmail.com het volgende geschreven: From: Sujith H sujith_harida...@mentor.com If hostname is not added to /etc/hosts file then rpcinfo command fails when hostname is passed as argument. This was observed when rpcinfo command was tested on freescale target. Below was the output observed without this change. Isn't this what nssmyhostname is for? Yes adding nss-myhostname would be the cleaner solution. Thanks Koen Kooi. -- സുജിത് ഹരിദാസന് Bangalore ProjectContributor to KDE project http://fci.wikia.com/wiki/Anti-DRM-Campaign Blog http://sujithh.info -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] blocking pie in recipes that build shared object files
On Tuesday, August 5, 2014, Peter A. Bigot p...@pabigot.com wrote:
On 08/04/2014 05:39 PM, Khem Raj wrote:
On 14-08-04 09:56:37, Peter A. Bigot wrote:
I've now hit two recipes in meta-openembedded that fail on armv7-a
because
SECURITY_CFLAGS has -pie as an option that leaks into a link command
building a shared object file. This produces:
|
/prj/oe/omap/build-beaglebone-master/tmp/sysroots/
beaglebone/usr/lib/Scrt1.o:
In function `_start':
| /prj/oe/omap/build-beaglebone-master/tmp/work/cortexa8hf-
vfp-neon-poky-linux-gnueabi/eglibc/2.19-r0/eglibc-2.19/
libc/csu/../ports/sysdeps/arm/start.S:128:
undefined reference to `main'
| collect2: error: ld returned 1 exit status
| error: command 'arm-poky-linux-gnueabi-gcc' failed with exit status 1
In openembedded-core meta/conf/distro/include/security_flags.inc
provides a
bunch of package-specific overrides to use SECURITY_NO_PIE_CFLAGS for
this
sort of package.
It's not clear to me how that should be accomplished for recipes that are
not part of openembedded-core. For
http://patches.openembedded.org/patch/77165/ for python-smbus in
meta-python
I chose to override it in the bb file.
What is the best-practices solution to this problem?
may be add SECURITY_CFLAGS_pn-blah = ${SECURITY_NO_PIE_CFLAGS}
to layer.conf of given layer where recipe resides
Could do that. Is there precedent?
Don't think so. But you can compare to things like how package blacklisting
is done in meta-OE.
Looking into this more, the reason I'm hitting this is I'm using
DISTRO=poky-lsb, which gives me oe-core's
conf/distro/include/security_flags.inc
automatically.
Now that I know more I'm uncomfortable about putting a distro-specific
workaround in each recipe patch I submit, and more uncomfortable about
creating new precedent by putting distro-specific workarounds in layer.conf
files. Updates to python-smbus in meta-python and rrdtool in meta-oe are
affected by this, plus the 42 package exceptions already listed in
security_flags.inc.
I don't think it's so distro related. Security flags is a general OE
feature. So layers have to deal with it in distro independent way and IMO
it's best place to dictate what recipes in a given layer can support, you
can also add this to recipe itself and if numbers of recipes to deal with
are less. It's similar to blacklisting feature.
I'm going to stop using poky-lsb for now to hide the problem, but for the
future we need guidance on how to make recipes/layers compatible with
distros that want to enable security_flags.inc.
Peter
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] PR_Service: Improvement of persistance of PR service
The current implementation only commits database changes after database exceptions or daemon shutdown. This patch adds a delayed commit after every request finish, defaulting to 20 seconds. I chose to make the sync on the consumer thread rather than the producer. This is to avoid simultaneous access to the database. I chose to use a separate timeout than the timeout defined for handle_request in work_forever. This is because the consumer thread would reach the handle_request before the quit flag was set. Thus for long timeouts the stop_daemon function would have to wait for an equally long amount of time. This solution is based on this discussion : https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg52932.html NOTE: I made a mistake with the previous patch I posted in this post: http://lists.openembedded.org/pipermail/openembedded-core/2014-July/095133.html I was using the wrong repository. This time it should be correct. Signed-off-by: Dimitrios Katsaros dmtka...@gmail.com --- lib/prserv/serv.py | 22 ++ 1 file changed, 18 insertions(+), 4 deletions(-) diff --git a/lib/prserv/serv.py b/lib/prserv/serv.py index 1e170ce..9c37339 100644 --- a/lib/prserv/serv.py +++ b/lib/prserv/serv.py @@ -1,4 +1,4 @@ -import os,sys,logging +import os,sys,logging, time import signal, time, atexit, threading from SimpleXMLRPCServer import SimpleXMLRPCServer, SimpleXMLRPCRequestHandler import xmlrpclib @@ -36,7 +36,7 @@ singleton = None class PRServer(SimpleXMLRPCServer): -def __init__(self, dbfile, logfile, interface, daemon=True): +def __init__(self, dbfile, logfile, interface, daemon=True, sync_timeout=20): ''' constructor ''' SimpleXMLRPCServer.__init__(self, interface, logRequests=False, allow_none=True) @@ -46,6 +46,8 @@ class PRServer(SimpleXMLRPCServer): self.working_thread=None self.host, self.port = self.socket.getsockname() self.pidfile=PIDPREFIX % (self.host, self.port) +self.dirty = False +self.sync_timeout = sync_timeout self.register_function(self.getPR, getPR) self.register_function(self.quit, quit) @@ -70,8 +72,13 @@ class PRServer(SimpleXMLRPCServer): while True: (request, client_address) = self.requestqueue.get() try: -self.finish_request(request, client_address) -self.shutdown_request(request) +if request == Sync: +self.table.sync() +else: +self.finish_request(request, client_address) +self.shutdown_request(request) +self.time_from_dirty = time.time() +self.dirty = True except: self.handle_error(request, client_address) self.shutdown_request(request) @@ -126,6 +133,13 @@ class PRServer(SimpleXMLRPCServer): self.server_close() return +def handle_timeout(self): +if self.dirty: +# making the consumer thead perform sync to ensure thread safty +if time.time() - self.time_from_dirty self.sync_timeout: +self.requestqueue.put((Sync, None)) +self.dirty = False + def start(self): pid = self.daemonize() # Ensure both the parent sees this and the child from the work_forever log entry above -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] INITRD var: make it a list of filesystem images
On 8/4/14, 21:33, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
On 8/4/2014 9:38 AM, Hart, Darren wrote:
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
...
+ if [ -n ${INITRD} ]; then
+ rm -f $dest/initrd
+ for fs in ${INITRD}
+ do
+ if [ -n ${fs} ] [ -s ${fs} ]; then
The -n test is unnecessary here. How would for fs in ${INITRD} result
in
an fs of ?
The -n test is needed here, it checks whether the file exist or not.
Nope, -n tests if the string length is non-zero. See the bash manual
section CONDITIONAL EXPRESSIONS. -s tests if the file exists and has a
size 0.
+ cat ${fs} $dest/ignited
+ fi
Some kind of a warning at least is warranted if a file appears in the
INITRD list but is either 0-size or non-existent.
I tried to keep the original style of the code. But it makes sense to
add a warning or even an error here.
Style is fine, but error checking is a functional thing. If it was missing
before, it was a bug.
build_iso() {
# Only create an ISO if we have an INITRD and NOISO was not set
- if [ -z ${INITRD} ] || [ ! -s ${INITRD} ] || [ ${NOISO} = 1
];
then
+ if [ -z ${INITRD} ] || [ ${NOISO} = 1 ]; then
bbnote ISO image will not be created.
return
Fi
Perhaps the -s test should be replaced with a -s of $dest/initrd?
The -s test is replaced by the loop few lines below.
+ # ${INITRD} is a list of multiple filesystem images
+ for fs in ${INITRD}
+ do
+ if [ ! -s ${fs} ]; then
+ bbnote ISO image will not be created. ${fs} is
invalid.
+ return
+ fi
+ done
This additional loop could be eliminated by including this test above.
Right? Or am I missing something subtle here?
That approach will leave a hole where, the function will continue when
one of the filesystem image is invalid.
So the loop is better here as it does not leave any hole.
But you've already built it right? So you have already tested for -s ${fs}
previously. The only thing that matters now is that the assembled image is
valid. $dest/initrd. Right?
--
Darren Hart Open Source Technology Center
darren.h...@intel.com Intel Corporation
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] INITRD var: make it a list of filesystem images
On 8/5/2014 9:45 AM, Hart, Darren wrote:
On 8/4/14, 21:33, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
On 8/4/2014 9:38 AM, Hart, Darren wrote:
On 7/29/14, 11:34, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
...
+ if [ -n ${INITRD} ]; then
+ rm -f $dest/initrd
+ for fs in ${INITRD}
+ do
+ if [ -n ${fs} ] [ -s ${fs} ]; then
The -n test is unnecessary here. How would for fs in ${INITRD} result
in
an fs of ?
The -n test is needed here, it checks whether the file exist or not.
Nope, -n tests if the string length is non-zero. See the bash manual
section CONDITIONAL EXPRESSIONS. -s tests if the file exists and has a
size 0.
You are right. it is -N which checks for presence of the file.
+ cat ${fs} $dest/ignited
+ fi
Some kind of a warning at least is warranted if a file appears in the
INITRD list but is either 0-size or non-existent.
I tried to keep the original style of the code. But it makes sense to
add a warning or even an error here.
Style is fine, but error checking is a functional thing. If it was missing
before, it was a bug.
Noted.
build_iso() {
# Only create an ISO if we have an INITRD and NOISO was not set
- if [ -z ${INITRD} ] || [ ! -s ${INITRD} ] || [ ${NOISO} = 1
];
then
+ if [ -z ${INITRD} ] || [ ${NOISO} = 1 ]; then
bbnote ISO image will not be created.
return
Fi
Perhaps the -s test should be replaced with a -s of $dest/initrd?
The -s test is replaced by the loop few lines below.
+ # ${INITRD} is a list of multiple filesystem images
+ for fs in ${INITRD}
+ do
+ if [ ! -s ${fs} ]; then
+ bbnote ISO image will not be created. ${fs} is
invalid.
+ return
+ fi
+ done
This additional loop could be eliminated by including this test above.
Right? Or am I missing something subtle here?
That approach will leave a hole where, the function will continue when
one of the filesystem image is invalid.
So the loop is better here as it does not leave any hole.
But you've already built it right? So you have already tested for -s ${fs}
previously. The only thing that matters now is that the assembled image is
valid. $dest/initrd. Right?
No, the dest/initrd is not built at this point. It will be built in the
populate function which is called later. so that check will always fail
wrongly.
I also notice that RP has pulled in part of the commit already, hence I
will be making another commit to address the feedback.
Thanks,
Nitin
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] util-linux: create an all encompassing package group
Currently util-linux is fragmented into lots of small chunks, and if one is looking to avoid using busybox wholesale, there is currently no easy way to say I want all of it. Here we create a packagegroup for all of the util-linux chunks, so that it need not be duplicated by everyone wanting the same overall goal of removing busybox. Signed-off-by: Paul Gortmaker paul.gortma...@windriver.com diff --git a/meta/recipes-core/packagegroups/packagegroup-util-linux.bb b/meta/recipes-core/packagegroups/packagegroup-util-linux.bb new file mode 100644 index ..54151502b176 --- /dev/null +++ b/meta/recipes-core/packagegroups/packagegroup-util-linux.bb @@ -0,0 +1,69 @@ +# +# Copyright (C) 2014 Wind River +# + +SUMMARY = util-linux Packages +DESCRIPTION = Packages created from util-linux +PR = r0 +LICENSE = MIT + +inherit packagegroup + +PACKAGES = \ +packagegroup-util-linux \ +packagegroup-util-linux-block \ +packagegroup-util-linux-console \ +packagegroup-util-linux-uid \ +packagegroup-util-linux-misc \ +packagegroup-util-linux-partition \ + + +RDEPENDS_packagegroup-util-linux = \ +packagegroup-util-linux-block \ +packagegroup-util-linux-console \ +packagegroup-util-linux-uid \ +packagegroup-util-linux-misc \ +packagegroup-util-linux-partition \ + + +RDEPENDS_packagegroup-util-linux-partition = \ +util-linux-fdisk \ +util-linux-cfdisk \ +util-linux-sfdisk \ +util-linux-partx \ + + +RDEPENDS_packagegroup-util-linux-console = \ +util-linux-agetty \ +util-linux-reset \ + + +RDEPENDS_packagegroup-util-linux-block = \ +util-linux-mkfs \ +util-linux-mkfs.cramfs \ +util-linux-fsck.cramfs \ +util-linux-fstrim \ +util-linux-fsck \ +util-linux-blkid \ +util-linux-libblkid \ +util-linux-umount \ +util-linux-mount \ +util-linux-libmount \ +util-linux-swaponoff \ + + +RDEPENDS_packagegroup-util-linux-uid = \ +util-linux-libuuid \ +util-linux-uuidd \ +util-linux-uuidgen \ +util-linux-findfs \ + + +RDEPENDS_packagegroup-util-linux-misc = \ +util-linux-losetup \ +util-linux-readprofile \ +util-linux-lscpu \ +util-linux-mcookie \ +util-linux-bash-completion \ +util-linux-hwclock \ + -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 01/20] udev-cache: Compress the cache
On 14-08-04 02:40 PM, Ben Shelton wrote: From: Richard Tollerton rich.toller...@ni.com $DEVCACHE is observed to be 100k uncompressed; compressing it reduces its size to ~5k. Natinst-Rally-ID: TA44427 Acked-by: Gratian Crisan gratian.cri...@ni.com Natinst-ReviewBoard-ID: 58620 This is a good series of patches; thanks for sending them. It would be nice if you could remove your company's ID tags from the commit log. For example, you create and use could use a YP bugzilla ID ( https://bugzilla.yoctoproject.org/ ) and then match that up in your internal process. Thanks, ../Randy Signed-off-by: Richard Tollerton rich.toller...@ni.com --- meta/recipes-core/udev/udev/init | 2 +- meta/recipes-core/udev/udev/udev-cache | 2 +- meta/recipes-core/udev/udev/udev-cache.default | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/recipes-core/udev/udev/init b/meta/recipes-core/udev/udev/init index f2c84d5..1e69861 100644 --- a/meta/recipes-core/udev/udev/init +++ b/meta/recipes-core/udev/udev/init @@ -69,7 +69,7 @@ case $1 in readfiles /etc/udev/cache.data OLDDATA=$READDATA if [ $OLDDATA = $NEWDATA ]; then -(cd /; tar xf $DEVCACHE /dev/null 21) +(cd /; tar xzf $DEVCACHE /dev/null 21) not_first_boot=1 [ $VERBOSE != no ] echo udev: using cache file $DEVCACHE [ -e /dev/shm/udev.cache ] rm -f /dev/shm/udev.cache diff --git a/meta/recipes-core/udev/udev/udev-cache b/meta/recipes-core/udev/udev/udev-cache index db5a513..3769062 100644 --- a/meta/recipes-core/udev/udev/udev-cache +++ b/meta/recipes-core/udev/udev/udev-cache @@ -25,7 +25,7 @@ fi if [ $DEVCACHE != -a -e /dev/shm/udev.cache ]; then echo Populating dev cache - (cd /; tar cf $DEVCACHE dev) + (cd /; tar czf $DEVCACHE dev) mv /dev/shm/udev.cache /etc/udev/cache.data fi diff --git a/meta/recipes-core/udev/udev/udev-cache.default b/meta/recipes-core/udev/udev/udev-cache.default index 2093336..909ec87 100644 --- a/meta/recipes-core/udev/udev/udev-cache.default +++ b/meta/recipes-core/udev/udev/udev-cache.default @@ -1,5 +1,5 @@ # Default for /etc/init.d/udev # Comment this out to disable device cache -DEVCACHE=/etc/dev.tar +DEVCACHE=/etc/dev.tar.gz PROBE_PLATFORM_BUS=yes -- # Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH v2] wpa-supplicant: use PACKAGECONFIG for ssl selection
From: Yasir-Khan yasir_k...@mentor.com
Select between openssl or gnutls as ssl implementation via
PACKAGECONFIG instead of explicitly adding both via DEPENDS.
Signed-off-by: Yasir-Khan yasir_k...@mentor.com
---
.../wpa-supplicant/wpa-supplicant.inc | 20 +-
.../wpa-supplicant/wpa-supplicant/defconfig-gnutls | 552
.../wpa-supplicant/defconfig-hostapd | 552
3 files changed, 569 insertions(+), 555 deletions(-)
delete mode 100644
meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-gnutls
create mode 100644
meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-hostapd
diff --git a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
index d9c6532..a7e1a16 100644
--- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
+++ b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant.inc
@@ -6,16 +6,20 @@ LICENSE = BSD
LIC_FILES_CHKSUM = file://COPYING;md5=ab87f20cd7e8c0d0a6539b34d3791d0e \
file://README;beginline=1;endline=56;md5=a07250b28e857455336bb59fc31cb845 \
file://wpa_supplicant/wpa_supplicant.c;beginline=1;endline=12;md5=e8e021e30f3a6ab7c341b66b86626a5a
-DEPENDS = gnutls dbus libnl openssl libgcrypt
+DEPENDS = dbus libnl libgcrypt
RRECOMMENDS_${PN} = wpa-supplicant-passphrase wpa-supplicant-cli
+PACKAGECONFIG ??= gnutls
+PACKAGECONFIG[gnutls] = ,,gnutls
+PACKAGECONFIG[ssl] = ,,openssl
+
inherit systemd
SYSTEMD_SERVICE_${PN} = wpa_supplicant.service
wpa_supplicant-nl80211@.service wpa_supplicant-wired@.service
SYSTEMD_AUTO_ENABLE = disable
SRC_URI = http://hostap.epitest.fi/releases/wpa_supplicant-${PV}.tar.gz \
- file://defconfig-gnutls \
+ file://defconfig-hostapd \
file://wpa-supplicant.sh \
file://wpa_supplicant.conf \
file://wpa_supplicant.conf-sane \
@@ -34,8 +38,18 @@ FILES_${PN} += ${datadir}/dbus-1/system-services/*
CONFFILES_${PN} += ${sysconfdir}/wpa_supplicant.conf
do_configure () {
- install -m 0755 ${WORKDIR}/defconfig-gnutls wpa_supplicant/.config
+ install -m 0755 ${WORKDIR}/defconfig-hostapd wpa_supplicant/.config
echo CFLAGS +=\-I${STAGING_INCDIR}/libnl3\ wpa_supplicant/.config
+
+ if echo ${PACKAGECONFIG} | grep -qw ssl; then
+ ssl=openssl
+ elif echo ${PACKAGECONFIG} | grep -qw gnutls; then
+ ssl=gnutls
+ fi
+ if [ -n $ssl ]; then
+ sed -i s/%ssl%/$ssl/ wpa_supplicant/.config
+ fi
+
}
export EXTRA_CFLAGS = ${CFLAGS}
diff --git
a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-gnutls
b/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-gnutls
deleted file mode 100644
index 92ef823..000
--- a/meta/recipes-connectivity/wpa-supplicant/wpa-supplicant/defconfig-gnutls
+++ /dev/null
@@ -1,552 +0,0 @@
-# Example wpa_supplicant build time configuration
-#
-# This file lists the configuration options that are used when building the
-# hostapd binary. All lines starting with # are ignored. Configuration option
-# lines must be commented out complete, if they are not to be included, i.e.,
-# just setting VARIABLE=n is not disabling that variable.
-#
-# This file is included in Makefile, so variables like CFLAGS and LIBS can also
-# be modified from here. In most cases, these lines should use += in order not
-# to override previous values of the variables.
-
-
-# Uncomment following two lines and fix the paths if you have installed OpenSSL
-# or GnuTLS in non-default location
-#CFLAGS += -I/usr/local/openssl/include
-#LIBS += -L/usr/local/openssl/lib
-
-# Some Red Hat versions seem to include kerberos header files from OpenSSL, but
-# the kerberos files are not in the default include path. Following line can be
-# used to fix build issues on such systems (krb5.h not found).
-#CFLAGS += -I/usr/include/kerberos
-
-# Example configuration for various cross-compilation platforms
-
- sveasoft (e.g., for Linksys WRT54G) ##
-#CC=mipsel-uclibc-gcc
-#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
-#CFLAGS += -Os
-#CPPFLAGS += -I../src/include -I../../src/router/openssl/include
-#LIBS += -L/opt/brcm/hndtools-mipsel-uclibc-0.9.19/lib -lssl
-###
-
- openwrt (e.g., for Linksys WRT54G) ###
-#CC=mipsel-uclibc-gcc
-#CC=/opt/brcm/hndtools-mipsel-uclibc/bin/mipsel-uclibc-gcc
-#CFLAGS += -Os
-#CPPFLAGS=-I../src/include -I../openssl-0.9.7d/include \
-# -I../WRT54GS/release/src/include
-#LIBS = -lssl
-###
-
-
-# Driver interface for Host AP driver
-CONFIG_DRIVER_HOSTAP=y
-
-# Driver interface for Agere driver
-#CONFIG_DRIVER_HERMES=y
-#
Re: [OE-core] [PATCH 01/20] udev-cache: Compress the cache
On Tue, Aug 5, 2014 at 4:00 PM, Randy MacLeod randy.macl...@windriver.com wrote: On 14-08-04 02:40 PM, Ben Shelton wrote: From: Richard Tollerton rich.toller...@ni.com $DEVCACHE is observed to be 100k uncompressed; compressing it reduces its size to ~5k. Natinst-Rally-ID: TA44427 Acked-by: Gratian Crisan gratian.cri...@ni.com Natinst-ReviewBoard-ID: 58620 This is a good series of patches; thanks for sending them. It would be nice if you could remove your company's ID tags from the commit log. For example, you create and use could use a YP bugzilla ID ( https://bugzilla.yoctoproject.org/ ) and then match that up in your internal process. I don't think we should ask for this. I saw several of us to include Id tags in past commits (I also did) and I think it is fine. We shouldn't ask an extra step for people to be able to track it (open a YP bugzilla ID issue for example). -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 01/20] udev-cache: Compress the cache
On 14-08-05 04:09 PM, Otavio Salvador wrote: On Tue, Aug 5, 2014 at 4:00 PM, Randy MacLeod randy.macl...@windriver.com wrote: On 14-08-04 02:40 PM, Ben Shelton wrote: From: Richard Tollerton rich.toller...@ni.com $DEVCACHE is observed to be 100k uncompressed; compressing it reduces its size to ~5k. Natinst-Rally-ID: TA44427 Acked-by: Gratian Crisan gratian.cri...@ni.com Natinst-ReviewBoard-ID: 58620 This is a good series of patches; thanks for sending them. It would be nice if you could remove your company's ID tags from the commit log. For example, you create and use could use a YP bugzilla ID ( https://bugzilla.yoctoproject.org/ ) and then match that up in your internal process. I don't think we should ask for this. I saw several of us to include Id tags in past commits (I also did) and I think it is fine. We shouldn't ask an extra step for people to be able to track it (open a YP bugzilla ID issue for example). Wind River patches used to include a CQID tag but we've changed our process to avoid needing such internal tags. If National Instruments can do so as well, that'd be best. I did check my oe-core email list history and this seems like the first patch from NI that has the tags included so I thought I'd reply and see if we can get the tags dropped. Ben, what's the story? -- # Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/2] INITRD commit feedback changes
From: Nitin A Kamble nitin.a.kam...@intel.com Here are couple of commits which enhances the code and documentation referring the recently changed INITRD variable. It is based on the feedback received from Darren Hart. Thanks, Nitin The following changes since commit 870bb8d35547b8313b3a487d7e8b914ab9470e64: local.conf.sample.extended: fix example for EXTRA_USERS_PARAMS (2014-08-04 17:38:24 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib nitin/misc http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=nitin/misc Nitin A Kamble (2): INITRD var: documentation changes code cleanup for INITRD variable handing documentation/ref-manual/ref-classes.xml | 4 ++-- documentation/ref-manual/ref-variables.xml | 2 +- meta/classes/boot-directdisk.bbclass | 4 +++- meta/classes/bootimg.bbclass | 2 ++ meta/conf/documentation.conf | 2 +- 5 files changed, 9 insertions(+), 5 deletions(-) -- 1.8.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] INITRD var: documentation changes
From: Nitin A Kamble nitin.a.kam...@intel.com
The use of the INITRD variable is changed in a recent commit. Instead of
specifying a single filesystem image, it specifies a list of file system
images. Reflecting this change in the documentation.
Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
documentation/ref-manual/ref-classes.xml | 4 ++--
documentation/ref-manual/ref-variables.xml | 2 +-
meta/conf/documentation.conf | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/ref-manual/ref-classes.xml
b/documentation/ref-manual/ref-classes.xml
index e7e9942..91dbfda 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -881,7 +881,7 @@
itemizedlist
listitempara
link linkend='var-INITRD'filenameINITRD/filename/link:
-Indicates a filesystem image to use as an initrd (optional).
+Indicates a list of filesystem images to concatenate and use
as an initrd (optional).
/para/listitem
listitempara
link linkend='var-ROOTFS'filenameROOTFS/filename/link:
@@ -2864,7 +2864,7 @@
The class supports the following variables:
itemizedlist
listitemparaemphasislink
linkend='var-INITRD'filenameINITRD/filename/link:/emphasis
-Indicates a filesystem image to use as an initial RAM disk
+Indicates a list of filesystem images to concatenate and use
as an initial RAM disk
(initrd).
This variable is optional./para/listitem
listitemparaemphasislink
linkend='var-ROOTFS'filenameROOTFS/filename/link:/emphasis
diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index b4d6e71..7808de6 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -4020,7 +4020,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR =
${INC_PR}.3
glossentry id='var-INITRD'glosstermINITRD/glossterm
glossdef
para
-Indicates a filesystem image to use as an initial RAM
+Indicates a list of filesystem images to concatenate and
use as an initial RAM
disk (filenameinitrd/filename).
/para
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index 31fbd6c..eb36de0 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -225,7 +225,7 @@ INHIBIT_PACKAGE_STRIP[doc] = If set to 1, causes the
build to not strip binar
INHERIT[doc] = Causes the named class to be inherited at this point during
parsing. The variable is only valid in configuration files.
INHERIT_DISTRO[doc] = Lists classes that will be inherited at the
distribution level. It is unlikely that you want to edit this variable.
INITRAMFS_FSTYPES[doc] = Defines the format for the output image of an
initial RAM disk (initramfs), which is used during boot.
-INITRD[doc] = Indicates list of filesystem images to concatenate and use as
an initial RAM disk (initrd).
+INITRD[doc] = Indicates a list of filesystem images to concatenate and use as
an initial RAM disk (initrd).
INITSCRIPT_NAME[doc] = The filename of the initialization script as installed
to ${sysconfdir}/init.d.
INITSCRIPT_PACKAGES[doc] = A list of the packages that contain initscripts.
This variable is used in recipes when using update-rc.d.bbclass. The variable
is optional and defaults to the PN variable.
INITSCRIPT_PARAMS[doc] = Specifies the options to pass to update-rc.d. The
variable is mandatory and is used in recipes when using update-rc.d.bbclass.
--
1.8.1.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] code cleanup for INITRD variable handing
From: Nitin A Kamble nitin.a.kam...@intel.com
* Remove an unnecessary check
* Instead of ignoring, report the errors
Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
---
meta/classes/boot-directdisk.bbclass | 4 +++-
meta/classes/bootimg.bbclass | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/classes/boot-directdisk.bbclass
b/meta/classes/boot-directdisk.bbclass
index 995d3e7..5107d7f 100644
--- a/meta/classes/boot-directdisk.bbclass
+++ b/meta/classes/boot-directdisk.bbclass
@@ -76,8 +76,10 @@ boot_direct_populate() {
rm -f $dest/initrd
for fs in ${INITRD}
do
- if [ -n ${fs} ] [ -s ${fs} ]; then
+ if [ -s ${fs} ]; then
cat ${fs} $dest/initrd
+ else
+ bbfatal ${fs} is invalid. initrd image
creation failed.
fi
done
chmod 0644 $dest/initrd
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index 7b3ce65..859d517 100644
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -75,6 +75,8 @@ populate() {
do
if [ -s ${fs} ]; then
cat ${fs} ${DEST}/initrd
+ else
+ bbfatal ${fs} is invalid. initrd image
creation failed.
fi
done
chmod 0644 ${DEST}/initrd
--
1.8.1.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 00/24] wic: Remove unused code
This patchset removes most of code inherited from mic but sitting essentially unused. There's no reason to be carrying it around other than some vague intention of reusing it, but that can still be done - anything needed can alwayse be added back. As it stands, it's only taking up space and obscuring a clear view of what's actually used. Removing the bsp subdir from scripts/lib, and taking a size measurement using 'du -bh lib', we get: before: 1.2M lib after: 393K lib More than half the code remaining after this exercise belongs to the parser and related code, which could presumably be simplified by future patches. [NOTE: the patches in this patchset are too large to post, see URLs below for the actual patches] The following changes since commit 4a226369b7bb37a971c77d4abc88df81033f56c5: dev-manual: Updates for checksums and wic (2014-08-02 10:00:26 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib.git tzanussi/wic-diet-phase1-v0 http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/wic-diet-phase1-v0 Tom Zanussi (24): wic: Make exec_cmd() error out instead of warn wic: Remove unused custom commands wic: Remove packaging, config commands wic: Remove mic bootstrap wic: Remove mic chroot wic: Remove rt_util wic: Remove mic package managers wic: Remove bmap support wic: Remove fiemap support wic: Remove grabber implementation wic: Remove proxy support wic: Remove rpmmisc wic: Remove unused fs_related code wic: Remove unused misc code wic: Remove 3rdparty/urlgrabber wic: Remove unused 3rdparty/commands wic: Remove gpt_parser wic: Remove unused plugin and error code wic: Clean up BaseImageCreator wic: Clean up DirectImageCreator wic: Clean up PartitionedMount wic: Clean up Creator wic: Remove unused command versioning support wic: Update 'Background and Motivation' help section scripts/lib/image/help.py | 14 +- .../mic/3rdparty/pykickstart/commands/__init__.py |8 +- .../3rdparty/pykickstart/commands/authconfig.py| 40 - .../mic/3rdparty/pykickstart/commands/autopart.py | 119 -- .../mic/3rdparty/pykickstart/commands/autostep.py | 55 - .../3rdparty/pykickstart/commands/bootloader.py| 49 - .../mic/3rdparty/pykickstart/commands/clearpart.py | 86 -- .../mic/3rdparty/pykickstart/commands/device.py| 125 -- .../3rdparty/pykickstart/commands/deviceprobe.py | 40 - .../3rdparty/pykickstart/commands/displaymode.py | 68 - .../mic/3rdparty/pykickstart/commands/dmraid.py| 91 -- .../3rdparty/pykickstart/commands/driverdisk.py| 184 --- .../lib/mic/3rdparty/pykickstart/commands/fcoe.py | 114 -- .../mic/3rdparty/pykickstart/commands/firewall.py | 193 --- .../mic/3rdparty/pykickstart/commands/firstboot.py | 62 - .../lib/mic/3rdparty/pykickstart/commands/group.py | 88 -- .../3rdparty/pykickstart/commands/ignoredisk.py| 139 -- .../3rdparty/pykickstart/commands/interactive.py | 58 - .../lib/mic/3rdparty/pykickstart/commands/iscsi.py | 133 -- .../mic/3rdparty/pykickstart/commands/iscsiname.py | 54 - .../lib/mic/3rdparty/pykickstart/commands/key.py | 64 - .../mic/3rdparty/pykickstart/commands/keyboard.py | 55 - .../lib/mic/3rdparty/pykickstart/commands/lang.py | 60 - .../3rdparty/pykickstart/commands/langsupport.py | 58 - .../mic/3rdparty/pykickstart/commands/lilocheck.py | 54 - .../mic/3rdparty/pykickstart/commands/logging.py | 66 - .../mic/3rdparty/pykickstart/commands/logvol.py| 304 .../3rdparty/pykickstart/commands/mediacheck.py| 53 - .../mic/3rdparty/pykickstart/commands/method.py| 186 --- .../mic/3rdparty/pykickstart/commands/monitor.py | 106 -- .../lib/mic/3rdparty/pykickstart/commands/mouse.py | 70 - .../mic/3rdparty/pykickstart/commands/multipath.py | 111 -- .../mic/3rdparty/pykickstart/commands/network.py | 363 - .../mic/3rdparty/pykickstart/commands/partition.py | 39 - .../lib/mic/3rdparty/pykickstart/commands/raid.py | 365 - .../mic/3rdparty/pykickstart/commands/reboot.py| 79 -- .../lib/mic/3rdparty/pykickstart/commands/repo.py | 249 .../mic/3rdparty/pykickstart/commands/rescue.py| 68 - .../mic/3rdparty/pykickstart/commands/rootpw.py| 93 -- .../mic/3rdparty/pykickstart/commands/selinux.py | 64 - .../mic/3rdparty/pykickstart/commands/services.py | 71 - .../lib/mic/3rdparty/pykickstart/commands/skipx.py | 54 - .../lib/mic/3rdparty/pykickstart/commands/sshpw.py | 105 -- .../mic/3rdparty/pykickstart/commands/timezone.py | 86 -- .../mic/3rdparty/pykickstart/commands/updates.py | 60 - .../mic/3rdparty/pykickstart/commands/upgrade.py | 106 -- .../lib/mic/3rdparty/pykickstart/commands/user.py | 173 --- .../lib/mic/3rdparty/pykickstart/commands/vnc.py | 114 -- .../mic/3rdparty/pykickstart/commands/volgroup.py | 102 --
Re: [OE-core] [PATCH 1/2] INITRD var: documentation changes
On 8/5/14, 14:39, Kamble, Nitin A nitin.a.kam...@intel.com wrote: From: Nitin A Kamble nitin.a.kam...@intel.com The use of the INITRD variable is changed in a recent commit. Instead of specifying a single filesystem image, it specifies a list of file system images. Reflecting this change in the documentation. Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com Reviewed-by: Darren Hart dvh...@linux.intel.com -- Darren Hart Open Source Technology Center darren.h...@intel.com Intel Corporation -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] code cleanup for INITRD variable handing
On 8/5/14, 14:39, Kamble, Nitin A nitin.a.kam...@intel.com wrote:
From: Nitin A Kamble nitin.a.kam...@intel.com
* Remove an unnecessary check
* Instead of ignoring, report the errors
This isn't enough to ask for a resend, but please be a bit more explicit
in what is going on in future commit messages, for example:
INITRD: Cleanup file tests and report errors
The null string test (-n) is no longer necessary as it is inherent in the
for loop.
If the INITRD file element is missing or of zero size, abort with bbfatal.
Signed-off-by: Nitin A Kamble nitin.a.kam...@intel.com
Reviewed-by: Darren Hart dvh...@linux.intel.com
---
meta/classes/boot-directdisk.bbclass | 4 +++-
meta/classes/bootimg.bbclass | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/classes/boot-directdisk.bbclass
b/meta/classes/boot-directdisk.bbclass
index 995d3e7..5107d7f 100644
--- a/meta/classes/boot-directdisk.bbclass
+++ b/meta/classes/boot-directdisk.bbclass
@@ -76,8 +76,10 @@ boot_direct_populate() {
rm -f $dest/initrd
for fs in ${INITRD}
do
- if [ -n ${fs} ] [ -s ${fs} ]; then
+ if [ -s ${fs} ]; then
cat ${fs} $dest/initrd
+ else
+ bbfatal ${fs} is invalid. initrd image
creation failed.
fi
done
chmod 0644 $dest/initrd
diff --git a/meta/classes/bootimg.bbclass b/meta/classes/bootimg.bbclass
index 7b3ce65..859d517 100644
--- a/meta/classes/bootimg.bbclass
+++ b/meta/classes/bootimg.bbclass
@@ -75,6 +75,8 @@ populate() {
do
if [ -s ${fs} ]; then
cat ${fs} ${DEST}/initrd
+ else
+ bbfatal ${fs} is invalid. initrd image
creation failed.
fi
done
chmod 0644 ${DEST}/initrd
--
1.8.1.4
--
Darren Hart Open Source Technology Center
darren.h...@intel.com Intel Corporation
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 01/20] udev-cache: Compress the cache
On 08/05, Randy MacLeod wrote: On 14-08-05 04:09 PM, Otavio Salvador wrote: On Tue, Aug 5, 2014 at 4:00 PM, Randy MacLeod randy.macl...@windriver.com wrote: On 14-08-04 02:40 PM, Ben Shelton wrote: From: Richard Tollerton rich.toller...@ni.com $DEVCACHE is observed to be 100k uncompressed; compressing it reduces its size to ~5k. Natinst-Rally-ID: TA44427 Acked-by: Gratian Crisan gratian.cri...@ni.com Natinst-ReviewBoard-ID: 58620 This is a good series of patches; thanks for sending them. It would be nice if you could remove your company's ID tags from the commit log. For example, you create and use could use a YP bugzilla ID ( https://bugzilla.yoctoproject.org/ ) and then match that up in your internal process. I don't think we should ask for this. I saw several of us to include Id tags in past commits (I also did) and I think it is fine. We shouldn't ask an extra step for people to be able to track it (open a YP bugzilla ID issue for example). Wind River patches used to include a CQID tag but we've changed our process to avoid needing such internal tags. If National Instruments can do so as well, that'd be best. I did check my oe-core email list history and this seems like the first patch from NI that has the tags included so I thought I'd reply and see if we can get the tags dropped. Ben, what's the story? In the past, I've stripped the tags before posting the patches. Looks like I forgot this time -- I'll remove the tags when I submit v2 of the patch set. Thanks, Ben -- # Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
