We're excited to announce the inaugural "OpenEmbedded Summit" taking place
Sunday March 10th 2019 as part of the Southern California Linux Expo
(SCaLE) 17x at the Pasadena Convention Center.
For the past few years there's been an ever-growing OpenEmbedded event as
part of SCaLE. This year, with th
Hi Darcy,
I cannot assure you of that specific case but to my understanding you could
find out with the taskexp:
bitbake -g -u taskexp
There you will have a graphical interface to explore your package dependencies
and which task will be executed before another. Hope that helps.
Greetings, D
Hi,
Can someone knowledgeable with the inner workings of the build system
please confirm...
IF package B has RDEPENDS on package A
THEN during do_rootfs task, package A will always be installed into
rootfs first AND the post-inst scripts of package A will always be run
prior to those for package
What is the recommended packaging approach for an upstream configure script
that seems to think that it must have pcre-config (which is disabled by the
binconfig-disabled class)?
Looking at the source of the upstream package seems to indicate that they
actually do need pcre, so this is not as simp
On 1/30/19 8:42 AM, Burton, Ross wrote:
No doubt devtool should handle this better, but upgrading glibc is
*not easy*. If you can't do it manually then I wouldn't recommend
doing it at all.
A better start would be to copy the recipes from git for the version
you want, and then you'll be able to
Hello,
On Thu, Jan 17, 2019 at 3:03 AM srinivasan wrote:
> I am trying to customize my vendor specific Yocto BSP's to my custom
> OS. I am facing the below error, could you please do the needful or
> provide me some pointers from your end for solving this issue
>
> Error:
> $ bitbake fsl-image-v
If a process gets killed by timeout or OOM the output could end
without '\n' so add 'DURATION: N\n' after '\nERROR: ptest-dir\n'.
Signed-off-by: Aníbal Limón
---
utils.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils.c b/utils.c
index 0813e3c..504df0b 100644
--- a/util
To fix buffer ordering problems.
Signed-off-by: Aníbal Limón
---
utils.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/utils.c b/utils.c
index 01ee415..0813e3c 100644
--- a/utils.c
+++ b/utils.c
@@ -250,7 +250,8 @@ run_child(char *run_ptest, int fd_stdout, int fd_stderr)
No doubt devtool should handle this better, but upgrading glibc is
*not easy*. If you can't do it manually then I wouldn't recommend
doing it at all.
A better start would be to copy the recipes from git for the version
you want, and then you'll be able to pick up all of the patches to
other recip
Hi,
I'm currently using Yocto Sumo 2.5 release with the glibc version 2.27 and
would like to upgrade it to v2.28.
Using the devtool upgrade glibc -V 2.28
-S 044c96f0d5595aeb0bb4e79355081c5a7f4faca5 doesn't work as expected.
In turn it creates the workspace/recipes/glibc_2.28.bb recipe with the
con
Signed-off-by: Adrian Bunk
---
recipes-security/xmlsec1/{xmlsec1_1.2.26.bb => xmlsec1_1.2.27.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename recipes-security/xmlsec1/{xmlsec1_1.2.26.bb => xmlsec1_1.2.27.bb} (93%)
diff --git a/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
b/re
Usually one doesn't need variants for all 4 different
crypto libraries installed at the same time.
Also remove a libgpg-error DEPENDS that is not used
directly by xmlsec1.
Signed-off-by: Adrian Bunk
---
recipes-security/xmlsec1/xmlsec1_1.2.26.bb | 10 ++
1 file changed, 6 insertions(+),
They can be dynamically loaded with xmlSecCryptoDLLoadLibrary().
Signed-off-by: Adrian Bunk
---
recipes-security/xmlsec1/xmlsec1_1.2.26.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
b/recipes-security/xmlsec1/xmlsec1_1.2.26.bb
index 2dbbf
13 matches
Mail list logo