Re: [OE-core] Figuring out why sstate-cache is no longer used for a package
On 10 December 2013 06:44, Mike Looijmans mike.looijm...@topic.nl wrote: The current situation is that a client will grab everything from the buildserver's HTTP sstate-cache, potentially finishing a build from scratch in about five minutes. However, for some reason, the fpga-image does not fall into this category, and eache machine insists on re-building it from scratch. I've been trying to debug this, but the sstate-cache is on another machine. I tried copying part of the build server's sstate-cache onto my machine, but that only results in bitbake-diffsigs -t fpga-image .. yielding ERROR: No sigdata files found matching fpga-image .. so that apparently is a dead end. The trick is to use bitbake -S to write stamp data for a particular image and copy that around. The script sstate-diff-machines can help here. Note that there's been some sstate fallout from the recent optimisations: it was discovered yesterday that sstate hashes using the contains() optimisation wasn't reliable so could produce different hashes on different machines. Try oe-core master from today and see if that's any better: it certainly is for me. Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] bash-completion
Hi, What's the status of this ? Is bash-completion recipe available somewhere? Regards, M -Message d'origine- De : openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org] De la part de Martin Jansa Envoyé : dimanche 21 avril 2013 01:29 À : bitbake-devel Cc : openembedded-core@lists.openembedded.org Objet : Re: [OE-core] bash-completion On Sun, Apr 21, 2013 at 12:56:59AM +0200, Martin Jansa wrote: There is old thread on oe-devel about it http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-December/ 003764.html Is there any reason why it wasn't added to contrib yet? Would it be applied if I send git patch adding it and update commands to include cleansstate and packagedata + new options like -S and maybe more? Or maybe in oe-core/contrib, as list of possible commands is not defined in bitbake. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] Add ability to set clear text password and remove zap_root_password function
From: Chen Qi qi.c...@windriver.com This patchset mainly contains two changes: 1. Add the ability to set clear text password The third patch serves as an example of how to do this in a recipe. An additional patch has been sent to p...@yoctoproject.org, which adds extra information to local.conf.sample.extended about this issue. 2. Remove the zap_root_password function to make things work correctly if 'debug-tweaks' is not in IMAGE_FEATRUES. The following changes since commit 853f5db48f4cfcb34345938b583874fe5b6fc678: nativesdk.bbclass: support nativesdk to override with the PACKAGES_DYNAMIC statement (2013-12-09 21:36:33 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib ChenQi/cleartext-password http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/cleartext-password Chen Qi (3): shadow-native: allow for setting password in clear text image.bbclass: remove zap_root_password useradd-example: add example for setting clear text password .../recipes-skeleton/useradd/useradd-example.bb|3 +- meta/classes/core-image.bbclass|3 - meta/classes/image.bbclass |9 +- .../allow-for-setting-password-in-clear-text.patch | 208 meta/recipes-extended/shadow/shadow.inc|1 + 5 files changed, 212 insertions(+), 12 deletions(-) create mode 100644 meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch -- 1.7.9.5 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] image.bbclass: remove zap_root_password
From: Chen Qi qi.c...@windriver.com
This function replaces the root password with '*' if 'debug-tweaks'
is not in IMAGE_FEATURES. As a result, if we don't have 'debug-tweaks',
we would be locked out of the system. That means, if the user uses a
bbappend file for base-passwd to set the root password, he would not be
able to login as root; if the user uses 'EXTRA_USERS_PARAMS' to set
the root password, he would still not be able to login as root.
In a word, this function should be removed to make things work correctly.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/classes/core-image.bbclass |3 ---
meta/classes/image.bbclass |9 +
2 files changed, 1 insertion(+), 11 deletions(-)
diff --git a/meta/classes/core-image.bbclass b/meta/classes/core-image.bbclass
index e7c34e2..5ee0d6d 100644
--- a/meta/classes/core-image.bbclass
+++ b/meta/classes/core-image.bbclass
@@ -73,8 +73,5 @@ inherit image
# Create /etc/timestamp during image construction to give a reasonably sane
default time setting
ROOTFS_POSTPROCESS_COMMAND += rootfs_update_timestamp ;
-# Zap the root password if debug-tweaks feature is not enabled
-ROOTFS_POSTPROCESS_COMMAND += '${@base_contains(IMAGE_FEATURES,
debug-tweaks, , zap_root_password ; ,d)}'
-
# Tweak the mount options for rootfs in /etc/fstab if read-only-rootfs is
enabled
ROOTFS_POSTPROCESS_COMMAND += '${@base_contains(IMAGE_FEATURES,
read-only-rootfs, read_only_rootfs_hook; , ,d)}'
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 168f283..a5ef244 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -562,13 +562,6 @@ rootfs_uninstall_unneeded () {
fi
}
-# set '*' as the root password so the images
-# can decide if they want it or not
-zap_root_password () {
- sed 's%^root:[^:]*:%root:*:%' ${IMAGE_ROOTFS}/etc/passwd
${IMAGE_ROOTFS}/etc/passwd.new
- mv ${IMAGE_ROOTFS}/etc/passwd.new ${IMAGE_ROOTFS}/etc/passwd
-}
-
# allow dropbear/openssh to accept root logins and logins from accounts with
an empty password string
ssh_allow_empty_password () {
if [ -e ${IMAGE_ROOTFS}${sysconfdir}/ssh/sshd_config ]; then
@@ -648,7 +641,7 @@ rootfs_sysroot_relativelinks () {
sysroot-relativelinks.py ${SDK_OUTPUT}/${SDKTARGETSYSROOT}
}
-EXPORT_FUNCTIONS zap_root_password remove_init_link do_rootfs
make_zimage_symlink_relative set_image_autologin rootfs_update_timestamp
rootfs_no_x_startup
+EXPORT_FUNCTIONS remove_init_link do_rootfs make_zimage_symlink_relative
set_image_autologin rootfs_update_timestamp rootfs_no_x_startup
do_fetch[noexec] = 1
do_unpack[noexec] = 1
--
1.7.9.5
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] useradd-example: add example for setting clear text password
From: Chen Qi qi.c...@windriver.com
Use '-P' option for user3 to set a clear text password. This is supposed
to serve as an example of how to set clear text password in recipes.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
.../recipes-skeleton/useradd/useradd-example.bb|3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
b/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
index 53d2340..2f8d9b0 100644
--- a/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
+++ b/meta-skeleton/recipes-skeleton/useradd/useradd-example.bb
@@ -32,7 +32,8 @@ USERADD_PACKAGES = ${PN} ${PN}-user3
USERADD_PARAM_${PN} = -u 1200 -d /home/user1 -r -s /bin/bash user1; -u 1201
-d /home/user2 -r -s /bin/bash user2
# user3 will be managed in the useradd-example-user3 pacakge:
-USERADD_PARAM_${PN}-user3 = -u 1202 -d /home/user3 -r -s /bin/bash user3
+# As an example, we use the -P option to set clear text password for user3
+USERADD_PARAM_${PN}-user3 = -u 1202 -d /home/user3 -r -s /bin/bash -P 'user3'
user3
# GROUPADD_PARAM works the same way, which you set to the options
# you'd normally pass to the groupadd command. This will create
--
1.7.9.5
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] dhclient-script: let resolv.conf and resolv.conf.dhclient on the same direcotry
On 12/10/2013 12:41 PM, Saul Wold wrote:
On 12/03/2013 05:46 AM, Hongxu Jia wrote:
Even though '/etc' is on the readonly partition, it's possible that
/etc/resolv.conf is on a separate writable partition.
In this situation, we should make sure the temp file
resolv.conf.dhclient
on the same direcotry.
[YOCTO #5624]
Signed-off-by: Hongxu Jia hongxu@windriver.com
---
meta/recipes-connectivity/dhcp/dhcp.inc| 1 +
...ript-let-resolv.conf-and-resolv.conf.dhcl.patch | 74
++
These new scripts are doing alot of out calling from the shell script,
and can cause additional fork/execs during the critical path of system
startup, is there any way to reduce this?
Do you mean the new script :readonly-dhclient-enter-hooks ?
If yes, we could just drop the [PATCH 2/2] patch and it could
work while read-only is enabled;
Because /etc/resolv.conf is a symlink to /var/run/ resolv.conf in
oe-core, and it's always writable:
#ls /etc/resolv.conf -al
lrwxrwxrwx 1 root root 29 Oct 22 2012 /etc/resolv.conf -
/var/run/resolv.conf
//Hongxu
Sau!
2 files changed, 75 insertions(+)
create mode 100644
meta/recipes-connectivity/dhcp/dhcp/dhclient-script-let-resolv.conf-and-resolv.conf.dhcl.patch
diff --git a/meta/recipes-connectivity/dhcp/dhcp.inc
b/meta/recipes-connectivity/dhcp/dhcp.inc
index ad82b57..d8376aa 100644
--- a/meta/recipes-connectivity/dhcp/dhcp.inc
+++ b/meta/recipes-connectivity/dhcp/dhcp.inc
@@ -16,6 +16,7 @@ SRC_URI =
ftp://ftp.isc.org/isc/dhcp/${PV}/dhcp-${PV}.tar.gz \
file://site.h \
file://init-relay file://default-relay \
file://init-server file://default-server \
+ file://dhclient-script-let-resolv.conf-and-resolv.conf.dhcl.patch \
file://dhclient.conf file://dhcpd.conf
inherit autotools
diff --git
a/meta/recipes-connectivity/dhcp/dhcp/dhclient-script-let-resolv.conf-and-resolv.conf.dhcl.patch
b/meta/recipes-connectivity/dhcp/dhcp/dhclient-script-let-resolv.conf-and-resolv.conf.dhcl.patch
new file mode 100644
index 000..db56f70
--- /dev/null
+++
b/meta/recipes-connectivity/dhcp/dhcp/dhclient-script-let-resolv.conf-and-resolv.conf.dhcl.patch
@@ -0,0 +1,74 @@
+dhclient-script: let resolv.conf and resolv.conf.dhclient on the
same direcotry
+
+Even though '/etc' is on the readonly partition, it's possible that
+/etc/resolv.conf is on a separate writable partition.
+
+In this situation, we should make sure the temp file
resolv.conf.dhclient
+on the same direcotry.
+
+Upstream-Status: Pending
+Signed-off-by: Hongxu Jia hongxu@windriver.com
+---
+ client/scripts/linux | 24 +---
+ 1 file changed, 13 insertions(+), 11 deletions(-)
+
+diff --git a/client/scripts/linux b/client/scripts/linux
+index 6f8ea4b..fbc6324 100755
+--- a/client/scripts/linux
b/client/scripts/linux
+@@ -27,27 +27,29 @@ ip=/sbin/ip
+
+ make_resolv_conf() {
+ if [ x$new_domain_name_servers != x ]; then
+-cat /dev/null /etc/resolv.conf.dhclient
+-chmod 644 /etc/resolv.conf.dhclient
++sysconfdir=`dirname $(readlink -f '/etc/resolv.conf')`
++cat /dev/null $sysconfdir/resolv.conf.dhclient
++chmod 644 $sysconfdir/resolv.conf.dhclient
+ if [ x$new_domain_search != x ]; then
+- echo search $new_domain_search /etc/resolv.conf.dhclient
++ echo search $new_domain_search
$sysconfdir/esolv.conf.dhclient
+ elif [ x$new_domain_name != x ]; then
+ # Note that the DHCP 'Domain Name Option' is really just a
domain
+ # name, and that this practice of using the domain name
option as
+ # a search path is both nonstandard and deprecated.
+- echo search $new_domain_name /etc/resolv.conf.dhclient
++ echo search $new_domain_name $sysconfdir/resolv.conf.dhclient
+ fi
+ for nameserver in $new_domain_name_servers; do
+- echo nameserver $nameserver /etc/resolv.conf.dhclient
++ echo nameserver $nameserver $sysconfdir/resolv.conf.dhclient
+ done
+
+-mv /etc/resolv.conf.dhclient /etc/resolv.conf
++mv $sysconfdir/resolv.conf.dhclient $sysconfdir/resolv.conf
+ elif [ x${new_dhcp6_name_servers} != x ] ; then
+-cat /dev/null /etc/resolv.conf.dhclient6
+-chmod 644 /etc/resolv.conf.dhclient6
++sysconfdir=`dirname $(readlink -f '/etc/resolv.conf')`
++cat /dev/null $sysconfdir/resolv.conf.dhclient6
++chmod 644 $sysconfdir/resolv.conf.dhclient6
+
+ if [ x${new_dhcp6_domain_search} != x ] ; then
+- echo search ${new_dhcp6_domain_search}
/etc/resolv.conf.dhclient6
++ echo search ${new_dhcp6_domain_search}
$sysconfdir/resolv.conf.dhclient6
+ fi
+ shopt -s nocasematch
+ for nameserver in ${new_dhcp6_name_servers} ; do
+@@ -59,11 +61,11 @@ make_resolv_conf() {
+ else
+ zone_id=
+ fi
+- echo nameserver ${nameserver}$zone_id
/etc/resolv.conf.dhclient6
++ echo nameserver ${nameserver}$zone_id
$sysconfdir/resolv.conf.dhclient6
+ done
+ shopt -u
Re: [OE-core] [PATCH] boost: Convert ??= weaker assingment to weak ?= assignment
On Mon, 2013-12-09 at 15:11 -0800, Khem Raj wrote:
On Mon, Dec 9, 2013 at 1:51 PM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Mon, 2013-12-09 at 09:34 -0800, Khem Raj wrote:
On Mon, Dec 9, 2013 at 3:48 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
To illustrate why I'm struggling to follow this, bitbake boost -e |
grep BOOST_LIBS on OE-Core does not show python in the list...
I can see it. Its on debian python is 2.7.3
kraj@builder:~$ cat /etc/os-release
PRETTY_NAME=Debian GNU/Linux 7 (wheezy)
NAME=Debian GNU/Linux
VERSION_ID=7
VERSION=7 (wheezy)
ID=debian
ANSI_COLOR=1;31
HOME_URL=http://www.debian.org/;
SUPPORT_URL=http://www.debian.org/support/;
BUG_REPORT_URL=http://bugs.debian.org/;
I doubt its host OS that is causing this, more likely something to do
with the configuration you have (I'm using python 2.7.5+ on Ubuntu
13.10). Which DISTRO is this? Which layers are enabled? Which version of
bitbake?
all is latest from yesterday config wise I am building angstrom. now I did
both
with angstrom and with OE-Core only and you are right it appears to
work with OE-Core alone
see
http://paste.ubuntu.com/6548349/
for angstrom version see
http://paste.ubuntu.com/6548360/
I will dig more into it a bit and see how PACKAGECONFIG can be bad in
angstrom's case
Looking at those pastebins, it shows up as a python function since the
python flag is set. That shouldn't do anything too bad to the variable
though:
python PACKAGECONFIG () {
}
In one case it has the value python, in the other it does not. Its all
very odd. I wonder if bitbake -e shows it taking any value? There has
to be something in the Angstrom setup which is triggering this...
Cheers,
Richard
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] libgcrypt: fix compile error with '-O2' in sysroot path
On Fri, 2013-12-06 at 09:30 +0800, ChenQi wrote: On 12/06/2013 06:41 AM, Saul Wold wrote: On 12/05/2013 12:55 AM, qi.c...@windriver.com wrote: From: Chen Qi qi.c...@windriver.com Characters like '-O2' or '-Ofast' will be replaced by '-O1' when compiling cipher. If we are cross compiling libgcrypt and sysroot contains such characters, we would get compile errors because the sysroot path has been modified. Fix this by adding whitespaces before and after the original matching pattern in the sed command. [YOCTO #5628] Signed-off-by: Chen Qi qi.c...@windriver.com --- ...fix-compile-error-with-O2-in-sysroot-path.patch | 46 meta/recipes-support/libgcrypt/libgcrypt.inc |3 +- 2 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch diff --git a/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch b/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch new file mode 100644 index 000..6b1f119 --- /dev/null +++ b/meta/recipes-support/libgcrypt/files/fix-compile-error-with-O2-in-sysroot-path.patch @@ -0,0 +1,46 @@ +Upstream-Status: Pending + +libgcrypt: fix building error with '-O2' in sysroot path + +Characters like '-O2' or '-Ofast' will be replaced by '-O1' when compiling cipher. +If we are cross compiling libgcrypt and sysroot contains such characters, we would +get compile errors because the sysroot path has been modified. + +Fix this by adding blank spaces before and after the original matching pattern in the +sed command. + +Signed-off-by: Chen Qi qi.c...@windriver.com +--- + cipher/Makefile.am |2 +- + cipher/Makefile.in |2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/cipher/Makefile.am b/cipher/Makefile.am +index 76cdc96..9a89792 100644 +--- a/cipher/Makefile.am b/cipher/Makefile.am +@@ -69,7 +69,7 @@ rfc2268.c \ + camellia.c camellia.h camellia-glue.c + + if ENABLE_O_FLAG_MUNGING +-o_flag_munging = sed -e 's/-O\([2-9s][2-9s]*\)/-O1/' -e 's/-Ofast/-O1/g' ++o_flag_munging = sed -e 's/ -O\([2-9s][2-9s]*\) / -O1 /' -e 's/ -Ofast / -O1 /g' + else + o_flag_munging = cat + endif +diff --git a/cipher/Makefile.in b/cipher/Makefile.in +index 1394d15..6080d59 100644 +--- a/cipher/Makefile.in b/cipher/Makefile.in Why do we need to patch Makefile.in if we are already patching the Makefile.am which will re-generate the Makefile.in Sau! I thought it would do no harm. And I will send this patch to upstream, so it might be a little strange that I only modify the Makefile.am file even if Makefile.in has the same problem. It can actually be harmful since the modification time of Makefile.in can be after the time for Makefile.am and things can go very wrong with autotools when that happens :( Cheers, Richard ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] libgcrypt: fix compile error with '-O2' in sysroot path
On 10 December 2013 11:37, Richard Purdie richard.pur...@linuxfoundation.org wrote: I thought it would do no harm. And I will send this patch to upstream, so it might be a little strange that I only modify the Makefile.am file even if Makefile.in has the same problem. It can actually be harmful since the modification time of Makefile.in can be after the time for Makefile.am and things can go very wrong with autotools when that happens :( Another good reason not to modify the Makefile.in is that being a generated file, updating automake can change how it is generated, so the patch doesn't apply anymore. Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] libmatchbox: fix libpng detection
The configure script looks for libpng12 though pkg-config and if that fails
falls back to looking for library files directly. The result of this is that
the linkage can change between libpng12 or libpng16 depending on what is
installed in the sysroot.
To resolve this, take a patch from upstream to just link using pkg-config.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
.../libmatchbox/libmatchbox/libpng.patch | 69
.../libmatchbox/libmatchbox_1.11.bb|4 +-
2 files changed, 72 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-graphics/libmatchbox/libmatchbox/libpng.patch
diff --git a/meta/recipes-graphics/libmatchbox/libmatchbox/libpng.patch
b/meta/recipes-graphics/libmatchbox/libmatchbox/libpng.patch
new file mode 100644
index 000..8cd507f
--- /dev/null
+++ b/meta/recipes-graphics/libmatchbox/libmatchbox/libpng.patch
@@ -0,0 +1,69 @@
+Upstream-Status: Backport
+Signed-off-by: Ross Burton ross.bur...@intel.com
+
+From 19c3d242034748b3c60765683e1ff4e2df970205 Mon Sep 17 00:00:00 2001
+From: Ross Burton ross.bur...@intel.com
+Date: Tue, 10 Dec 2013 11:37:32 +
+Subject: [PATCH] configure: improve libpng detection
+
+Instead of looking for libpng12 explicitly though pkg-config and then falling
+back to library hunting, just use pkg-config to find libpng which is provided
+by both libpng12 and libpng16.
+
+This also makes the libpng detection deterministic.
+
+Signed-off-by: Ross Burton ross.bur...@intel.com
+---
+ configure.ac | 29 +
+ 1 file changed, 5 insertions(+), 24 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 8a28076..65d7c79 100644
+--- a/configure.ac
b/configure.ac
+@@ -34,7 +34,7 @@ AC_ARG_ENABLE(jpeg,
+ enable_jpeg=$enableval, enable_jpeg=no)
+
+ AC_ARG_ENABLE(png,
+- [ --disable-png disable png support [default=no]],
++ [ --disable-png disable PNG support [default=enabled]],
+ enable_png=$enableval, enable_png=yes )
+
+ AC_ARG_ENABLE(doxygen-docs,
+@@ -156,29 +156,10 @@ fi
+ dnl -- Check for PNG ---
+
+ if test x$enable_png != xno; then
+- AC_MSG_CHECKING(for libpng12)
+- if test x$PKG_CONFIG != xno $PKG_CONFIG --exists libpng12; then
+-AC_MSG_RESULT(yes)
+-PNG_LIBS=`$PKG_CONFIG --libs libpng12`
+- PNG_CFLAGS=`$PKG_CONFIG --cflags libpng12`
+-AC_DEFINE(USE_PNG, [1], [Use Png])
+- SUPPORTS_PNG=1
+- PNG_REQUIRED=libpng12
+- else
+- AC_MSG_RESULT(no)
+-# AC_CHECK_HEADERS(png.h, [ have_png_h=yes ], [ have_png_h=no ] )
+-AC_CHECK_LIB([png], [png_create_read_struct], [have_png=yes],
[have_png=no])
+-
+-if test x$have_png=xyes test x$have_png_h=xyes; then
+-AC_DEFINE(USE_PNG, [1], [Use Png])
+- SUPPORTS_PNG=1
+-PNG_LIBS=-lpng -lz
+-MB_EXTRA_LIBS=$MB_EXTRA_LIBS $PNG_LIBS
+-else
+- AC_MSG_WARN([*** Cannot find PNG, disabling support])
+-enable_png=no
+- fi
+- fi
++ PKG_CHECK_MODULES(PNG, libpng)
++ AC_DEFINE(USE_PNG, [1], [Use PNG])
++ SUPPORTS_PNG=1
++ PNG_REQUIRED=libpng
+ fi
+
+
+--
+1.8.5
+
diff --git a/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
b/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
index d162a78..118c808 100644
--- a/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
+++ b/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
@@ -10,7 +10,9 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34 \
DEPENDS = virtual/libx11 libxext expat libxft jpeg libpng zlib
libxsettings-client startup-notification
-SRC_URI =
http://downloads.yoctoproject.org/releases/matchbox/${BPN}/${PV}/${BPN}-${PV}.tar.bz2;
+SRC_URI =
http://downloads.yoctoproject.org/releases/matchbox/${BPN}/${PV}/${BPN}-${PV}.tar.bz2
\
+ file://libpng.patch
+
SRC_URI[md5sum] = fc6cc807f55a3e7c752d8013176875d7
SRC_URI[sha256sum] =
254cab52e304a3512c8df4be59d690cf3921bbb68a28ede7fe26b93534217b53
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] libmatchbox: use PACKAGECONFIG
Use PACKAGECONFIG to offer some flexibility to the libmatchbox configuration,
and remove two spurious build dependencies (expat and libstartup-notification).
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
b/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
index 118c808..e2e971e 100644
--- a/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
+++ b/meta/recipes-graphics/libmatchbox/libmatchbox_1.11.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34 \
file://libmb/mbexp.c;endline=20;md5=28c0aef3b23e308464f5dae6a11b0d2f \
file://libmb/mbdotdesktop.c;endline=21;md5=5a287156b3207e851c1d68d09c439b51
-DEPENDS = virtual/libx11 libxext expat libxft jpeg libpng zlib
libxsettings-client startup-notification
+DEPENDS = virtual/libx11 libxext
SRC_URI =
http://downloads.yoctoproject.org/releases/matchbox/${BPN}/${PV}/${BPN}-${PV}.tar.bz2
\
file://libpng.patch
@@ -18,4 +18,9 @@ SRC_URI[sha256sum] =
254cab52e304a3512c8df4be59d690cf3921bbb68a28ede7fe26b93534
inherit autotools pkgconfig
-EXTRA_OECONF = --enable-jpeg --enable-xsettings
+PACKAGECONFIG ??= jpeg png xft xsettings
+PACKAGECONFIG[jpeg] = --enable-jpeg,--disable-jpeg,jpeg
+PACKAGECONFIG[pango] = --enable-pango,--disable-pango,pango
+PACKAGECONFIG[png] = --enable-png,--disable-png,libpng
+PACKAGECONFIG[xft] = --enable-xft,--disable-xft,libxft
+PACKAGECONFIG[xsettings] =
--enable-xsettings,--disable-xsettings,libxsettings-client
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Figuring out why sstate-cache is no longer used for a package
On Tue, Dec 10, 2013 at 07:44:49AM +0100, Mike Looijmans wrote: I've been struggling with this for a few days. We have a build server that build various images overnight. One of the packages in that image is fpga-image, which takes more than an hour to build. We have been sharing the the build server's sstate-cache via HTTP and this has worked excellently up until yesterday. The current situation is that a client will grab everything from the buildserver's HTTP sstate-cache, potentially finishing a build from scratch in about five minutes. However, for some reason, the fpga-image does not fall into this category, and eache machine insists on re-building it from scratch. I've been trying to debug this, but the sstate-cache is on another machine. I tried copying part of the build server's sstate-cache onto my machine, but that only results in bitbake-diffsigs -t fpga-image .. yielding ERROR: No sigdata files found matching fpga-image .. so that apparently is a dead end. How can I determine what is causing the system to think that it needs to rebuild this package? I use this script: openembedded-core/scripts/sstate-diff-machines.sh to create backup of sstate signatures and when some next build unexpectedly doesn't reuse some sstate packages I use the script again and compare new and old signatures to see why. As bonus each build which populates out SSTATE_MIRROR also creates tarball with these signatures, so I can easily download one tarball and compare what and why won't be reused from sstate. -- 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
Re: [OE-core] bash-completion
On Tue, Dec 10, 2013 at 09:37:14AM +, Matthieu CRAPET wrote: Hi, What's the status of this ? Is bash-completion recipe available somewhere? I don't know about any change since my question. Are you talking about bash-completion definition for bitbake, right? I wasn't asking about recipe for generic bash-completion. -Message d'origine- De : openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org] De la part de Martin Jansa Envoyé : dimanche 21 avril 2013 01:29 À : bitbake-devel Cc : openembedded-core@lists.openembedded.org Objet : Re: [OE-core] bash-completion On Sun, Apr 21, 2013 at 12:56:59AM +0200, Martin Jansa wrote: There is old thread on oe-devel about it http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-December/ 003764.html Is there any reason why it wasn't added to contrib yet? Would it be applied if I send git patch adding it and update commands to include cleansstate and packagedata + new options like -S and maybe more? Or maybe in oe-core/contrib, as list of possible commands is not defined in bitbake. -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com -- 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] [PATCH 0/1] linux-yocto: static -dev SRCREVs and -headers for klibc
Richard/Saul, Here are a couple of changes that I've been testing locally for a week now, with nothing (obvious) breaking. The linux-yocto-dev kernel change is to allow integration into master under test, so our dev kernels can be exercised directly before they become the kernel for a release. With this change, a layer can now create an optional include file, set a couple of variables and have a set of static REVs used rather than the default of AUTOREV. The linux-libc-headers change fixes a klibc mips build failure issue found by Andrea Adami. This is fixed in the latest kernels, so we'll backport the change to the 3.10 based headers and drop it when I next uprev the kernel and headers. Cheers, Bruce cc: Andrea Adami andrea.ad...@gmail.com The following changes since commit fc1bbe3654a3d456dfeb904f4c9752a03e3c48d6: linux-yocto-dev: allow static SRCREVs via include (2013-12-10 10:06:09 -0500) are available in the git repository at: git://git.pokylinux.org/poky-contrib zedd/kernel http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Bruce Ashfield (1): linux-libc-headers: fix MIPS klibc build error ...lude-asm-byteorder.h-in-linux-raid-md_p.h.patch | 34 ++ .../linux-libc-headers/linux-libc-headers_3.10.bb | 3 ++ 2 files changed, 37 insertions(+) create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch -- 1.8.1.2 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] linux-libc-headers: fix MIPS klibc build error
As reported by Andrea Adami, klibc fails to build for MIPS with the 3.10 libc-headers commit ca044f9a [UAPI: fix endianness conditionals in linux/raid/md_p.h] is the root cause of the breakage. This is fixed in the kernel source itself, but we must also carry the change in the linux-libc-headers recipe, until we update past the 3.13 kernel. With this change, we can again build klibc for mips, with no impact on the rest of the system. cc: Andrea Adami andrea.ad...@gmail.com Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com --- ...lude-asm-byteorder.h-in-linux-raid-md_p.h.patch | 34 ++ .../linux-libc-headers/linux-libc-headers_3.10.bb | 3 ++ 2 files changed, 37 insertions(+) create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch new file mode 100644 index ..1bf0e7ec85f0 --- /dev/null +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch @@ -0,0 +1,34 @@ +From c0f8bd146a8b3e630798561c605f5669823107af Mon Sep 17 00:00:00 2001 +From: Aurelien Jarno aurel...@aurel32.net +Date: Thu, 14 Nov 2013 15:16:19 +1100 +Subject: [PATCH] UAPI: include asm/byteorder.h in linux/raid/md_p.h + +linux/raid/md_p.h is using conditionals depending on endianess and fails +with an error if neither of __BIG_ENDIAN, __LITTLE_ENDIAN or +__BYTE_ORDER are defined, but it doesn't include any header which can +define these constants. This make this header unusable alone. + +This patch adds a #include asm/byteorder.h at the beginning of this +header to make it usable alone. This is needed to compile klibc on MIPS. + +Signed-off-by: Aurelien Jarno aurel...@aurel32.net +Signed-off-by: NeilBrown ne...@suse.de +--- + include/uapi/linux/raid/md_p.h | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/include/uapi/linux/raid/md_p.h b/include/uapi/linux/raid/md_p.h +index fe1a540..f7cf7f3 100644 +--- a/include/uapi/linux/raid/md_p.h b/include/uapi/linux/raid/md_p.h +@@ -16,6 +16,7 @@ + #define _MD_P_H + + #include linux/types.h ++#include asm/byteorder.h + + /* + * RAID superblock. +-- +1.8.1.2 + diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb index 65df230c4b0c..a78d4ba59a62 100644 --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.10.bb @@ -3,6 +3,9 @@ require linux-libc-headers.inc SRC_URI += file://0001-ptrace.h-remove-ptrace_peeksiginfo_args.patch SRC_URI += file://scripts-Makefile.headersinst-install-headers-from-sc.patch +# fixes klibc build for MIPS, drop when libc-headers 3.13 +SRC_URI += file://UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch + SRC_URI[md5sum] = 72d0a9b3e60cd86fabcd3f24b1708944 SRC_URI[sha256sum] = 46c9e55e1fddf40813b8d697d5645037a8e2af5c1a8dff52b3fe82b5021582b8 -- 1.8.1.2 ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/1] linux-yocto: static -dev SRCREVs and -headers for klibc
On Tue, Dec 10, 2013 at 10:16 AM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
Richard/Saul,
Here are a couple of changes that I've been testing locally for a week now,
with nothing (obvious) breaking.
The linux-yocto-dev kernel change is to allow integration into master under
test, so our dev kernels can be exercised directly before they become the
kernel for a release. With this change, a layer can now create an optional
include file, set a couple of variables and have a set of static REVs used
rather than the default of AUTOREV.
I then proceeded to NOT include this patch in my rr directory, so it didn't
get sent.
I've attached it here and it is on the branch I referenced, but let me know
if you'd rather I do a complete resend.
Cheers,
Bruce
The linux-libc-headers change fixes a klibc mips build failure issue found
by Andrea Adami. This is fixed in the latest kernels, so we'll backport
the change to the 3.10 based headers and drop it when I next uprev the
kernel and headers.
Cheers,
Bruce
cc: Andrea Adami andrea.ad...@gmail.com
The following changes since commit fc1bbe3654a3d456dfeb904f4c9752a03e3c48d6:
linux-yocto-dev: allow static SRCREVs via include (2013-12-10 10:06:09
-0500)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-libc-headers: fix MIPS klibc build error
...lude-asm-byteorder.h-in-linux-raid-md_p.h.patch | 34
++
.../linux-libc-headers/linux-libc-headers_3.10.bb | 3 ++
2 files changed, 37 insertions(+)
create mode 100644
meta/recipes-kernel/linux-libc-headers/linux-libc-headers/UAPI-include-asm-byteorder.h-in-linux-raid-md_p.h.patch
--
1.8.1.2
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
From fc1bbe3654a3d456dfeb904f4c9752a03e3c48d6 Mon Sep 17 00:00:00 2001
From: Bruce Ashfield bruce.ashfi...@windriver.com
Date: Thu, 5 Dec 2013 14:31:55 -0500
Subject: [PATCH] linux-yocto-dev: allow static SRCREVs via include
The linux-yocto dev recipe is intended to track the latest revisions of the
kernel tree by default. To control revision churn, and integrate into a
regular build schedule having the ability to specify a set of SRCREVs without
modifying the recipe itself is desired.
So we introduce an optional include file, and variables that control whether
or not the static SRCREVs are used: USE_MACHINE_AUTOREV and USE_META_AUTOREV,
to add this flexibility.
Signed-off-by: Bruce Ashfield bruce.ashfi...@windriver.com
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 25 ++---
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index e7b8d8b2a7a1..e8d14b966d84 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -11,6 +11,12 @@
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
+USE_MACHINE_AUTOREV ?= 1
+USE_META_AUTOREV ?= 1
+
+# provide this .inc to set specific revisions
+include recipes-kernel/linux/linux-yocto-dev-revisions.inc
+
KBRANCH = standard/base
KBRANCH_DEFAULT = ${KBRANCH}
KMETA = meta
@@ -22,15 +28,19 @@ SRC_URI = git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=${KBR
# linux-yocto-dev is the preferred provider, they will be overridden to
# AUTOREV in following anonymous python routine and resolved when the
# variables are finalized.
-SRCREV_machine=29594404d7fe73cd80eaa4ee8c43dcc53970c60e
-SRCREV_meta=29594404d7fe73cd80eaa4ee8c43dcc53970c60e
+SRCREV_machine ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
+SRCREV_meta ?= 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
python () {
if d.getVar(PREFERRED_PROVIDER_virtual/kernel, True) != linux-yocto-dev:
raise bb.parse.SkipPackage(Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-dev to enable it)
else:
-d.setVar(SRCREV_machine, ${AUTOREV})
-d.setVar(SRCREV_meta, ${AUTOREV})
+# if the revisions have been changed from the defaults above we leave them
+# alone. But if the defaults are left, we change to AUTOREV.
+if d.getVar(USE_MACHINE_AUTOREV, True) == 1:
+d.setVar(SRCREV_machine, ${AUTOREV})
+if d.getVar(USE_META_AUTOREV, True) == 1:
+d.setVar(SRCREV_meta, ${AUTOREV})
}
LINUX_VERSION ?= 3.10+
@@ -40,8 +50,9 @@ PV = ${LINUX_VERSION}+git${SRCPV}
COMPATIBLE_MACHINE = (qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64)
# Functionality flags
-KERNEL_FEATURES_append = features/netfilter/netfilter.scc
-KERNEL_FEATURES_append_qemux86= cfg/sound.scc
+KERNEL_EXTRA_FEATURES ?=
Re: [OE-core] Figuring out why sstate-cache is no longer used for a package
On Tue, Dec 10, 2013 at 7:32 AM, Martin Jansa martin.ja...@gmail.comwrote: On Tue, Dec 10, 2013 at 07:44:49AM +0100, Mike Looijmans wrote: I've been struggling with this for a few days. We have a build server that build various images overnight. One of the packages in that image is fpga-image, which takes more than an hour to build. We have been sharing the the build server's sstate-cache via HTTP and this has worked excellently up until yesterday. The current situation is that a client will grab everything from the buildserver's HTTP sstate-cache, potentially finishing a build from scratch in about five minutes. However, for some reason, the fpga-image does not fall into this category, and eache machine insists on re-building it from scratch. I've been trying to debug this, but the sstate-cache is on another machine. I tried copying part of the build server's sstate-cache onto my machine, but that only results in bitbake-diffsigs -t fpga-image .. yielding ERROR: No sigdata files found matching fpga-image .. so that apparently is a dead end. How can I determine what is causing the system to think that it needs to rebuild this package? I use this script: openembedded-core/scripts/sstate-diff-machines.sh to create backup of sstate signatures and when some next build unexpectedly doesn't reuse some sstate packages I use the script again and compare new and old signatures to see why. As bonus each build which populates out SSTATE_MIRROR also creates tarball with these signatures, so I can easily download one tarball and compare what and why won't be reused from sstate. You can also directly use bitbake-whatchanged -v target, with STAMPS_DIR set to the automated build’s stamps directory w/ sstates included. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh script
On 12/07/2013 09:49 AM, Martin Jansa wrote:
* ltp installs 2 different runtests_noltp.sh files from different
directories into /opt/ltp/testcases/bin/runtests_noltp.sh
last one installed wins and causes unexpected changes in
buildhistory's files-in-image.txt report, rename them to have
unique name as other ltp scripts have.
* also define PREFERRED_PROVIDER to resolve note shown when
building with meta-oe layer:
NOTE: multiple providers are available for ltp (ltp, ltp-ddt)
NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta/conf/distro/include/default-providers.inc | 2 ++
...tests_noltp.sh-script-so-have-unique-name.patch | 38 ++
meta/recipes-extended/ltp/ltp_20130904.bb | 4 ++-
3 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
This patch does not appear to apply correctly, I drop into patch resolution:
*** Manual patch resolution mode ***
Dropping to a shell, so patch rejects can be fixed manually.
Run quilt refresh when patch is corrected, press CTRL+D to exit.
Applying patch
0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
patch: Only garbage was found in the patch input.
Patch 0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
does not apply (enforce with -f)
Can you verify this is correct.
Thanks
Sau!
diff --git a/meta/conf/distro/include/default-providers.inc
b/meta/conf/distro/include/default-providers.inc
index d4b9db0..e2b0892 100644
--- a/meta/conf/distro/include/default-providers.inc
+++ b/meta/conf/distro/include/default-providers.inc
@@ -43,3 +43,5 @@ PREFERRED_PROVIDER_udev ?=
${@base_contains('DISTRO_FEATURES','systemd','system
# There are issues with runtime packages and PREFERRED_PROVIDER, see YOCTO
#5044 for details
# on this rather strange entry.
PREFERRED_PROVIDER_bluez4 ?= bluez4
+# Alternative is ltp-ddt in meta-oe:
meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
+PREFERRED_PROVIDER_ltp ?= ltp
diff --git
a/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
b/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
new file mode 100644
index 000..74abe56
--- /dev/null
+++
b/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
@@ -0,0 +1,38 @@
+From 9751a6526cffcdf4e3dc2cb33641259a7be00e19 Mon Sep 17 00:00:00 2001
+From: Martin Jansa martin.ja...@gmail.com
+Date: Sat, 7 Dec 2013 18:24:32 +0100
+Subject: [PATCH] Rename runtests_noltp.sh script so have unique name
+
+* they are installed in the same target path
+ /opt/ltp/testcases/bin/runtests_noltp.sh
+ and overwrite each other in non-deterministic way
+ when multiple processes are used in make install
+
+ ./temp/log.do_install:install -m 00775
+
ltp/20120903-r2/ltp-20120903/testcases/kernel/containers/sysvipc/runtests_noltp.sh
+ltp/20120903-r2/image/opt/ltp/testcases/bin/runtests_noltp.sh
+ ./temp/log.do_install:install -m 00775
+
ltp/20120903-r2/ltp-20120903/testcases/kernel/containers/utsname/runtests_noltp.sh
+ltp/20120903-r2/image/opt/ltp/testcases/bin/runtests_noltp.sh
+
+Upstream-Status: Pending
+
+Signed-off-by: Martin Jansa martin.ja...@gmail.com
+---
+ .../kernel/containers/sysvipc/{runtests_noltp.sh = runipctests_noltp.sh} | 0
+ .../kernel/containers/utsname/{runtests_noltp.sh = runutstests_noltp.sh} | 0
+ 2 files changed, 0 insertions(+), 0 deletions(-)
+ rename testcases/kernel/containers/sysvipc/{runtests_noltp.sh =
runipctests_noltp.sh} (100%)
+ rename testcases/kernel/containers/utsname/{runtests_noltp.sh =
runutstests_noltp.sh} (100%)
+
+diff --git a/testcases/kernel/containers/sysvipc/runtests_noltp.sh
b/testcases/kernel/containers/sysvipc/runipctests_noltp.sh
+similarity index 100%
+rename from testcases/kernel/containers/sysvipc/runtests_noltp.sh
+rename to testcases/kernel/containers/sysvipc/runipctests_noltp.sh
+diff --git a/testcases/kernel/containers/utsname/runtests_noltp.sh
b/testcases/kernel/containers/utsname/runutstests_noltp.sh
+similarity index 100%
+rename from testcases/kernel/containers/utsname/runtests_noltp.sh
+rename to testcases/kernel/containers/utsname/runutstests_noltp.sh
+--
+1.8.4.3
+
diff --git a/meta/recipes-extended/ltp/ltp_20130904.bb
b/meta/recipes-extended/ltp/ltp_20130904.bb
index 5e10448..4722a38 100644
--- a/meta/recipes-extended/ltp/ltp_20130904.bb
+++ b/meta/recipes-extended/ltp/ltp_20130904.bb
@@ -21,7 +21,9 @@ LIC_FILES_CHKSUM =
file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
DEPENDS = attr libaio libcap acl openssl
-SRC_URI = git://github.com/linux-test-project/ltp.git
+SRC_URI = git://github.com/linux-test-project/ltp.git \
+
file://0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch \
Re: [OE-core] [PATCH] ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh script
On Tue, Dec 10, 2013 at 07:41:22AM -0800, Saul Wold wrote:
On 12/07/2013 09:49 AM, Martin Jansa wrote:
* ltp installs 2 different runtests_noltp.sh files from different
directories into /opt/ltp/testcases/bin/runtests_noltp.sh
last one installed wins and causes unexpected changes in
buildhistory's files-in-image.txt report, rename them to have
unique name as other ltp scripts have.
* also define PREFERRED_PROVIDER to resolve note shown when
building with meta-oe layer:
NOTE: multiple providers are available for ltp (ltp, ltp-ddt)
NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp
Signed-off-by: Martin Jansa martin.ja...@gmail.com
---
meta/conf/distro/include/default-providers.inc | 2 ++
...tests_noltp.sh-script-so-have-unique-name.patch | 38
++
meta/recipes-extended/ltp/ltp_20130904.bb | 4 ++-
3 files changed, 43 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
This patch does not appear to apply correctly, I drop into patch resolution:
*** Manual patch resolution mode ***
Dropping to a shell, so patch rejects can be fixed manually.
Run quilt refresh when patch is corrected, press CTRL+D to exit.
Applying patch
0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
patch: Only garbage was found in the patch input.
Patch 0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
does not apply (enforce with -f)
Can you verify this is correct.
I'll send v2 with patch which wasn't created with -M.
I have tested both versions and both work here, but maybe you're using
different PATCHTOOL (well my bitbake -e also shows PATCHTOOL=quilt,
maybe PATCHRESOLVE = noop causes different behavior here).
diff --git a/meta/conf/distro/include/default-providers.inc
b/meta/conf/distro/include/default-providers.inc
index d4b9db0..e2b0892 100644
--- a/meta/conf/distro/include/default-providers.inc
+++ b/meta/conf/distro/include/default-providers.inc
@@ -43,3 +43,5 @@ PREFERRED_PROVIDER_udev ?=
${@base_contains('DISTRO_FEATURES','systemd','system
# There are issues with runtime packages and PREFERRED_PROVIDER, see
YOCTO #5044 for details
# on this rather strange entry.
PREFERRED_PROVIDER_bluez4 ?= bluez4
+# Alternative is ltp-ddt in meta-oe:
meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
+PREFERRED_PROVIDER_ltp ?= ltp
diff --git
a/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
b/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
new file mode 100644
index 000..74abe56
--- /dev/null
+++
b/meta/recipes-extended/ltp/ltp/0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch
@@ -0,0 +1,38 @@
+From 9751a6526cffcdf4e3dc2cb33641259a7be00e19 Mon Sep 17 00:00:00 2001
+From: Martin Jansa martin.ja...@gmail.com
+Date: Sat, 7 Dec 2013 18:24:32 +0100
+Subject: [PATCH] Rename runtests_noltp.sh script so have unique name
+
+* they are installed in the same target path
+ /opt/ltp/testcases/bin/runtests_noltp.sh
+ and overwrite each other in non-deterministic way
+ when multiple processes are used in make install
+
+ ./temp/log.do_install:install -m 00775
+
ltp/20120903-r2/ltp-20120903/testcases/kernel/containers/sysvipc/runtests_noltp.sh
+ltp/20120903-r2/image/opt/ltp/testcases/bin/runtests_noltp.sh
+ ./temp/log.do_install:install -m 00775
+
ltp/20120903-r2/ltp-20120903/testcases/kernel/containers/utsname/runtests_noltp.sh
+ltp/20120903-r2/image/opt/ltp/testcases/bin/runtests_noltp.sh
+
+Upstream-Status: Pending
+
+Signed-off-by: Martin Jansa martin.ja...@gmail.com
+---
+ .../kernel/containers/sysvipc/{runtests_noltp.sh = runipctests_noltp.sh}
| 0
+ .../kernel/containers/utsname/{runtests_noltp.sh = runutstests_noltp.sh}
| 0
+ 2 files changed, 0 insertions(+), 0 deletions(-)
+ rename testcases/kernel/containers/sysvipc/{runtests_noltp.sh =
runipctests_noltp.sh} (100%)
+ rename testcases/kernel/containers/utsname/{runtests_noltp.sh =
runutstests_noltp.sh} (100%)
+
+diff --git a/testcases/kernel/containers/sysvipc/runtests_noltp.sh
b/testcases/kernel/containers/sysvipc/runipctests_noltp.sh
+similarity index 100%
+rename from testcases/kernel/containers/sysvipc/runtests_noltp.sh
+rename to testcases/kernel/containers/sysvipc/runipctests_noltp.sh
+diff --git a/testcases/kernel/containers/utsname/runtests_noltp.sh
b/testcases/kernel/containers/utsname/runutstests_noltp.sh
+similarity index 100%
+rename from testcases/kernel/containers/utsname/runtests_noltp.sh
+rename to testcases/kernel/containers/utsname/runutstests_noltp.sh
+--
+1.8.4.3
+
diff --git a/meta/recipes-extended/ltp/ltp_20130904.bb
[OE-core] Can OE build it's own make?
Hi, I have run into problems with make. Most things works fine with make v3.81 but when building a kernel recipe (meta-fsl-arm linux-imx-3.10.9) I consistently get: make: INTERNAL: Exiting with 5 jobserver tokens available; should be 4! To solve this I manually upgraded make on my machine to v3.82 which soon brought new problems. I then realized that OE-core got a recipe for make v3.82 with a number of patches. After rebuilding make using those patches, everything now seems to work fine :-D. It would be nice, however, if I didn't have to write detailed instructions for everyone on how to patch their machines in order to get their builds to work. Is it possible that OE could build it's own make to use the same way it compiles a new compiler using the existing one? (building make v3.82 using make v3.81 works fine;) BR // Mats ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Can OE build it's own make?
On 10 December 2013 16:36, Mats Kärrman mats.karr...@tritech.se wrote: It would be nice, however, if I didn't have to write detailed instructions for everyone on how to patch their machines in order to get their builds to work. Is it possible that OE could build it's own make to use the same way it compiles a new compiler using the existing one? (building make v3.82 using make v3.81 works fine;) bitbake make-native should be sufficient instructions to build a replacement make. Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] psplash: add support for systems without mmap support.
Signed-off-by: Yevhen Kyriukha kirg...@gmail.com
---
...-support-for-systems-without-mmap-support.patch | 133 +
meta/recipes-core/psplash/psplash_git.bb | 3 +-
2 files changed, 135 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-core/psplash/files/0001-Add-support-for-systems-without-mmap-support.patch
diff --git
a/meta/recipes-core/psplash/files/0001-Add-support-for-systems-without-mmap-support.patch
b/meta/recipes-core/psplash/files/0001-Add-support-for-systems-without-mmap-support.patch
new file mode 100644
index 000..76b21f5
--- /dev/null
+++
b/meta/recipes-core/psplash/files/0001-Add-support-for-systems-without-mmap-support.patch
@@ -0,0 +1,133 @@
+Add support for systems without mmap support.
+
+Patch adds support to display splash image on systems
+where mmap syscall is not available or is not working properly.
+
+Upstream-Status: Pending
+
+Signed-off-by: Yevhen Kyriukha kirg...@gmail.com
+---
+ psplash-fb.c | 24 +---
+ psplash-fb.h |4
+ psplash.c|6 ++
+ 3 files changed, 31 insertions(+), 3 deletions(-)
+
+diff --git a/psplash-fb.c b/psplash-fb.c
+index 71740cd..17893ab 100644
+--- a/psplash-fb.c
b/psplash-fb.c
+@@ -19,12 +19,21 @@
+ void
+ psplash_fb_destroy (PSplashFB *fb)
+ {
++ if (fb-alloc == 1)
++ free(fb-base);
+ if (fb-fd = 0)
+ close (fb-fd);
+
+ free(fb);
+ }
+
++void
++psplash_fb_flush (PSplashFB *fb)
++{
++ if (fb-alloc == 1)
++ pwrite(fb-fd, fb-base, fb-stride * fb-height, 0);
++}
++
+ static int
+ attempt_to_change_pixel_format (PSplashFB *fb,
+ struct fb_var_screeninfo *fb_var)
+@@ -119,6 +128,7 @@ psplash_fb_new (int angle)
+ memset (fb, 0, sizeof(PSplashFB));
+
+ fb-fd = -1;
++ fb-alloc = -1;
+
+ if ((fb-fd = open (fbdev, O_RDWR)) 0)
+ {
+@@ -194,17 +204,25 @@ psplash_fb_new (int angle)
+ DBG(width: %i, height: %i, bpp: %i, stride: %i,
+ fb-width, fb-height, fb-bpp, fb-stride);
+
++ size_t size = fb-stride * fb-height;
++
+ fb-base = (char *) mmap ((caddr_t) NULL,
+ /*fb_fix.smem_len */
+- fb-stride * fb-height,
++ size,
+ PROT_READ|PROT_WRITE,
+ MAP_SHARED,
+ fb-fd, 0);
+
+ if (fb-base == (char *)-1)
+ {
+- perror(Error cannot mmap framebuffer );
+- goto fail;
++ fprintf(stdout, Error cannot mmap framebuffer. Using malloc
instead.\n);
++fb-base = (char*)malloc(size);
++ if (!fb-base)
++{
++ perror(Error cannot allocate memory.);
++ goto fail;
++}
++ fb-alloc = 1;
+ }
+
+ off = (unsigned long) fb_fix.smem_start % (unsigned long) getpagesize();
+diff --git a/psplash-fb.h b/psplash-fb.h
+index ef5b39e..0dbc5ea 100644
+--- a/psplash-fb.h
b/psplash-fb.h
+@@ -48,6 +48,7 @@ typedef struct PSplashFB
+ intgreen_length;
+ intblue_offset;
+ intblue_length;
++ intalloc;
+ }
+ PSplashFB;
+
+@@ -57,6 +58,9 @@ psplash_fb_destroy (PSplashFB *fb);
+ PSplashFB*
+ psplash_fb_new (int angle);
+
++void
++psplash_fb_flush (PSplashFB *fb);
++
+ inline void
+ psplash_fb_plot_pixel (PSplashFB*fb,
+ int x,
+diff --git a/psplash.c b/psplash.c
+index 09cf0d0..524d37d 100644
+--- a/psplash.c
b/psplash.c
+@@ -57,6 +57,8 @@ psplash_draw_msg (PSplashFB *fb, const char *msg)
+ PSPLASH_TEXT_COLOR,
+ radeon_font,
+ msg);
++
++ psplash_fb_flush (fb);
+ }
+
+ void
+@@ -90,6 +92,8 @@ psplash_draw_progress (PSplashFB *fb, int value)
+ PSPLASH_BAR_COLOR);
+ }
+
++ psplash_fb_flush (fb);
++
+ DBG(value: %i, width: %i, barwidth :%i\n, value,
+ width, barwidth);
+ }
+@@ -289,6 +293,8 @@ main (int argc, char** argv)
+
+ psplash_draw_msg (fb, MSG);
+
++ psplash_fb_flush (fb);
++
+ psplash_main (fb, pipe_fd, 0);
+
+
+--
+1.7.9.5
+
diff --git a/meta/recipes-core/psplash/psplash_git.bb
b/meta/recipes-core/psplash/psplash_git.bb
index 1cab296..91c3fef 100644
--- a/meta/recipes-core/psplash/psplash_git.bb
+++ b/meta/recipes-core/psplash/psplash_git.bb
@@ -7,9 +7,10 @@ LIC_FILES_CHKSUM =
file://psplash.h;beginline=1;endline=16;md5=840fb2356b10a85b
SRCREV = afd4e228c606a9998feae44a3fed4474803240b7
PV = 0.1+git${SRCPV}
-PR = r15
+PR = r16
SRC_URI = git://git.yoctoproject.org/${BPN} \
+ file://0001-Add-support-for-systems-without-mmap-support.patch \
file://psplash-init \
${SPLASH_IMAGES}
--
1.8.1.2
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Can OE build it's own make?
On 10 December 2013 17:16, Mats Kärrman mats.karr...@tritech.se wrote: On: Tuesday, December 10, 2013 5:41 PM, Burton, Ross wrote: bitbake make-native should be sufficient instructions to build a replacement make. Ouch, that was simple. Unfortunately the consistently failing build doesn't feel like failing right now so I can't verify that it works. Assuming that it works, I could of course add make-native to the depends of the troublesome recipe but what if I'd like to use the new make for all recipes? Is there somewhere else I could put the dependency to force bitbake to build make first of all? As far as I know there isn't an easy build this first hook as it leads to scary dependency cycles and issues. There's also the buildtools tarball which contains pre-built binaries for most of the tools that we expect the host to have: http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/buildtools/ Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] psplash: add support for systems without mmap support.
Surely if your system has a broken mmap() you've got far bigger problems than the splash screen not working? Also, we're upstream for this so instead of patching the recipe, file a bug with a patch for psplash itself. Ross ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 000/124] [dora] fixes for dora (cover leter only)
On Tuesday 10 December 2013 10:08:10 Robert Yang wrote: * Main changes: - Wic fixes - Update the kernel to 3.10.17 - CVE fixes - Other Bug fixes Note: The PULL is created based on poky, maybe oe-core is preferred ? OE-Core is preferred for the OE-Core parts, yes. I haven't yet looked at all of these, but: Bruce Ashfield (10): kernel: restore scripts in the sysroot Wasn't there a problem with this patch? I can't recall if it was rectified before or after it was merged to master. 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] psplash: add support for systems without mmap support.
2013/12/10 Burton, Ross ross.bur...@intel.com: Surely if your system has a broken mmap() you've got far bigger problems than the splash screen not working? I'm using Intel Cedartrail platform where mmap is not working properly with framebuffer. It's a framebuffer driver problem and such problem may be present on other platforms too. Everything else is working as expected. Also, we're upstream for this so instead of patching the recipe, file a bug with a patch for psplash itself. I had already asked a question here about how I can submit this changes. I was told to send email to someone of developers of psplash. I send email to Richard Purdie but there was no reply. So now I decided to send a patch for psplash recipe. Best regards, Yevhen ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [RFC PATCH 1/2] useradd.bbclass: Fix build time install issues
When the system attempts to populate the sysroot's passwd/group files, it
does so in a single block. However, with the way it was previously
implemented, the system would always run through the code necessary to
populate the sysroot, even in the case of target packages. This had
the side effect that a cross-installed filesystem may not match a
target installed filesystem.
The code was slightly reorganized to ensure that the cross/target installed
pre-install script behavior is the same. It also moves the block that
configures the sysroot parameters to the sysroot specific section of
the code.
Also some minor validation was occuring even on nativesdk packages.
Nativesdk packages should be skipped when processing useradd ops.
Signed-off-by: Mark Hatle mark.ha...@windriver.com
---
meta/classes/useradd.bbclass | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass
index a850e9d..a60ab09 100644
--- a/meta/classes/useradd.bbclass
+++ b/meta/classes/useradd.bbclass
@@ -24,12 +24,11 @@ if test x$D != x; then
# Installing into a sysroot
SYSROOT=$D
OPT=--root $D
+fi
- # Add groups and users defined for all recipe packages
- GROUPADD_PARAM=${@get_all_cmd_params(d, 'groupadd')}
- USERADD_PARAM=${@get_all_cmd_params(d, 'useradd')}
- GROUPMEMS_PARAM=${@get_all_cmd_params(d, 'groupmems')}
-else
+# If we're not doing a special SSTATE/SYSROOT install
+# then set the values, otherwise use the environment
+if test x$UA_SYSROOT = x; then
# Installing onto a target
# Add groups and users defined only for this package
GROUPADD_PARAM=${GROUPADD_PARAM}
@@ -97,6 +96,15 @@ useradd_sysroot () {
# Explicitly set $D since it isn't set to anything
# before do_install
D=${STAGING_DIR_TARGET}
+
+ # Add groups and users defined for all recipe packages
+ GROUPADD_PARAM=${@get_all_cmd_params(d, 'groupadd')}
+ USERADD_PARAM=${@get_all_cmd_params(d, 'useradd')}
+ GROUPMEMS_PARAM=${@get_all_cmd_params(d, 'groupmems')}
+
+ # Tell the system to use the environment vars
+ UA_SYSROOT=1
+
useradd_preinst
}
@@ -137,7 +145,8 @@ def update_useradd_after_parse(d):
bb.fatal(%s inherits useradd but doesn't set USERADD_PARAM,
GROUPADD_PARAM or GROUPMEMS_PARAM for package %s % (d.getVar('FILE'), pkg))
python __anonymous() {
-update_useradd_after_parse(d)
+if not bb.data.inherits_class('nativesdk', d):
+update_useradd_after_parse(d)
}
# Return a single [GROUP|USER]ADD_PARAM formatted string which includes the
--
1.8.1.2.545.g2f19ada
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [RFC PATCH 0/2] RFC: Implement deterministic uid/gid
The following series implements the deterministic uid/gid setting for a distribution. Currently when a filesystem is generated the uid/gid values are generally set at install time, so the install order determines what the actual uid/gid values become. In order to create a deterministic uid/gid set, that still dynamically constructs the passwd/group file, we add an option to read a special passwd/group file to allow the system to determine the values. It uses the existing parameters, and the values from the special passwd/group files to reconstruct the parameter set to ensure these items are fully defined with static values. The first patch (01/02) is generally applicable. It fixes a real bug in the way the user/group adds occur today within the system. Patch 02/02 implements the new functionality. The following changes since commit 8505f0fa48cc79d51616b923c6e2c778c4b46a44: libmatchbox: use PACKAGECONFIG (2013-12-10 14:13:01 +) are available in the git repository at: git://git.yoctoproject.org/poky-contrib mhatle/uidgid http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=mhatle/uidgid Mark Hatle (2): useradd.bbclass: Fix build time install issues useradd.bbclass: Add ability to select a static uid/gid automatically meta/classes/useradd.bbclass | 247 ++- meta/conf/local.conf.sample.extended | 24 2 files changed, 265 insertions(+), 6 deletions(-) -- 1.8.1.2.545.g2f19ada ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [RFC PATCH 2/2] useradd.bbclass: Add ability to select a static uid/gid automatically
[YOCTO #5436]
Automatic selection of static uid/gid is needed for a dynamically generated
passwd and group file to have a deterministic outcome.
When a package is installed and instructs the system to add a new user or
group, unless it selects a static uid/gid value, the next available uid/gid
will be used. The order in which packages are installed is dynamically
computed, and may change from one installation to the next. This results
in a non-deterministic set of uid/gid values.
Enabling USERADD_REWRITE_PARAMS, and providing a preconfigured passwd/group
file will allow the continued dynamic generation of the passwd/group file
on the target, but ensure a deterministic outcome. (Dynamic generation is
desired so that user and groups that have no corresponding functionality
are not present within the final system image.)
Signed-off-by: Mark Hatle mark.ha...@windriver.com
---
meta/classes/useradd.bbclass | 226 +++
meta/conf/local.conf.sample.extended | 24
2 files changed, 250 insertions(+)
diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass
index a60ab09..7f2c6e8 100644
--- a/meta/classes/useradd.bbclass
+++ b/meta/classes/useradd.bbclass
@@ -144,9 +144,235 @@ def update_useradd_after_parse(d):
if not d.getVar('USERADD_PARAM_%s' % pkg, True) and not
d.getVar('GROUPADD_PARAM_%s' % pkg, True) and not d.getVar('GROUPMEMS_PARAM_%s'
% pkg, True):
bb.fatal(%s inherits useradd but doesn't set USERADD_PARAM,
GROUPADD_PARAM or GROUPMEMS_PARAM for package %s % (d.getVar('FILE'), pkg))
+# In order to support a deterministic set of 'dynamic' users/groups,
+# we need a function to reformat the params based on a static file
+def update_useradd_static_config(d):
+import argparse
+import re
+
+class myArgumentParser( argparse.ArgumentParser ):
+def _print_message(self, message, file=None):
+bb.warn(%s - %s: %s % (d.getVar('PN', True), pkg, message))
+
+# This should never be called...
+def exit(self, status=0, message=None):
+message = message or (%s - %s: useradd.bbclass: Argument parsing
exited % (d.getVar('PN', True), pkg))
+error(message)
+
+def error(self, message):
+raise bb.build.FuncFailed(message)
+
+# We parse and rewrite the useradd components
+def rewrite_useradd(params):
+# The following comes from --help on useradd from shadow
+parser = myArgumentParser(prog='useradd')
+parser.add_argument(-b, --base-dir, metavar=BASE_DIR, help=base
directory for the home directory of the new account)
+parser.add_argument(-c, --comment, metavar=COMMENT, help=GECOS
field of the new account)
+parser.add_argument(-d, --home-dir, metavar=HOME_DIR, help=home
directory of the new account)
+parser.add_argument(-D, --defaults, help=print or change default
useradd configuration, action=store_true)
+parser.add_argument(-e, --expiredate, metavar=EXPIRE_DATE,
help=expiration date of the new account)
+parser.add_argument(-f, --inactive, metavar=INACTIVE,
help=password inactivity period of the new account)
+parser.add_argument(-g, --gid, metavar=GROUP, help=name or ID
of the primary group of the new account)
+parser.add_argument(-G, --groups, metavar=GROUPS, help=list of
supplementary groups of the new account)
+parser.add_argument(-k, --skel, metavar=SKEL_DIR, help=use this
alternative skeleton directory)
+parser.add_argument(-K, --key, metavar=KEY=VALUE, help=override
/etc/login.defs defaults)
+parser.add_argument(-l, --no-log-init, help=do not add the user
to the lastlog and faillog databases, action=store_true)
+parser.add_argument(-m, --create-home, help=create the user's
home directory, action=store_true)
+parser.add_argument(-M, --no-create-home, help=do not create the
user's home directory, action=store_true)
+parser.add_argument(-N, --no-user-group, help=do not create a
group with the same name as the user, action=store_true)
+parser.add_argument(-o, --non-unique, help=allow to create users
with duplicate (non-unique UID), action=store_true)
+parser.add_argument(-p, --password, metavar=PASSWORD,
help=encrypted password of the new account)
+parser.add_argument(-R, --root, metavar=CHROOT_DIR,
help=directory to chroot into)
+parser.add_argument(-r, --system, help=create a system account,
action=store_true)
+parser.add_argument(-s, --shell, metavar=SHELL, help=login
shell of the new account)
+parser.add_argument(-u, --uid, metavar=UID, help=user ID of the
new account)
+parser.add_argument(-U, --user-group, help=create a group with
the same name as the user, action=store_true)
+parser.add_argument(LOGIN, help=Login name of the new user)
+
+# Return a list of configuration files based on either the default
+#
Re: [OE-core] Can OE build it's own make?
You need to do a number of things anyway to prepare a machine for building openembedded. I have a git repository containing a script which will install all the packages I want to have on my machine. It will also build new versions of some applications. When I install a new Ubuntu machine, i manually add synaptic, then add gnome + git + ssh keys. Then I download the script and let it run. Suggest you adopt a similar approach. Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 10 dec 2013 kl. 17:36 skrev Mats Kärrman mats.karr...@tritech.se: Hi, I have run into problems with make. Most things works fine with make v3.81 but when building a kernel recipe (meta-fsl-arm linux-imx-3.10.9) I consistently get: make: INTERNAL: Exiting with 5 jobserver tokens available; should be 4! To solve this I manually upgraded make on my machine to v3.82 which soon brought new problems. I then realized that OE-core got a recipe for make v3.82 with a number of patches. After rebuilding make using those patches, everything now seems to work fine :-D. It would be nice, however, if I didn't have to write detailed instructions for everyone on how to patch their machines in order to get their builds to work. Is it possible that OE could build it's own make to use the same way it compiles a new compiler using the existing one? (building make v3.82 using make v3.81 works fine;) BR // Mats ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] dpkg: upgrade to 1.17.4
Signed-off-by: Saul Wold s...@linux.intel.com
---
meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb = dpkg_1.17.4.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb = dpkg_1.17.4.bb} (75%)
diff --git a/meta/recipes-devtools/dpkg/dpkg_1.17.1.bb
b/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
similarity index 75%
rename from meta/recipes-devtools/dpkg/dpkg_1.17.1.bb
rename to meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
index 525f759..9e2392c 100644
--- a/meta/recipes-devtools/dpkg/dpkg_1.17.1.bb
+++ b/meta/recipes-devtools/dpkg/dpkg_1.17.4.bb
@@ -11,6 +11,6 @@ SRC_URI += file://noman.patch \
file://arch_pm.patch \
-SRC_URI[md5sum] = ece3ae87a099158c17bde95c0036c575
-SRC_URI[sha256sum] =
8912ea77bc9c14297c0a340f5f461fbd212582ce814e1805d1d0436ca885e3a1
+SRC_URI[md5sum] = cc25086e1e3bd9512a95f14cfe9002e1
+SRC_URI[sha256sum] =
01cdc81c33e77c3d7c40df17e19171794542be7cf12e411381ffcaa8f87b1854
--
1.8.3.1
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] Package Updates
Did a build with debian packaging and tested dpkg lightly on the target.
Sau!
The following changes since commit 315367ea9526186d5836c64867ce0cd40d9d8412:
nativesdk.bbclass: support nativesdk to override with the PACKAGES_DYNAMIC
statement (2013-12-09 21:36:30 +)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib sgw/updates
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates
Saul Wold (3):
util-macros: upgrade to 1.18.0
dpkg: upgrade to 1.17.4
cracklib: upgrade to 2.9.1
meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb = dpkg_1.17.4.bb} | 4 ++--
.../cracklib/{cracklib_2.9.0.bb = cracklib_2.9.1.bb} | 4 ++--
.../xorg-util/{util-macros_1.17.1.bb = util-macros_1.18.0.bb}| 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
rename meta/recipes-devtools/dpkg/{dpkg_1.17.1.bb = dpkg_1.17.4.bb} (75%)
rename meta/recipes-extended/cracklib/{cracklib_2.9.0.bb = cracklib_2.9.1.bb}
(84%)
rename meta/recipes-graphics/xorg-util/{util-macros_1.17.1.bb =
util-macros_1.18.0.bb} (75%)
--
1.8.3.1
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] util-macros: upgrade to 1.18.0
Signed-off-by: Saul Wold s...@linux.intel.com
---
.../xorg-util/{util-macros_1.17.1.bb = util-macros_1.18.0.bb}| 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/xorg-util/{util-macros_1.17.1.bb =
util-macros_1.18.0.bb} (75%)
diff --git a/meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb
b/meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
similarity index 75%
rename from meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb
rename to meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
index 9274a3a..79759f6 100644
--- a/meta/recipes-graphics/xorg-util/util-macros_1.17.1.bb
+++ b/meta/recipes-graphics/xorg-util/util-macros_1.18.0.bb
@@ -15,5 +15,5 @@ RRECOMMENDS_${PN}-dbg = ${PN}-dev (= ${EXTENDPKGV})
BBCLASSEXTEND = native nativesdk
-SRC_URI[md5sum] = 886de1940334e097c5f66233a8393122
-SRC_URI[sha256sum] =
67bd01d5f4713c9e9d57dc742504d06292dd9c4fb73041ea16fed034c56c622a
+SRC_URI[md5sum] = fd0ba21b3179703c071bbb4c3e5fb0f4
+SRC_URI[sha256sum] =
cf4ab0e17bfee0f7689cdcff8c7d7f164c9a710f851f91c488f5cd81fac9c0aa
--
1.8.3.1
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] cracklib: upgrade to 2.9.1
Signed-off-by: Saul Wold s...@linux.intel.com
---
.../cracklib/{cracklib_2.9.0.bb = cracklib_2.9.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/cracklib/{cracklib_2.9.0.bb = cracklib_2.9.1.bb}
(84%)
diff --git a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
b/meta/recipes-extended/cracklib/cracklib_2.9.1.bb
similarity index 84%
rename from meta/recipes-extended/cracklib/cracklib_2.9.0.bb
rename to meta/recipes-extended/cracklib/cracklib_2.9.1.bb
index bbf88bb..5e6156f 100644
--- a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
+++ b/meta/recipes-extended/cracklib/cracklib_2.9.1.bb
@@ -13,8 +13,8 @@ SRC_URI =
${SOURCEFORGE_MIRROR}/cracklib/cracklib-${PV}.tar.gz \
file://0001-packlib.c-support-dictionary-byte-order-dependent.patch
\
file://0002-craklib-fix-testnum-and-teststr-failed.patch
-SRC_URI[md5sum] = e0f94ac2138fd33c7e77b19c1e9a9390
-SRC_URI[sha256sum] =
17fecdfa78c0b9b47afa1533ea99b5351c3cef770bbd9c8c34391827efecbdc0
+SRC_URI[md5sum] = 90536219c520add2ceb3c26f0d7da404
+SRC_URI[sha256sum] =
408905c2539a97dc8cbbb6d7cd2046cb5647a345b4bda399220d9471be16d156
inherit autotools gettext
--
1.8.3.1
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] insane: handle recursive configures when checking for unknown configure options
Some recipes have configure scripts that recursively call other configure
scripts (e.g. dropbear). These multiple-line matches were not being handled
correctly, so iterate over every matching line instead of assuming only one line
was found.
[ YOCTO #5646 ]
Signed-off-by: Ross Burton ross.bur...@intel.com
---
meta/classes/insane.bbclass |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index a51f504..e77e993 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -941,8 +941,10 @@ Missing inherit gettext? % (gt, config))
try:
flag = WARNING: unrecognized options:
log = os.path.join(d.getVar('B', True), 'config.log')
-output = subprocess.check_output(['grep', '-F', flag, log])
-options = set(map(lambda s: s.strip(' ,'),
output.partition(flag)[2].split()))
+output = subprocess.check_output(['grep', '-F', flag,
log]).replace(', ', ' ')
+options = set()
+for line in output.splitlines():
+options |= set(line.partition(flag)[2].split())
whitelist = set(d.getVar(UNKNOWN_CONFIGURE_WHITELIST,
True).split())
options -= whitelist
if options:
--
1.7.10.4
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] lsb: update directory of install_initd and remove_initd
On 11/13/2013 12:27 AM, Kai Kang wrote:
According to LSB specification:
http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/installinitd.html
http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/removeinitd.html
commands install_initd and remove_initd should under directory /usr/lib/lsb/.
lsb recipe creates these commands under directory ${libdir} which may
expand to /usr/lib64 when multilib is enabled on qemux86-64. That will
cause LSB command check for install_initd and remove_initd fail. So
correct it.
Signed-off-by: Kai Kang kai.k...@windriver.com
---
meta/recipes-extended/lsb/lsb_4.1.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-extended/lsb/lsb_4.1.bb
b/meta/recipes-extended/lsb/lsb_4.1.bb
index c80ff59..8105e59 100644
--- a/meta/recipes-extended/lsb/lsb_4.1.bb
+++ b/meta/recipes-extended/lsb/lsb_4.1.bb
@@ -79,8 +79,8 @@ do_install_append(){
# creat links for LSB test
install -d ${D}/${libdir}/lsb
- ln -sf ${sbindir}/chkconfig ${D}/${libdir}/lsb/install_initd
- ln -sf ${sbindir}/chkconfig ${D}/${libdir}/lsb/remove_initd
+ ln -sf ${sbindir}/chkconfig ${D}/usr/lib/lsb/install_initd
+ ln -sf ${sbindir}/chkconfig ${D}/usr/lib/lsb/remove_initd
It's arguable that this should be ${prefix}/lib since there is a
possibly case of libdir not being /usr/lib or /usr/lib64. It also goes
to LSB explictly requires /usr/lib/lsb so for an LSB machine /usr/lib
will aways exist.
I will put this in the next C-Pull.
Sau!
ln -sf ${sbindir}/sendmail ${D}/${libdir}/sendmail
if [ ${TARGET_ARCH} = x86_64 ];then
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [V3 1/2] bluez4: Install the test script
On 11/19/2013 01:18 AM, hongbo zhong wrote:
From: Zhong Hongbo hongbo.zh...@windriver.com
Signed-off-by: Zhong Hongbo hongbo.zh...@windriver.com
---
.../bluez/bluez4-4.101/install-test-script.patch | 26
meta/recipes-connectivity/bluez/bluez4_4.101.bb|6 -
2 files changed, 31 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-connectivity/bluez/bluez4-4.101/install-test-script.patch
diff --git
a/meta/recipes-connectivity/bluez/bluez4-4.101/install-test-script.patch
b/meta/recipes-connectivity/bluez/bluez4-4.101/install-test-script.patch
new file mode 100644
index 000..23f7d99
--- /dev/null
+++ b/meta/recipes-connectivity/bluez/bluez4-4.101/install-test-script.patch
@@ -0,0 +1,26 @@
+Upstream-Status: Inappropriate
+
+Install the bluez's test scripts
+
+Signed-off-by: Zhong Hongbo hongbo.zh...@windriver.com
+diff -Nurd bluez-4.101.orig/Makefile.tools bluez-4.101/Makefile.tools
+--- bluez-4.101.orig/Makefile.tools2013-11-19 15:49:07.688838000 +0800
bluez-4.101/Makefile.tools 2013-11-19 15:50:09.256837848 +0800
+@@ -227,6 +227,17 @@
+ test/service-spp.xml test/service-opp.xml test/service-ftp.xml \
+ test/simple-player test/test-nap
+
++bluez4_testdir = $(libdir)/bluez4/test/
++dist_bluez4_test_SCRIPTS = test/sap-client test/hsplay test/hsmicro \
++ test/monitor-bluetooth test/list-devices \
++ test/test-discovery test/test-manager test/test-adapter \
++ test/test-device test/test-service test/test-serial \
++ test/test-telephony test/test-network test/simple-agent \
++ test/simple-service test/simple-endpoint test/test-audio \
++ test/test-input test/test-sap-server test/test-oob \
++ test/test-attrib test/test-proximity test/test-thermometer \
++ test/test-serial-proxy test/test-health test/test-health-sink \
++ test/simple-player test/test-nap
+ if HIDD
+ bin_PROGRAMS += compat/hidd
+
diff --git a/meta/recipes-connectivity/bluez/bluez4_4.101.bb
b/meta/recipes-connectivity/bluez/bluez4_4.101.bb
index d6c3e26..7127619 100644
--- a/meta/recipes-connectivity/bluez/bluez4_4.101.bb
+++ b/meta/recipes-connectivity/bluez/bluez4_4.101.bb
@@ -7,6 +7,7 @@ SRC_URI += file://bluetooth.conf \
file://fix-udev-paths.patch \
file://obsolete_automake_macros.patch \
file://network-fix-network-Connect-method-parameters.patch \
+file://install-test-script.patch \
SRC_URI[md5sum] = fb42cb7038c380eb0e2fa208987c96ad
@@ -23,9 +24,10 @@ do_install_append() {
}
RDEPENDS_${PN}-dev = bluez-hcidump
+RDEPENDS_${PN}-testtools += python python-dbus python-pygobject
ALLOW_EMPTY_libasound-module-bluez = 1
-PACKAGES =+ libasound-module-bluez
+PACKAGES =+ libasound-module-bluez ${PN}-testtools
I am not sure this will do the right thing, have you verified that the
testtools packages actually gets populated? I ask since this line will
add ${PN}-testtools after ${PN} and unless you excplictly override
FILES_${PN}, it will greedily grab the ${libdir}/${BPN}/* files which in
this case includes the test directory listed below.
Sau!
FILES_libasound-module-bluez = ${libdir}/alsa-lib/lib*.so ${datadir}/alsa
FILES_${PN} += ${libdir}/bluetooth/plugins ${libdir}/bluetooth/plugins/*.so
${base_libdir}/udev/ ${nonarch_base_libdir}/udev/ ${systemd_unitdir}/
${datadir}/dbus-1
@@ -34,6 +36,8 @@ FILES_${PN}-dev += \
${libdir}/alsa-lib/*.la \
+FILES_${PN}-testtools = ${libdir}/bluez4/test/*
+
FILES_${PN}-dbg += \
${libdir}/bluetooth/plugins/.debug \
${libdir}/*/.debug \
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] json-glib: enable ptest
Found this in my backlog queue, it does not apply to master currently,
please verify it and resend.
Thanks
Sau!
On 11/21/2013 10:07 AM, Ross Burton wrote:
Use a patch from upstream to install the test suite and add the minimal logic to
integrate it with ptest.
Signed-off-by: Ross Burton ross.bur...@intel.com
---
.../json-glib/json-glib/install-tests.patch| 186
meta/recipes-gnome/json-glib/json-glib/run-ptest |3 +
meta/recipes-gnome/json-glib/json-glib_0.16.2.bb | 13 +-
3 files changed, 200 insertions(+), 2 deletions(-)
create mode 100644 meta/recipes-gnome/json-glib/json-glib/install-tests.patch
create mode 100644 meta/recipes-gnome/json-glib/json-glib/run-ptest
diff --git a/meta/recipes-gnome/json-glib/json-glib/install-tests.patch
b/meta/recipes-gnome/json-glib/json-glib/install-tests.patch
new file mode 100644
index 000..4bd9764
--- /dev/null
+++ b/meta/recipes-gnome/json-glib/json-glib/install-tests.patch
@@ -0,0 +1,186 @@
+Upstream-Status: Backport
+Signed-off-by: Ross Burton ross.bur...@intel.com
+
+From 3e9858cb9c34f492ad0859bd262c8c4691260b41 Mon Sep 17 00:00:00 2001
+From: Emmanuele Bassi eba...@gnome.org
+Date: Thu, 16 May 2013 23:27:56 +0100
+Subject: [PATCH] build: Add --enable-installed-tests
+
+See https://live.gnome.org/GnomeGoals/InstalledTests for more
+information.
+
+It's still possible to run `make check` with locally uninstalled tests.
+---
+ .gitignore |1 +
+ configure.ac| 16 ++-
+ json-glib/tests/Makefile.am | 46 +++
+ json-glib/tests/parser.c| 24 +++---
+ 4 files changed, 75 insertions(+), 12 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index a84dbb3..54b9706 100644
+--- a/configure.ac
b/configure.ac
+@@ -160,6 +160,19 @@ AS_IF([test x$enable_maintainer_flags = xyes test x$GCC =
xyes],
+ MAINTAINER_CFLAGS=${MAINTAINER_CFLAGS#* }
+ AC_SUBST([MAINTAINER_CFLAGS])
+
++dnl === Test suite
++
++AC_ARG_ENABLE(modular_tests,
++ AS_HELP_STRING([--disable-modular-tests],
++ [Disable build of test programs (default: no)]),,
++ [enable_modular_tests=yes])
++AC_ARG_ENABLE(installed_tests,
++ AS_HELP_STRING([--enable-installed-tests],
++ [Install test programs (default: no)]),,
++ [enable_installed_tests=no])
++AM_CONDITIONAL(BUILD_MODULAR_TESTS, test x$enable_modular_tests = xyes ||
test x$enable_installed_tests=xyes)
++AM_CONDITIONAL(BUILDOPT_INSTALL_TESTS, test x$enable_installed_tests = xyes)
++
+ dnl === Test coverage
=
+
+ AC_ARG_ENABLE([gcov],
+@@ -297,7 +310,8 @@ echo • Compiler flags: ${CFLAGS} ${MAINTAINER_CFLAGS}
+ echo
+ echo • API reference: ${enable_gtk_doc}
+ echo
+-echo • Enable test suite: ${enable_glibtest}
++echo • Enable test suite: ${enable_modular_tests}
++echo • Install tests: ${enable_installed_tests}
+ echo • Build introspection data: ${enable_introspection}
+ echo • Enable test coverage: ${use_gcov}
+ echo
+diff --git a/json-glib/tests/Makefile.am b/json-glib/tests/Makefile.am
+index 9815b95..23a93d6 100644
+--- a/json-glib/tests/Makefile.am
b/json-glib/tests/Makefile.am
+@@ -5,22 +5,23 @@ NULL =
+
+ DISTCLEANFILES =
+
+-INCLUDES = \
+- -I$(top_srcdir) \
+- -I$(top_srcdir)/json-glib \
++insttestdir=$(pkglibexecdir)/installed-tests
++
++AM_CPPFLAGS = \
++ $(JSON_DEBUG_CFLAGS) \
++ -DTESTS_DATA_DIR=\$(top_srcdir)/json-glib/tests\ \
++ -I$(top_srcdir) \
++ -I$(top_srcdir)/json-glib \
+ $(NULL)
+
+-AM_CPPFLAGS = $(JSON_DEBUG_CFLAGS)
-DTESTS_DATA_DIR=\$(top_srcdir)/json-glib/tests\
+ AM_CFLAGS = -g $(JSON_CFLAGS) $(MAINTAINER_CFLAGS)
++
+ LDADD = \
+ ../libjson-glib-1.0.la \
+ $(JSON_LIBS) \
+ $(NULL)
+
+-EXTRA_DIST += stream-load.json
+-
+-noinst_PROGRAMS = $(TEST_PROGS)
+-TEST_PROGS += \
++all_test_programs = \
+ array \
+ boxed \
+ builder \
+@@ -37,4 +38,33 @@ TEST_PROGS += \
+ serialize-full \
+ $(NULL)
+
++test_files = \
++ stream-load.json\
++ $(NULL)
++
++if BUILD_MODULAR_TESTS
++TEST_PROGS += $(all_test_programs)
++noinst_PROGRAMS = $(TEST_PROGS)
++endif
++
++if BUILDOPT_INSTALL_TESTS
++insttest_PROGRAMS = $(all_test_programs)
++
++testmetadir = $(datadir)/installed-tests/$(PACKAGE)
++testmeta_DATA = $(all_test_programs:=.test)
++
++testdatadir=$(insttestdir)
++testdata_DATA = $(test_files)
++
++testdata_SCRIPTS = $(test_script_files)
++endif
++
++EXTRA_DIST += $(test_files)
++
++%.test: % Makefile
++ $(AM_V_GEN) (echo '[Test]' $@.tmp; \
++ echo 'Type=session' $@.tmp; \
++ echo 'Exec=env
Re: [OE-core] [PATCH 000/124] [dora] fixes for dora (cover leter only)
On 12/10/2013 07:08 AM, Robert Yang wrote: * Main changes: - Wic fixes - Update the kernel to 3.10.17 - CVE fixes - Other Bug fixes Note: The PULL is created based on poky, maybe oe-core is preferred ? As Paul already pointed out this should be oe-core based if possible. I started a build of robert/dora-next branch. While this list looks long nothing immediately jumps out at me as flagged. I would as that you verify you have collected as many of the patches from the mailing list that wanted to be in dora that are either in master or you needed to merge separately. Check below for an additional question about lttng-modules update Sau! // Robert The following changes since commit 53d2563ff13fcec74d4250bef5419e36169e55cc: bitbake: perforce: Fix path subdirectory issues (2013-12-03 17:51:31 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib robert/dora-next-oecore http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/dora-next-oecore Amy Fong (1): native-python: bad interpreter error message Andreas Müller (1): systemd-compat-units: run-postinsts fix script link Andreas Oberritter (1): cogl-1.0: depend on virtual/mesa Baogen Shang (2): libtiff: CVE-2013-4232 libtiff: CVE-2013-4243 Bruce Ashfield (10): kernel: restore scripts in the sysroot linux-yocto/3.10: MinnowBoard support linux-yocto-3.10: bump to 3.10.17 and -rt11 linux-yocto/3.10: haswell-wc and crystalforest support linux-yocto/3.8: add crystalforest bsp legacy block drivers configurations linux-yocto/3.10: common-pc: add missing dependencies for BRCMSMAC linux-yocto/3.10: fix qemuarm boot and spurious mips build warning linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard linux-yocto-rt/3.10: fix ntp merge issue linux-yocto/3.10: meta: ARM: OMAP3: Add USB PHY driver for Beagleboard Chen Qi (7): device_table-minimal.txt: change group of /dev/hda back to disk runqemu-extract-sdk: add --numeric-owner option to tar command extrausers.bbclass: avoid infinite loop bootlogd: create log file if not present license.bbclass: fix missing of license files on ubuntu build host sysvinit: use ALTERNATIVE to manage sulogin nfs-utils: explicitly rdepend on bash Christopher Larson (1): base.bbclass: fix nondeterministic PACKAGECONFIG processing order Chunrong Guo (1): mdadm: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for powerpc64 Darren Hart (2): wic: Force lba off for FAT16 partitions wic: Check for external modules Gary Thomas (1): core-image-basic.bb: Allow user extensions Hans Beckerus (1): initscripts: add missing dmesg.sh to run-level S Hongxu Jia (1): debugedit: fix segment fault while file's bss offset have a large number Jack Mitchell (1): crond: remove UID check in init script Jackie Huang (2): midori: exclude from self-hosted for mips64 busybox: fix sed auto insert newline testcase Jason Wessel (2): syslinux.bbclass: Fix default serial port string grub-efi.bbclass: Fix startup.nsh to work on more EFI revs Jeffrey C Honig (3): initscripts: insure checkroot.sh runs before anything writing to the file perl: perl-ptest.inc polutes package dependencies when ptest not enabled rootfs_*.bbclass: List which post-install scripts can not be run Joao Henrique Ferreira de Freitas (1): grub-efi.bbclass: Fixes GRUB_IMAGE when using boot-directdisk class Joe Slater (1): vala.bbclass: add dependency on vala Jonathan Liu (4): qt4: add upstream QTBUG-31579 patch for QPainter regression qt4: add upstream QTBUG-34218/QTBUG-34234 misaligned selection patch eglibc_2.18.bb: accept make versions 4.0 and greater eglibc_2.17.bb: accept make versions 4.0 and greater Junxian.Xiao (1): Fix conflict between procps and base-files Khem Raj (2): pulseaudio: Fix build break on armeb libnl: Fix random segfaults due to memory corruption Konrad Scherer (4): relocate_sdk.py: Allow script to work with Python 2.4 and 3. cracklib: cracklib-native should not depend on zlib pigz: Add pigz to buildtools tarball pixbufcache.bbclass: gdk-pixbuf-query-loaders depends on libz Laurentiu Palcu (3): nativesdk-qt4-tools: create qt.conf file meta-toolchain-qt: put QT_CONF_PATH in environment script flex: fix m4 issue on target Lei Liu (7): image-mklibs: Fix grep pattern when mklibs collects executables in rootfs mklibs: add dependency on dpkg-native base.bbclass: Fix incorrect setting of multilib PREFERRED_PROVIDER_virtual_pkg package_rpm.bbclass: Replace -linux-gnun32 with -linux.* in RPM platform file syslinux: use cross toolchain to compile dpkg: Fix a build error for dpkg-native on CentOS 5.8. dpkg: Fix a link problem for dpkg-native on CentOS 5.8. Lu Chong (3): dbus: no messages of status command print ppp: Add two structures in
Re: [OE-core] [PATCH 1/1] libgcrypt: fix compile error with '-O2' in sysroot path
On 12/10/2013 07:40 PM, Burton, Ross wrote: On 10 December 2013 11:37, Richard Purdie richard.pur...@linuxfoundation.org wrote: I thought it would do no harm. And I will send this patch to upstream, so it might be a little strange that I only modify the Makefile.am file even if Makefile.in has the same problem. It can actually be harmful since the modification time of Makefile.in can be after the time for Makefile.am and things can go very wrong with autotools when that happens :( Another good reason not to modify the Makefile.in is that being a generated file, updating automake can change how it is generated, so the patch doesn't apply anymore. Ross Hi All, Thanks for your explanation. I'll send out a V2. Best Regards, Chen Qi ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 000/124] [dora] fixes for dora (cover leter only)
On 12/11/2013 10:28 AM, Saul Wold wrote:
On 12/10/2013 07:08 AM, Robert Yang wrote:
* Main changes:
- Wic fixes
- Update the kernel to 3.10.17
- CVE fixes
- Other Bug fixes
Note:
The PULL is created based on poky, maybe oe-core is preferred ?
As Paul already pointed out this should be oe-core based if possible.
OK, I will send a new one based on oe-core.
I started a build of robert/dora-next branch.
While this list looks long nothing jumps out atimmediately me as flagged. I
would as that you verify you have collected as many of the patches from the
mailing list that wanted to be in dora that are either in master or you needed
Yes, I've verified that.
to merge separately.
Check below for an additional question about lttng-modules update
Sau!
// Robert
The following changes since commit 53d2563ff13fcec74d4250bef5419e36169e55cc:
Otavio Salvador (1):
lttng-modules: Update to 2.3.3 version
Why are you including this package update? We do not normally do package
updates
We had decided to update the kernel to 3.10.17, so we also need update the
lttng-modules.
// Robert
Paul Eggleton (3):
classes/ptest: fix quoting
zisofs-tools-native: add missing DEPENDS on zlib-native
buildhistory_analysis: fix error when comparing image contents
Phil Blundell (2):
binutils: Add gnu-config-native to DEPENDS
boost: Add patch to avoid undefined references to
boost::atomic::lockpool::get_lock_for()
Qiang Chen (6):
nfs-utils: Stop rpc.statd correctly
nfs-utils: nfsserver restart should kill and recreate nfsd kernel
threads
openssl: create package for openssl configuration file
openssh: fix sshd status command error prompt
nfs-utils: modify nfsserver init script indent
irda-utils: restart irda daemon correctly
Richard Purdie (4):
nativesdk: Fix pn check
cross-canadian: Fix SHLIBSDIR when using multilib
cross-canadian: Handle powerpc linux verses linux-gnuspe
ethtool: Fix ptest compile
Ross Burton (6):
xorg-lib-common: fix malloc0returnsnull usage
pango: fix x11 DISTRO_FEATURE check
cairo: add explicit dependency on zlib
packagegroup-base: if zeroconf DISTRO_FEATURE enabled, add
libnss-mdns
weston-init: start weston on a new VT
qt4-x11-free: depend on ICU
Roy Li (2):
pseudo: fix library path in FILES_${PN}
libcap: fix CAP_LAST_CAP
Saul Wold (5):
busybox: Add depmod (adds 2240 bytes)
kmod: Add patch to fix seperate build dir of ptest
mdadm: Disable the RUN_DIR check
sysvinit: unmount the psplash lazyily
image_types: newer btrfs.mkfs needs an empty file to build the disk
in
Seth Bollinger (1):
ncurses-terminfo: Remove bashism from basic terminfo installation
Steffen Sledz (1):
gdb-7.6: fix cygwin check in configure script
Søren Holm (1):
e2fsprogs: Escape filenames in populate-extfs.sh
Ting Liu (2):
kmod-native: use bswap to work on older Linux hosts
perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for
powerpc64
Tom Zanussi (16):
wic: check for build artifacts
wic: check passed-in build artifact directories
wic: Check for the existence/correctness of build artifacts
wic: Initialize return values in find_artifacts()
wic: add pseudo to the populate-extfs step
wic: Remove dependency on rt_util module
wic: eliminate module checks
wic: Remove dependency on rpmmisc
wic: Remove dependency on myurlgrab module
wic: remove rpm warning code from BackendPlugin
wic: Remove rpm and grabber dependencies from BaseImageCreator
wic: Remove rpmmisc call from livecd
wic: Remove binary dependencies
wic: Make find_binary_path() more user-friendly
wic: Update and generalize pseudo setup for rootfs generation
wic: Remove selinux_check()
Wenzong Fan (2):
perf: flag __SANE_USERSPACE_TYPES__ to include int-ll64.h for mips64
udev: remove extra -dev/-dbg packages
Xufeng Zhang (1):
kernel.bbclass: Delay rm_work to run after do_bundle_initramfs
meta/classes/base.bbclass |8 +-
meta/classes/cross-canadian.bbclass| 36 +++
meta/classes/distutils.bbclass | 24 +-
meta/classes/extrausers.bbclass|4 +
meta/classes/grub-efi.bbclass |3 +-
meta/classes/image-mklibs.bbclass |3 +-
meta/classes/image_types.bbclass |1 +
meta/classes/kernel.bbclass| 13 +-
meta/classes/license.bbclass |4 +-
meta/classes/nativesdk.bbclass |2 +-
meta/classes/package_rpm.bbclass |6 +-
meta/classes/pixbufcache.bbclass |2 +-
meta/classes/ptest.bbclass |2 +-
meta/classes/rootfs_deb.bbclass|5 +-
meta/classes/rootfs_ipk.bbclass|5 +-
meta/classes/rootfs_rpm.bbclass
Re: [OE-core] [PATCH 000/124] [dora] fixes for dora (cover leter only)
On 12/11/2013 08:52 AM, Khem Raj wrote: On Tue, Dec 10, 2013 at 10:03 AM, Paul Eggleton paul.eggle...@linux.intel.com wrote: Bruce Ashfield (10): kernel: restore scripts in the sysroot Wasn't there a problem with this patch? I can't recall if it was rectified before or after it was merged to master. Problem is elsewhere, there was more of documentation issue with Richard fixed in module.bbclass. this is ok. Yes, we need the patch, otherwise, perf will fail to build if the kernel is mirrored from the sstate IIRC. // Robert ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2 1/3] shadow-native: allow for setting password in clear text
From: Chen Qi qi.c...@windriver.com
Allow user to set password in clear text. This is convenient when
we're building out an image.
This feature is mainly used by useradd.bbclass and extrausers.bbclass.
This patch adds a new option '-P' to useradd, usermod, groupadd and groupmod
commands provided by shadow-native. The shadow package on target and in SDK
will not be affected.
[YOCTO #5365]
Signed-off-by: Chen Qi qi.c...@windriver.com
---
.../allow-for-setting-password-in-clear-text.patch | 208
meta/recipes-extended/shadow/shadow.inc|1 +
2 files changed, 209 insertions(+)
create mode 100644
meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch
diff --git
a/meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch
b/meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch
new file mode 100644
index 000..eafb935
--- /dev/null
+++
b/meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch
@@ -0,0 +1,208 @@
+Upstream-Status: Inappropriate [OE specific]
+
+Allow for setting password in clear text.
+
+Signed-off-by: Chen Qi qi.c...@windriver.com
+
+---
+ src/Makefile.am |8
+ src/groupadd.c |8 +++-
+ src/groupmod.c |9 -
+ src/useradd.c |9 +++--
+ src/usermod.c | 10 --
+ 5 files changed, 34 insertions(+), 10 deletions(-)
+
+diff --git a/src/Makefile.am b/src/Makefile.am
+index 6a3b4c5..1ffdbc6 100644
+--- a/src/Makefile.am
b/src/Makefile.am
+@@ -76,10 +76,10 @@ chgpasswd_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBSELINUX)
$(LIBCRYPT)
+ chsh_LDADD = $(LDADD) $(LIBPAM) $(LIBSELINUX) $(LIBCRYPT_NOPAM)
$(LIBSKEY) $(LIBMD)
+ chpasswd_LDADD = $(LDADD) $(LIBPAM) $(LIBSELINUX) $(LIBCRYPT)
+ gpasswd_LDADD = $(LDADD) $(LIBAUDIT) $(LIBSELINUX) $(LIBCRYPT)
+-groupadd_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
++groupadd_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX) $(LIBCRYPT)
+ groupdel_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
+ groupmems_LDADD = $(LDADD) $(LIBPAM) $(LIBSELINUX)
+-groupmod_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
++groupmod_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX) $(LIBCRYPT)
+ grpck_LDADD= $(LDADD) $(LIBSELINUX)
+ grpconv_LDADD = $(LDADD) $(LIBSELINUX)
+ grpunconv_LDADD = $(LDADD) $(LIBSELINUX)
+@@ -99,9 +99,9 @@ su_SOURCES = \
+ suauth.c
+ su_LDADD = $(LDADD) $(LIBPAM) $(LIBCRYPT_NOPAM) $(LIBSKEY) $(LIBMD)
+ sulogin_LDADD = $(LDADD) $(LIBCRYPT)
+-useradd_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
++useradd_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX) $(LIBCRYPT)
+ userdel_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
+-usermod_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX)
++usermod_LDADD = $(LDADD) $(LIBPAM_SUID) $(LIBAUDIT) $(LIBSELINUX) $(LIBCRYPT)
+ vipw_LDADD = $(LDADD) $(LIBSELINUX)
+
+ install-am: all-am
+diff --git a/src/groupadd.c b/src/groupadd.c
+index 66b38de..3157486 100644
+--- a/src/groupadd.c
b/src/groupadd.c
+@@ -124,6 +124,7 @@ static void usage (void)
+ (void) fputs (_( -o, --non-unique allow to create groups
with duplicate\n
+ (non-unique) GID\n),
stderr);
+ (void) fputs (_( -p, --password PASSWORD use this encrypted
password for the new group\n), stderr);
++ (void) fputs (_( -P, --clear-password PASSWORD use this clear text
password for the new group\n), stderr);
+ (void) fputs (_( -R, --root CHROOT_DIR directory to chroot
into\n), stderr);
+ (void) fputs (_( -r, --system create a system
account\n), stderr);
+ (void) fputs (\n, stderr);
+@@ -388,13 +389,14 @@ static void process_flags (int argc, char **argv)
+ {key, required_argument, NULL, 'K'},
+ {non-unique, no_argument, NULL, 'o'},
+ {password, required_argument, NULL, 'p'},
++ {clear-password, required_argument, NULL, 'P'},
+ {root, required_argument, NULL, 'R'},
+ {system, no_argument, NULL, 'r'},
+ {NULL, 0, NULL, '\0'}
+ };
+
+ while ((c =
+- getopt_long (argc, argv, fg:hK:op:R:r, long_options,
++ getopt_long (argc, argv, fg:hK:op:P:R:r, long_options,
+option_index)) != -1) {
+ switch (c) {
+ case 'f':
+@@ -446,6 +448,10 @@ static void process_flags (int argc, char **argv)
+ pflg = true;
+ group_passwd = optarg;
+ break;
++ case 'P':
++ pflg = true;
++ group_passwd = pw_encrypt (optarg, crypt_make_salt
(NULL, NULL));
++ break;
+ case 'R':
+ if
[OE-core] [PATCH V2 2/3] image.bbclass: fix for zap_root_password
From: Chen Qi qi.c...@windriver.com
Previously, this function replaces the root password with '*' if
'debug-tweaks' is not in IMAGE_FEATURES. It not only zaps empty root
password, but also zaps non-empty root password. That means, if the
user uses a bbappend file for base-passwd to set the root password, he
would not be able to login as root; if the user uses 'EXTRA_USERS_PARAMS'
to set the root password, he would still not be able to login as root.
What we really want from this function is to disallow empty root password
if 'debug-tweaks' is not in IMAGE_FEATURES. This function should not remove
non-empty root password because that password is usually deliberately set
by the user.
This patch renames zap_root_password to zap_empty_root_password to
better reflect the intent of this function. It also modifies the code
to make this function work correctly.
Signed-off-by: Chen Qi qi.c...@windriver.com
---
meta/classes/core-image.bbclass |2 +-
meta/classes/image.bbclass | 14 --
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/meta/classes/core-image.bbclass b/meta/classes/core-image.bbclass
index e7c34e2..fc4bd2f 100644
--- a/meta/classes/core-image.bbclass
+++ b/meta/classes/core-image.bbclass
@@ -74,7 +74,7 @@ inherit image
ROOTFS_POSTPROCESS_COMMAND += rootfs_update_timestamp ;
# Zap the root password if debug-tweaks feature is not enabled
-ROOTFS_POSTPROCESS_COMMAND += '${@base_contains(IMAGE_FEATURES,
debug-tweaks, , zap_root_password ; ,d)}'
+ROOTFS_POSTPROCESS_COMMAND += '${@base_contains(IMAGE_FEATURES,
debug-tweaks, , zap_empty_root_password ; ,d)}'
# Tweak the mount options for rootfs in /etc/fstab if read-only-rootfs is
enabled
ROOTFS_POSTPROCESS_COMMAND += '${@base_contains(IMAGE_FEATURES,
read-only-rootfs, read_only_rootfs_hook; , ,d)}'
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index 168f283..c6d9db8 100644
--- a/meta/classes/image.bbclass
+++ b/meta/classes/image.bbclass
@@ -562,11 +562,13 @@ rootfs_uninstall_unneeded () {
fi
}
-# set '*' as the root password so the images
-# can decide if they want it or not
-zap_root_password () {
- sed 's%^root:[^:]*:%root:*:%' ${IMAGE_ROOTFS}/etc/passwd
${IMAGE_ROOTFS}/etc/passwd.new
- mv ${IMAGE_ROOTFS}/etc/passwd.new ${IMAGE_ROOTFS}/etc/passwd
+# This function is intended to disallow empty root password if 'debug-tweaks'
is not in IMAGE_FEATURES.
+zap_empty_root_password () {
+ if [ -e ${IMAGE_ROOTFS}/etc/shadow ]; then
+ sed -i 's%^root::%root:*:%' ${IMAGE_ROOTFS}/etc/shadow
+ elif [ -e ${IMAGE_ROOTFS}/etc/passwd ]; then
+ sed -i 's%^root::%root:*:%' ${IMAGE_ROOTFS}/etc/passwd
+ fi
}
# allow dropbear/openssh to accept root logins and logins from accounts with
an empty password string
@@ -648,7 +650,7 @@ rootfs_sysroot_relativelinks () {
sysroot-relativelinks.py ${SDK_OUTPUT}/${SDKTARGETSYSROOT}
}
-EXPORT_FUNCTIONS zap_root_password remove_init_link do_rootfs
make_zimage_symlink_relative set_image_autologin rootfs_update_timestamp
rootfs_no_x_startup
+EXPORT_FUNCTIONS zap_empty_root_password remove_init_link do_rootfs
make_zimage_symlink_relative set_image_autologin rootfs_update_timestamp
rootfs_no_x_startup
do_fetch[noexec] = 1
do_unpack[noexec] = 1
--
1.7.9.5
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
