On 10/2/19 6:17 AM, Richard Purdie wrote:
On Fri, 2019-09-27 at 14:56 -0400, Konrad Scherer wrote:
From: Konrad Scherer
Using the glob function to map signatures to sstate files is very
slow
when the sstate is large and accessed over nfs. The lookup now only
loads the necessary prefixes and
From: Konrad Scherer
Using the glob function to map signatures to sstate files is very slow
when the sstate is large and accessed over nfs. The lookup now only
loads the necessary prefixes and doesn't use glob as all.
Unfortunately I don't have access to the systems where the perfor
ect this and include the required binaries
in HOSTTOOLS? Or have the oeqa helper modify the HOSTTOOLS before they
are used?
--
Konrad Scherer, MTS, Linux Products Group, Wind River
--
___
Openembedded-core mailing list
Openembedded-core@lists.o
7;.
What config options are you putting in local.conf to trigger the tests?
--
Konrad Scherer, MTS, Linux Products Group, Wind River
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
ase have a look and give it a try. All feedback welcome!
[1]: https://github.com/Wind-River/wr-lx-setup
--
Konrad Scherer, MTS, Linux Products Group, Wind River
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedde
From: Konrad Scherer
While experimenting with signing rpms, I attempted to import the keys
into a temporary keyring and set GPG_PATH to the temporary keyring.
This fails because the gpg export call cannot find the requested key
in the default keyring.
Signed-off-by: Konrad Scherer
---
meta
Summary: Fix exporting of gpg keys when using a temporary keyring
When I tried to sign rpms and feeds using a gpg key on a temporary
keyring, I got a build failure in os-release.bb due to missing
exported keys. I traced the failure back to signing-keys.bb. Even
though the task had logged successfu
From: Konrad Scherer
When testing the do_export_public_keys function using
bitbake -c do_export_public_keys signing-keys
the destination path for the exported keys does not exist
and the gpg export call fails.
Signed-off-by: Konrad Scherer
---
meta/recipes-core/meta/signing-keys.bb | 2
From: Konrad Scherer
The Makedoc.sh script uses the following line to set TMPDIR
export TMPDIR=`mktemp -d ${TMPDIR:-/tmp}/ldt.XX`;
and then later in the script:
chmod u+x $TMPDIR/linuxdoc
Since TMPDIR is not set the script will default to /tmp and if /tmp
is set to noexec (which is
From: Konrad Scherer
Hello,
I am working on distributing native sstate files to our customers and
have ran into a few issues. Here is my workflow
cd
mkdir downloads
git clone git://git.yoctoproject.org/poky
source poky/oe-init-build-env mybuild
echo 'DL_DIR ?= "
With commit 3d59d0bed756f64d0092caa3892239c779c4a341 the populate-lic
sstate files are now arch independent and not stored with the
native populate-sysroot sstate files. If the native sstate dir is
distributed then populate-lic step is still triggered.
Signed-off-by: Konrad Scherer
---
meta
On 13-11-21 02:33 AM, Mark Hatle wrote:
From: Konrad Scherer
If the sed command does not run before make is invoked, the compile
fails. Defining the environment variable is the proper way to disable
warnings as errors build option and eliminates the race condition.
Signed-off-by: Konrad
On 13-11-07 06:16 PM, Saul Wold wrote:
On 11/07/2013 10:36 AM, Konrad Scherer wrote:
From: Konrad Scherer
Turns out the sed command has not been working as intended since
kernel 3.1 due to the trailing space. Adding the WERROR=0 environment
variable is the correct way to disable warnings as
From: Konrad Scherer
Turns out the sed command has not been working as intended since
kernel 3.1 due to the trailing space. Adding the WERROR=0 environment
variable is the correct way to disable warnings as errors.
Signed-off-by: Konrad Scherer
---
meta/recipes-kernel/perf/perf.bb | 4
1
The original method to remove -Werror using sed does not work on
kernels after 3.1 due to trailing space. To avoid build failures due to
warnings as errors add the WERROR env variable.
---
Konrad Scherer, MTS, Linux Products Group, Wind River
I am pretty sure this is just a typo. I noticed it while building
a native only packagegroup and zlib kept getting built as well.
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openembedded-core mailing list
Openembedded-core
From: Konrad Scherer
Signed-off-by: Konrad Scherer
---
meta/recipes-extended/cracklib/cracklib_2.9.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
b/meta/recipes-extended/cracklib/cracklib_2.9.0.bb
index 34c2ff1
Another native sstate minor issue. Reuse of native sstate file for
gdk-pixbuf-native fails in the pixbufcache_sstate_postinst. The file
gdk-pixbuf-query-loaders attempts to use the host libz. Adding the
dependency to zlib-native ensures the sstate for zlib-native is
available.
---
Konrad Scherer
From: Konrad Scherer
ldd sysroots/x86_64-linux/usr/bin/gdk-pixbuf-query-loaders.real
libz.so.1 => /sysroots/x86_64-linux/usr/bin/../../usr/lib/libz.so.1
(0x7fab55393000)
If zlib-native has not been unpacked, host libz is used which can fail.
Signed-off-by: Konrad Scherer
---
m
seems to have been fixed recently. This has made
reproducing the build failure more difficult, but the race condition
still exists.
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openembedded-core mailing list
Openembedded-core
From: Konrad Scherer
When using the tar executable in the buildtools, tar will execute
gzip. If this happens before zlib-native is built, then the gzip
on the host will be used and can fail if the libz in the buildtools
is not compatible. Adding pigz to the build tools avoids this host
From: Konrad Scherer
Python 2.4 does not support the 'b' string literal or the
keyword 'as' in exception handling. Python 3 does not accept
the old method of exception handling and defaults to unicode.
The b() function converts strings to bytes on Python 3 and
using sys.e
tested the patch on 2.4.3, 2.6.5, 2.7.3 and
3.2.3.
V2: Detect the system encoding before converting
V3: Remove unneeded import codecs
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openembedded-core mailing list
Openembedded-core
tested the patch on 2.4.3, 2.6.5, 2.7.3 and
3.2.3.
V2: Detect the system encoding before converting
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http
From: Konrad Scherer
Python 2.4 does not support the 'b' string literal or the
keyword 'as' in exception handling. Python 3 does not accept
the old method of exception handling and defaults to unicode.
The b() function converts strings to bytes on Python 3 and
using sys.e
tested the patch on 2.4.3, 2.6.2, 2.7.3 and
3.2.3.
---
Konrad Scherer, MTS, Linux Products Group, Wind River
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
From: Konrad Scherer
Python 2.4 does not support the 'b' string literal or the
keyword 'as' in exception handling. Python 3 does not accept
the old method of exception handling and defaults to unicode.
The b() function converts strings to bytes on Python 3 and
using sys.e
file.write('LABEL=%s '% (label))
cfgfile.write('%s %s\n' % (append, btype[1]))
else:
cfgfile.write('APPEND %s\n' % btype[1])
The extra kernel parameters are added to btype[1] and then written out as part
of the APPEND field.
D
From: Konrad Scherer
Unmount all filesystems automounted by udev except one with
rootfs since the filesystem will be destroyed by switch_root.
Signed-off-by: Konrad Scherer
---
meta/recipes-core/initrdscripts/files/init-live.sh | 21
1 file changed, 17 insertions(+), 4
29 matches
Mail list logo
