Some binaries generated by util-linux will be replaced by core-utils
in the final image by update-alternatives, so use a dedicated directory
with symlinks to avoid using a binary generated by another package.
This will solve the issue with the ptest runner timing out when
running the kill ptests
This adds the functionality to create a binary directory within
PTEST_PATH directory. This directory will be populated with
symlinks pointing to the binaries installed by the package and
then renamed by update-alternatives. This way the ptest only needs
to source this binary directory in order to
This will generate the symlinks in the ptest binary directory using the
ptest class functionality instead of generating them manually. Because
the ptest class uses update-alternatives to get the metadata for the
symlinks it will respect the use of BUSYBOX_SPLIT_SUID automatically.
[YOCTO #12597]
This adds update_alternatives_alt_targets function to get the metadata
for a package. This is for code reuse because the metadata would help
other classes that needs to be aware of how update-alternatives modify
the final package.
[YOCTO #12597]
[YOCTO #13238]
Signed-off-by: Mariano Lopez
---
Some binaries are renamed by update-alternatives class at build time
and some ptest run against a binary belonging to another package. Take
for example busybox or util-linux.
This series adds a directory within the ptest with symlinks to the
binaries produced by the package, so just adding this
On Mon, Apr 8, 2019 at 7:32 PM wrote:
>
> From: Mingli Yu
>
> When DEBUG_BUILD = "1" added in local.conf, there
> comes below build error when "bitbake gcc-sanitizers":
> |
> ./../../../../../../../../work-shared/gcc-8.3.0-r0/gcc-8.3.0/libsanitizer/libbacktrace/../../libbacktrace/elf.c:
> In
From: Mingli Yu
When DEBUG_BUILD = "1" added in local.conf, there
comes below build error when "bitbake gcc-sanitizers":
|
./../../../../../../../../work-shared/gcc-8.3.0-r0/gcc-8.3.0/libsanitizer/libbacktrace/../../libbacktrace/elf.c:
In function 'elf_is_symlink':
|
From: Nikhil Pal Singh
Support project-file generators such as CodeBlocks, CodeLite,
Eclipse, Sublime, and Kate for both make and Ninja build systems.
The following generators are listed in cmake --help:
Unix Makefiles = Generates standard UNIX makefiles.
Ninja
Can you put that in the commit message, because I tried googling and
didn't find that list. Maybe also expand the comment.
Ross
On Mon, 8 Apr 2019 at 22:12, Douglas Royds wrote:
>
> On 9/04/19 9:04 AM, Burton, Ross wrote:
>
> On Mon, 8 Apr 2019 at 21:56, Douglas Royds
> wrote:
>
> python()
On 9/04/19 9:04 AM, Burton, Ross wrote:
On Mon, 8 Apr 2019 at 21:56, Douglas Royds wrote:
python() {
generator = d.getVar("OECMAKE_GENERATOR")
-if generator == "Unix Makefiles":
-args = "-G 'Unix Makefiles' -DCMAKE_MAKE_PROGRAM=" + d.getVar("MAKE")
+if "Unix Makefiles"
On Mon, 8 Apr 2019 at 21:56, Douglas Royds wrote:
> python() {
> generator = d.getVar("OECMAKE_GENERATOR")
> -if generator == "Unix Makefiles":
> -args = "-G 'Unix Makefiles' -DCMAKE_MAKE_PROGRAM=" + d.getVar("MAKE")
> +if "Unix Makefiles" in generator:
> +args = "-G
From: Nikhil Pal Singh
As per Generators information mentioned in the cmake --help file
only "Unix Makefiles" and "Ninja" generators are supported as
standard project files.
With this change generic solution can be created for all the other
supported generators such as CodeBlocks, CodeLite,
ELL has originally been part of meta-openembedded, but newer versions
of some of the poky components depend on it, e.g. ofono.
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-core/ell/ell_0.18.bb | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
Am 08.04.19 um 08:55 schrieb richard.pur...@linuxfoundation.org:
On Mon, 2019-04-08 at 07:43 +0200, Stefan Herbrechtsmeier wrote:
Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:
You're saying A runtime depends on B and B runtime depends on A.
Yes, only the run time depends on
On Mon, 8 Apr 2019 at 20:03, Alejandro del Castillo
wrote:
> +do_install_ptest() {
> + install -d ${D}${PTEST_PATH}
> + install -m 755 ${WORKDIR}/run-ptest ${D}/${PTEST_PATH}/run-ptest
> + install -m 755 ${B}/Makefile ${D}${PTEST_PATH}/Makefile
> + sed -i -e
Signed-off-by: Alejandro del Castillo
---
py-resolve-paths-before-comparision.patch | 31 +++
meta/recipes-devtools/opkg/opkg/run-ptest | 3 ++
meta/recipes-devtools/opkg/opkg_0.4.0.bb | 15 -
3 files changed, 48 insertions(+), 1 deletion(-)
create mode
This patch tried to address a gcc problem when -Og is used, but it did
cause regressions on normal compiles when using clang e.g. the real
problem is to fix the compiler until then disable the warning in
DEBUG_FLAGS
This reverts commit 630281663893cdcfa9c4323b717b415d87d5510f.
Signed-off-by:
On Sun, Apr 7, 2019 at 6:59 PM Kang Kai wrote:
>
> On 2019/4/4 下午3:52, kai.k...@windriver.com wrote:
> > From: Kai Kang
> >
> > When gcc compile options '-O2 -fvisibility=default' are applied, it
> > fails to compile virglrenderer for x86:
> >
> > | ld:
All,
The triage team meets weekly and does its best to handle the bugs reported
into the Bugzilla. The number of people attending that meeting has fallen,
as have the number of people available to help fix bugs. One of the things
we hear users report is they don't know how to help. We (the
On Mon, Apr 08, 2019 at 08:08:08PM +0530, akuster808 wrote:
>
>
> On 4/8/19 5:38 PM, Adrian Bunk wrote:
> > This is a new upstream release from the same stable branch
> > bringing new features and bugfixes (including CVE fixes).
> >
> > COPYING changed http -> https.
> >
> > configure no longer
On 4/8/19 5:38 PM, Adrian Bunk wrote:
> This is a new upstream release from the same stable branch
> bringing new features and bugfixes (including CVE fixes).
>
> COPYING changed http -> https.
>
> configure no longer has a --without-libunistring-prefix option.
Here is the same comment post
This is a new upstream release from the same stable branch
bringing new features and bugfixes (including CVE fixes).
COPYING changed http -> https.
configure no longer has a --without-libunistring-prefix option.
Signed-off-by: Adrian Bunk
---
.../gnutls/{gnutls_3.6.5.bb => gnutls_3.6.7.bb}
Bugfix-only compared to 9.11.5, mostly CVE fixes.
COPYRIGHT checksum changed due to 2018 -> 2019.
Signed-off-by: Adrian Bunk
---
.../bind/{bind_9.11.5.bb => bind_9.11.5-P4.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename
This change adds three patches to improve the handling of stdout/stderr and
child
processes to try and improve logging reliability in ptest-runner.
Signed-off-by: Richard Purdie
---
...ils-Ensure-stdout-stderr-are-flushed.patch | 45 +++
...002-use-process-groups-when-spawning.patch |
We need to run sed with the -u option to ensure the output is unbuffered else
ptest-runner may timeout thinkig things were idle. Busybox doesn't have the -u
option so we need to RDEPEND on sed (which is a good thing to do if we use it
anyway).
Alex Kanavin should get credit for discovering the
There is a python test which hangs with recent kernels, 5.0 onwards. This causes
ptest to timeout for python3. Disable the problematic test until we better
understand
the real cause and fix of the issue (discussions are happening with upstream).
See the patch for details/links.
Signed-off-by:
This message was using %s markers but nothing was being passed in.
Signed-off-by: Ross Burton
---
meta/classes/insane.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index c8d18c07f55..43df0046201 100644
---
On Sun, 2019-04-07 at 21:23 -0500, Mariano Lopez wrote:
> On 4/7/19 4:32 PM, Richard Purdie wrote:
> > On Sun, 2019-04-07 at 12:15 -0500, Mariano Lopez wrote:
> > > -
> > > -# Default to generate shell script.. eventually we
> > > may want to change this...
> > > -
On Mon, 2019-04-08 at 07:43 +0200, Stefan Herbrechtsmeier wrote:
> Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:
> > You're saying A runtime depends on B and B runtime depends on A.
>
> Yes, only the run time depends on each other. This means the
> dependency doesn't exist
From: Mingli Yu
When DEBUG_BUILD = "1" added in local.conf, there
comes below build error when "bitbake gcc-sanitizers":
|
./../../../../../../../../work-shared/gcc-8.3.0-r0/gcc-8.3.0/libsanitizer/libbacktrace/../../libbacktrace/elf.c:
In function 'elf_is_symlink':
|
From: Changqing Li
fix below compile error with -Werror=maybe-uninitialized
while DEBUG_BUILD is enabled
| ../../cogl-1.22.2/cogl/driver/gl/gles/cogl-driver-gles.c:217:17: error:
'gltype' may be used uninitialized in this function
[-Werror=maybe-uninitialized]
| *out_gltype = gltype;
|
31 matches
Mail list logo
