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...
> > > -alt_target
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 during
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;
|
Hi,Am 07.04.2019 23:35 schrieb richard.pur...@linuxfoundation.org:On Sun, 2019-04-07 at 21:18 +0200, Stefan Herbrechtsmeier wrote:
> I'm working towards an integrated Node.js support without npm and
> have a problem with a circular dependency of do_populate_sysroot for
> the native build.
>
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...
-alt_target = os.path.normpath(alt_target)
-
-alt_setup_links += '\tupdate-alt
On 4/4/19 9:42 PM, Burton, Ross wrote:
+Upstream-Status: Submitted
[https://github.com/GNOME/cogl/pull/4/commits/be7a7b983952d3f2ce2cbaa7b89f413b92e15066]
The pull request has automatically forwarded to GNOME gitlab, I will
send a V2 to fix this.
That's a GNOME mirror, note how your PR was
On 4/4/19 4:11 PM, Adrian Bunk wrote:
On Thu, Apr 04, 2019 at 10:06:44AM +0800, Changqing Li wrote:
...
And also upstream have use same way to fix under
cogl/driver/gl/gl/cogl-driver-gl.c
https://gitlab.gnome.org/GNOME/cogl/commit/ca5226513eb64bceb38ca01994799c4e7cd9f5fa
Have they?
This look
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: gallium/auxiliary/.libs/libgallium.a(u_cpu_detect.o): relocation
R_386_GOTOFF against undefined symbol `util_cpu
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 u
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
---
m
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 f
On Sat, 2019-04-06 at 17:11 -0700, Khem Raj wrote:
> This reverts commit 630281663893cdcfa9c4323b717b415d87d5510f.
>
> Signed-off-by: Khem Raj
I know the answer but just for the benefit of the git logs, can we say
why please.
Cheers,
Richard
--
___
On Sun, 2019-04-07 at 21:18 +0200, Stefan Herbrechtsmeier wrote:
> I'm working towards an integrated Node.js support without npm and
> have a problem with a circular dependency of do_populate_sysroot for
> the native build.
>
> I have two recipes a.bb and b.bb which have no DEPENDS but a
> RDEPE
On Sun, 2019-04-07 at 12:15 -0500, Mariano Lopez wrote:
> python populate_packages_updatealternatives () {
> if not update_alternatives_enabled(d):
> return
>
> -pn = d.getVar('BPN')
> -
> # Do actual update alternatives processing
> -pkgdest = d.getVar('PKGD')
>
Hi,
I'm working towards an integrated Node.js support without npm and have a
problem with a circular dependency of do_populate_sysroot for the native
build.
I have two recipes a.bb and b.bb which have no DEPENDS but a
RDEPENDS_${PN} between each other. This is no problem for a cross build
b
Thanks for pointing that out! The busybox recipe provided me
insight on how to implement this series in a cleaner way.
I refactor the code and the v2 of the series can be found here:
http://lists.openembedded.org/pipermail/openembedded-core/2019-April/280981.html
Please do not integrate this serie
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 f
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
---
m
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 di
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 u
There are the commit I intend on sending a pull request for in two days.
Tuesday my timezone (IST)
Please provide feedback by then if there are any issues. This is mostly OEQA
changes. They have been througt the AB a-full and passed.
The following changes since commit 45032e30be70503faeee468159
24 matches
Mail list logo
