Stefan Seefeld wrote:
+RDEPENDS_${PN}-ptest += make
I just noticed that the lttng-tools test suite is hardcoded for bash, so that
is another dependency.
--
Björn
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
rongqing...@windriver.com wrote:
+for x in `find $libdir -name run-ptest -type f`
+cd `dirname $x`
You can get this list of ptest dirs by just running `ls -d */ptest`. It is
simpler and also much faster than using find.
--
Björn
___
Randy MacLeod wrote:
Yes, Roy will fix this. He's on holiday for a few days.
Excellent.
I presume he'll add a check to see which arg to use for find
rather than add a dependency on findutils.
I suggest skipping the find command altogether. The run-ptest files are defined
to always sit in
Chris Larson wrote:
On Wed, Sep 11, 2013 at 2:17 AM, rongqing...@windriver.com wrote:
+for x in `find -L ./ -name run-ptest -type f -perm /u+x,g+x`
+do
As far as I can tell, busybox find doesn't support -L, so this adds an
implicit, undeclared dependency upon findutils.
Chris Larson wrote:
On Wed, Sep 11, 2013 at 2:17 AM, rongqing...@windriver.com wrote:
+for x in `find -L ./ -name run-ptest -type f -perm /u+x,g+x`
+do
As far as I can tell, busybox find doesn't support -L, so this adds an
implicit, undeclared dependency upon findutils.
That
rongqing...@windriver.com wrote:
+DISTRO_FEATURES += ptest
This looks a bit odd to have in the recipe. Ptest should rather be
enabled/disabled by the distro.conf or local.conf.
--
Björn
___
Openembedded-core mailing list
Burton, Ross wrote:
Do you plan on adding GStreamer to that list?
No, we have no plans for gstreamer pest. Feel free to run with it. :-)
--
Björn
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
Install busybox test suite and run it as ptest.
Signed-off-by: Anders Roxell anders.rox...@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/busybox/busybox.inc |2 +-
meta/recipes-core/busybox/busybox_1.20.2.bb |7 +++
meta/recipes-core/busybox/files
Hi all.
In the interest of avoiding duplication of work, here is a list of recipes for
which we (Enea) have already enabled ptest but have not yet submitted patches:
- bash*
- busybox
- bzip2
- dbus*
- dhcp
- dropbear
- ethtool
- gcc-runtime
- gdb
- gdbm
- gettext
- glib-2.0*
- kmod
- libxml2
-
Jesse Zhang wrote:
Ok.. Here is the new commit.
Looks good to me.
Reviewed-by: Björn Stenberg b...@enea.com
--
Björn
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo
Jesse Zhang wrote:
+--- a/t/TEST 2013-05-15 23:12:12.705104588 -0400
b/t/TEST 2013-05-15 23:20:20.126104587 -0400
Is patching t/TEST better than simply using sed to transform the output?
I took a quick look at future versions and t/TEST is modified in both perl
5.16.3 and 5.18.0-RC4.
Jesse Zhang wrote:
+++ b/meta/recipes-devtools/perl/perl-5.14.3/run-ptest
@@ -0,0 +1,2 @@
+#!/bin/sh
+cd t ./TEST
run-ptest also needs to parse the output and reformat results into the standard
ptest/automake format, such as PASS: foo, FAIL: foo and SKIP: foo.
--
Björn
FILES_${PN} = ${libdir}/lib*${SOLIBS} ${datadir}/glib-2.0/schemas \
${datadir}/glib-2.0/gettext/mkinstalldirs
${datadir}/glib-2.0/gettext/po/Makefile.in.in
Acked-By: Björn Stenberg b...@enea.com
--
Björn
___
Openembedded-core
Björn Stenberg wrote:
Your paste contains some errors that are clearly recipe/framework issues:
I forgot to say that I think we should separate between issues with the ptest
framework (bbclass changes) and issues with specific package test suites.
In my view it is critical that we get
Saul Wold wrote:
I ran ptest-runner finally I saw that there were failures, I am
wondering if these are expected?
http://pastebin.com/PAH3gJT0
Thank you for testing. Some test failures are to be expected. The purpose of
ptest is to make the tests build and run. Fixing errors found by the
-by: Björn Stenberg b...@enea.com
Signed-off-by: Anders Roxell anders.rox...@enea.com
Signed-off-by: Josep Puigdemont josep.puigdem...@enea.com
---
meta/classes/insane.bbclass |6 +++---
meta/classes/native.bbclass |3 +++
meta/classes/ptest.bbclass | 17 +
3 files changed, 11
Richard Purdie wrote:
Why are we putting all the debug files into the -ptest package now? Does
that make sense?
(Sorry, I missed this comment.)
My reasoning is that we want all ptest data to be contained in -ptest packages
and not leak into other packages.
If we keep debug data in the
Move ${PN}-ptest to start of PACKAGES to ensure all ptest files are
packaged in the -ptest package.
Add QA exclusions to insane.bbclass to ensure -ptest packages can contain
any files they need.
Disable ptest for native packages.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes
The dbus-ptest recipe doesn't produce an output package called
dbus-ptest. What we are interested in is actually the dbus-ptest-ptest
package.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus.inc |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
(The subject was a mistake. Parent is the only patch.)
--
Björn
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Move ${PN}-ptest to start of PACKAGES to ensure all ptest files are
packaged in the -ptest package.
Add QA exclusions to insane.bbclass to ensure -ptest packages can contain
any files they need.
Bugfix: Add subshells for 'type' command.
This patch fixes bug #4069.
Signed-off-by: Björn Stenberg
Björn Stenberg wrote:
Move ${PN}-ptest to start of PACKAGES to ensure all ptest files are
packaged in the -ptest package.
Add QA exclusions to insane.bbclass to ensure -ptest packages can contain
any files they need.
This patch fixes bug #4069.
Signed-off-by: Björn Stenberg b
Hi. I need a little help.
The ${PN}-ptest group is not added to PACKAGES by default in bitbake.conf like
all the other groups. Instead it is added to PACKAGES in ptest.bbclass. This
way it is only added for those recipes that implement ptest.
However it turns out this doesn't work when package
In response to feedback about the ptest checks added to recipes when
implementing ptest, I have changed it so those checks now only exist in
ptest.bbclass and recipes instead use dedicated _ptest functions to define
ptest-specific actions.
Björn Stenberg (4):
ptest: Move ptest checks from
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb
b/meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb
index d58d489..7795524 100644
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus-ptest_1.6.8.bb |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-core/dbus/dbus-ptest_1.6.8.bb
b/meta/recipes-core/dbus/dbus-ptest_1.6.8.bb
index 1382206..d00819a 100644
--- a/meta
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-extended/bash/bash.inc | 15 ++-
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/meta/recipes-extended/bash/bash.inc
b/meta/recipes-extended/bash/bash.inc
index 20a23f0..c619f82 100644
--- a/meta/recipes
This patch cleans up ptest implementation in recipes by moving ptest
specific code parts into dedicated *_ptest functions.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/ptest.bbclass | 35 +--
1 files changed, 29 insertions(+), 6 deletions
Richard Purdie wrote:
+RDEPENDS_${PN}-ptest += make
+RDEPENDS_${PN}-ptest_virtclass-native =
+RDEPENDS_${PN}-ptest_virtclass-nativesdk =
The above scares me. Why? This is going to make packaging of zlib
dependent on the packaging of make, due to the way our packaging works.
Will it?
From: Daniel Dai daniel@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/busybox/busybox.inc |2 +-
meta/recipes-core/busybox/busybox_1.20.2.bb | 10 ++
meta/recipes-core/busybox/files/run-ptest |7 +++
3 files changed, 18 insertions
Here is a handful ptest additions for various packages.
Also included is a minor tweak for ptest.bbclass.
Anders Roxell (1):
zlib: Add ptest
Björn Stenberg (4):
bzip2: Add ptest
openssh: Add ptest
openssl: Add ptest
ptest: Add missed .debug path
Daniel Dai (1):
busybox: Add ptest
From: Daniel Dai daniel@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/busybox/busybox.inc |2 +-
meta/recipes-core/busybox/busybox_1.20.2.bb | 10 ++
meta/recipes-core/busybox/files/run-ptest | 11 +++
3 files changed, 22
From: Anders Roxell anders.rox...@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
Signed-off-by: Anders Roxell anders.rox...@enea.com
---
.../zlib/zlib-1.2.7/Makefile-runtests.patch| 38
meta/recipes-core/zlib/zlib-1.2.7/run-ptest|7
meta
From: jack zhang jack.zh...@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/udev/udev.inc| 19 ++-
.../recipes-core/udev/udev/add-install-ptest.patch | 60
meta/recipes-core/udev/udev/run-ptest |3 +
3
From: Rick.Yang rick.y...@enea.com
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-support/attr/acl_2.2.51.bb| 21
.../attr/files/add-runtest-target.patch| 26
meta/recipes-support/attr/files/run-ptest
Signed-off-by: Björn Stenberg b...@enea.com
---
.../add-test-support-for-busybox.patch | 61
.../openssh/openssh-6.1p1/run-ptest|7 ++
meta/recipes-connectivity/openssh/openssh_6.1p1.bb | 11 +++-
3 files changed, 78 insertions(+), 1
Signed-off-by: Björn Stenberg b...@enea.com
---
.../openssl/openssl-1.0.0j/Makefiles-ptest.patch | 74
.../openssl/openssl-1.0.0j/run-ptest |2 +
meta/recipes-connectivity/openssl/openssl.inc | 19 +-
.../recipes-connectivity/openssl
Signed-off-by: Björn Stenberg b...@enea.com
---
.../recipes-extended/bzip2/bzip2-1.0.6/Makefile.am | 32
meta/recipes-extended/bzip2/bzip2-1.0.6/run-ptest |2 +
meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 10 +-
3 files changed, 43 insertions(+), 1
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/ptest.bbclass |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/meta/classes/ptest.bbclass b/meta/classes/ptest.bbclass
index 361de78..131af7b 100644
--- a/meta/classes/ptest.bbclass
+++ b/meta/classes
Only install eglibc-specific dependencies when building for eglibc.
Tweak a test case that won't build with uclibc.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/fix-conflicting-rand.patch | 35
meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb
Bernhard Reutner-Fischer wrote:
The uncompressed log is about 50MB, i put it here (still 1.2MB):
http://busybox.net/~aldot/oe/mk.all.20130118-1442.53.log.xz
Can I ask how you worked around the iconv RPATH issue?
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2669
--
Björn
glib-2.0 would not build with ptest, due to bad dependencies.
When looking into that, I found that libiconv did not pass the QA RPATH
check so I fixed that too.
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=2669)
Björn Stenberg (2):
glib-2.0: Fix ptest to build with uclibc.
libiconv
Modify libtool to not add RPATH.
This solves https://bugzilla.yoctoproject.org/show_bug.cgi?id=2669
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-support/libiconv/libiconv_1.14.bb |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/meta/recipes-support
Only install eglibc-specific dependencies when building for eglibc.
Tweak a test case that won't build with uclibc.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/fix-conflicting-rand.patch | 35
meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb
Saul Wold wrote:
-RDEPENDS_${PN}-ptest += \
-eglibc-gconv-utf-16 \
-eglibc-charmap-utf-8 \
-eglibc-gconv-cp1255 \
-eglibc-charmap-cp1255 \
-eglibc-gconv-utf-32 \
-eglibc-gconv-utf-7 \
-
This patch adds a new recipe dbus-test to build and package the dbus test
suite. The reason for a separate recipe is that the dbus test suite depends
on dbus-glib, so it cannot be compiled at the same time as dbus.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus-1.6.4
Marcin Juszkiewicz wrote:
ExpansionError: Failure expanding variable RDEPENDS_dbus-lib
Ehm, how embarrassing. I have now posted an updated patch.
--
Björn
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
for building and running the tests.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/image.bbclass |6 ++-
meta/classes/packagegroup.bbclass |2 +-
meta/classes/ptest.bbclass | 34
.../automake
This patch adds a new recipe dbus-test to build and package the dbus test
suite. The reason for a separate recipe is that the dbus test suite depends
on dbus-glib, so it cannot be compiled at the same time as dbus.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus-1.6.4
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/Makefile-ptest.patch | 61
meta/recipes-core/glib-2.0/glib-2.0/run-ptest |3 +
meta/recipes-core/glib-2.0/glib-2.0_2.34.3.bb | 25 +++-
meta/recipes-core/glib-2.0/glib.inc
This package contains a simple shell script which searches for all installed
ptests on the rootfs and runs each test in sequence.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../ptest-runner/files/ptest-runner| 16
.../ptest-runner/ptest-runner_1.0.bb
Signed-off-by: Björn Stenberg b...@enea.com
---
.../bash/bash-4.2/build-tests.patch| 48
meta/recipes-extended/bash/bash-4.2/run-ptest |2 +
.../bash/bash-4.2/test-output.patch| 25 ++
meta/recipes-extended/bash/bash.inc
now.
Björn Stenberg (5):
Add a new distro feature ptest.
New package: ptest-runner
Add ptest for glib.
Add ptest for dbus.
Add ptest for bash.
meta/classes/image.bbclass |6 +-
meta/classes/packagegroup.bbclass |2 +-
meta/classes
Radu Moisan wrote:
curl: upgrade to 7.27.0
I guess 7.27.0 is better than the current 7.26.0, but wouldn't it make more
sense to upgrade to the latest version 7.28.1? There has been a lot of bug
fixes since 7.27.0.
--
Björn
___
Openembedded-core
Richard Purdie wrote:
meta/classes/image.bbclass |6 ++-
meta/classes/packagegroup.bbclass |2 +-
meta/conf/bitbake.conf | 15 -
Whilst we're in bootstrapping mode for this work, how about we make
Moved install logic from recipe to makefiles.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/Makefile-ptest.patch | 61
meta/recipes-core/glib-2.0/glib-2.0/run-ptest |3 +
meta/recipes-core/glib-2.0/glib-2.0_2.34.1.bb | 40
Richard Purdie wrote:
Whilst we're in bootstrapping mode for this work, how about we make
these changes a ptest.bbclass file which we'd inherit in the recipes
where we've got ptest enabled?
Ok. I'll give it a go and see how it turns out.
--
Björn
I have a few specific issues I would like help and/or feedback on:
- The -ptest .ipk packages get installed with Status: install user unpacked
rather than install user installed, causing them to be processed by postinst.
What do I have to do to take them from unpacked to installed?
- I have to
Otavio Salvador wrote:
Please base it in master branch as danny is now stable and this is a
new feature which might include regresions.
I will post patches against master soon.
--
Björn
___
Openembedded-core mailing list
Otavio Salvador wrote:
What do I have to do to take them from unpacked to installed?
Your package postinst needs to be able to be run offline.
But they don't have any postinst. There are no .postinst files installed for
these packages in /var/lib/opkg/info. run-postinst.awk goes through the
into the image when ptest is enabled, since the standard -ptest
suffix mechanism does not apply to this package.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus-1.6.4/run-ptest|3 +
.../dbus/dbus-1.6.4/test-run-path.patch| 26 ++
meta/recipes
for building and running the tests.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/image.bbclass |6 ++-
meta/classes/packagegroup.bbclass |2 +-
meta/conf/bitbake.conf | 15 -
.../automake/automake
This package contains a simple shell script which searches for all installed
ptests on the rootfs and runs each test in sequence.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../ptest-runner/files/ptest-runner| 16
.../ptest-runner/ptest-runner_1.0.bb
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/Makefile-ptest.patch | 30 ++
meta/recipes-core/glib-2.0/glib-2.0/run-ptest |3 +
meta/recipes-core/glib-2.0/glib-2.0_2.34.1.bb | 57
meta/recipes-core/glib-2.0/glib.inc
This recipe installs a simple shell script which searches for all installed
ptests on the rootfs and runs each test in sequence.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/conf/bitbake.conf |2 +-
.../ptest-runner/files/ptest-runner| 16
into the image when ptest is enabled, since the standard -ptest
suffix mechanism does not apply to this package.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-core/dbus/dbus-1.6.4/run-ptest|3 +
.../dbus/dbus-1.6.4/test-run-path.patch| 26 ++
meta/recipes
Signed-off-by: Björn Stenberg b...@enea.com
---
.../glib-2.0/glib-2.0/Makefile-ptest.patch | 30 ++
meta/recipes-core/glib-2.0/glib-2.0/run-ptest |3 +
meta/recipes-core/glib-2.0/glib-2.0_2.32.4.bb | 57
.../ptest-runner/files/ptest-runner
. They solve the
building and running relatively cleanly but the install bit is still a
rather kludgy list of cp and sed lines. I'm working on a more generic
make ptest-install solution.
These patches are against the danny branch.
Björn Stenberg (4):
Add a new distro feature ptest
New recipe
for building and running the tests.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/image.bbclass |6 ++-
meta/classes/packagegroup.bbclass |2 +-
meta/conf/bitbake.conf | 15 -
.../automake/automake
Khem Raj wrote:
I agree but then 1.7 GB is noticeably huge too and it will only become
larger in future so I don't think fetching from git will be a good solution
for gcc ever.
Can we use shallow clones? A quick test of gcc-4.7 gave me a 308 MB tar.gz when
cloned with --depth 1.
--
Björn
Hi.
I couldn't figure out where to properly patch this, so I'll just raise the
issue:
LDFLAGS is configured in bitbake.conf as linker flags to be passed to gcc, not
to ld. Hence it uses the -Wl prefix.
The linux kernel build system inherits LDFLAGS from the environment and passes
it directly
Koen Kooi wrote:
These have always been called ${PN}-tests, why the change?
When I discussed package testing informally before submitting patches, I found
that some people tend to lump all types of testing into one big Test bucket
and get very confused.
By giving this concept a slightly less
This package contains the top-level script that seeks out and starts all
package tests.
---
.../ptest-runner/files/ptest-runner| 16
.../ptest-runner/ptest-runner_1.0.bb | 17 +
2 files changed, 33 insertions(+), 0 deletions(-)
This patch creates a new package group -ptest to contain the tests from
each package.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/classes/distutils-common-base.bbclass |5 -
meta/classes/image.bbclass |6 --
meta/classes/task.bbclass
Patch Makefile.in to allow test programs be built on host and ran on
target.
Patch tests/run-all to output PASS/FAIL for each testcase.
Patch recipe to contitionally build and install ptest.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../bash/bash-4.2/build-tests.patch| 34
, which could potentially take a long time
My suggestion is a). I'm open for all suggestions that would make the
patch load easier to manage.
Björn Stenberg (3):
Add -ptest package group
Enable bash-ptest
New recipe: ptest-runner
meta/classes/distutils-common-base.bbclass |5
Saul Wold wrote:
You new patches still need patch headers with Upstream-Status and
Signed-off-by tags.
Ouch, sorry about that. I added Signed-off but forgot upstream. I'll be more
careful next time.
Should this be a DISTRO or IMAGE FEATURE? I can see potential
arguments for both sides, what
Also added beginline/endline to LIC_FILES_CHKSUM to not track whole pigz.c.
Signed-off-by: Björn Stenberg b...@enea.com
---
.../pigz/{pigz_2.2.4.bb = pigz_2.2.5.bb} |8 +++-
1 files changed, 3 insertions(+), 5 deletions(-)
rename meta/recipes-extended/pigz/{pigz_2.2.4.bb
---
meta/recipes-extended/pigz/pigz_2.2.4.bb | 11 ---
meta/recipes-extended/pigz/pigz_2.2.5.bb | 11 +++
2 files changed, 11 insertions(+), 11 deletions(-)
delete mode 100644 meta/recipes-extended/pigz/pigz_2.2.4.bb
create mode 100644
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-extended/pigz/pigz_2.2.4.bb | 11 ---
meta/recipes-extended/pigz/pigz_2.2.5.bb | 11 +++
2 files changed, 11 insertions(+), 11 deletions(-)
delete mode 100644 meta/recipes-extended/pigz/pigz_2.2.4.bb
create mode
PRSERV_DUMPDIR PRSERV_DUMPFILE PRSERV_LOCKDOWN PARALLEL_MAKE
BB_HASHCONFIG_WHITELIST ?= ${BB_HASHBASE_WHITELIST} DATE TIME
SESSION_MANAGER DBUS_SESSION_BUS_ADDRESS SSH_AGENT_PID XDG_SESSION_COOKIE
SSH_AUTH_SOCK XAUTHORITY
MLPREFIX ??=
Tested-by: Björn Stenberg b...@enea.com
--
Björn
Koen Kooi wrote:
My intention with the patch was to provide a native-only recipe for pigz,
to improve distro build speed.
But it went in as a regular recipe and hence needs to play well with others.
I thought I made it native-only by only providing gzip-native?
--
Björn
Koen Kooi wrote:
Op 15 mrt. 2012, om 09:25 heeft Björn Stenberg het volgende geschreven:
+PROVIDES_virtclass-native += gzip-native
This is either missing update-alternatives entries or it is missing
RREPLACES/RCONFLICTS with gzip/busybox/etc. Or both.
My intention with the patch
as an alternative gzip-native implementation only.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-extended/pigz/files/ldflags.patch | 17 +
meta/recipes-extended/pigz/pigz.inc| 21 +
meta/recipes-extended/pigz/pigz_2.2.4.bb |9
as an alternative gzip-native implementation only.
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-extended/pigz/files/ldflags.patch | 17 +
meta/recipes-extended/pigz/pigz.inc| 21 +
meta/recipes-extended/pigz/pigz_2.2.4.bb |9
as an alternative provider of gzip-native. Pigz is much
faster than gzip on multi-core machines.
Upstream-status: Pending
Signed-off-by: Björn Stenberg b...@enea.com
---
meta/recipes-extended/pigz/files/ldflags.patch | 11 +++
meta/recipes-extended/pigz/pigz.inc| 21
86 matches
Mail list logo
