On Tue, 2018-09-25 at 14:54 +0100, richard.pur...@linuxfoundation.org
wrote:
> On Tue, 2018-09-25 at 15:05 +0200, Urs Fässler wrote:
> > On Mon, 2018-09-24 at 15:26 +0200, Urs Fässler wrote:
> > > On Wed, 2018-09-19 at 09:01 -0700, Richard Purdie wrote:
> > > > On Wed, 2018-09-19 at 17:11 +0200, An
If the test case needs debug symbols then I'd suggest we just disable
that test. Especially as the test starts with this comment:
"NOTE: developer test! It's possible that it won't run on your\n",
"platform, and that's perfectly fine. This is mainly for developers\n",
Ross
On Mon, 1 Oct 2018 at
Append '\n' to the formatted string before return. If you write it
to the (manifest) file, it will ensure file ends with a newline.
Many GNU utilities have problems processing the last line of a file
if it is not '\n' terminated. E.g. if the last line is not terminated
by a newline character, then
Sorry for missing V2 in subject
//Hongxu
On 2018年10月01日 23:47, Hongxu Jia wrote:
The case in ptest use `nm -Pg libcrypto.so' to check symbol presence,
if library is stripped or debug split, the case will fail.
The dbg library keeps symbol table, so tweak to check on it.
Use wildcard `libcrypt
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 tr
The case in ptest use `nm -Pg libcrypto.so' to check symbol presence,
if library is stripped or debug split, the case will fail.
The dbg library keeps symbol table, so tweak to check on it.
Use wildcard `libcrypto.so*' rather than `libcrypto.so.1.1' to compat
the subsequent version upgrade.
The
On Sat, 2018-09-29 at 15:01 +0800, Kevin Hao wrote:
> When multilib is enabled, there would be two different recipe
> specific
> sysroot directories:
> libxx-recipe-sysroot
> recipe-sysroot
>
> We do need to access the files under the "recipe-sysroot" directory
> in some cases. So introduces t
Sure, sounds good.
On Mon, Oct 1, 2018 at 2:03 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Mon, 2018-10-01 at 11:12 +, Martin Jansa wrote:
> > * currently it's used only by image.bbclass, image_types.bbclass and
> > meta/recipes-core/images/build-appliance-image_15.0
On Sun, 2018-09-30 at 14:39 +0800, Hongxu Jia wrote:
> The case in ptest use `nm -Pg libcrypto.so.1.1' to check symbol
> presence,
> hence we need to inhibit package split and package debug split.
>
> The binutils provides `nm', hence add it to ptest runtime depends.
> (Without `nm', the test_symb
On Mon, 2018-10-01 at 11:12 +, Martin Jansa wrote:
> * currently it's used only by image.bbclass, image_types.bbclass and
> meta/recipes-core/images/build-appliance-image_15.0.0.bb
> but if it's needed by some recipe which isn't itself an image, then
> it's useful in bitbake.conf, e.g. we
== Series Details ==
Series: bitbake.conf: move IMAGE_NAME_SUFFIX variable from image_types.bbclass
Revision: 1
URL : https://patchwork.openembedded.org/series/14313/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response.
On Sat, 29 Sep 2018 at 10:35, Chen Qi wrote:
> -REQUIRED_DISTRO_FEATURES = "opengl"
But libepoxy is a GL wrapper, so what is this *actually* achieving?
The opengl DISTRO_FEATURE is deliberately vague and just means that
some form of OpenGL is available.
Ross
--
_
* currently it's used only by image.bbclass, image_types.bbclass and
meta/recipes-core/images/build-appliance-image_15.0.0.bb
but if it's needed by some recipe which isn't itself an image, then
it's useful in bitbake.conf, e.g. we have a recipe for creating
VirtualBox appliances which combi
>From the libepoxy web site:
"Epoxy is a library for handling OpenGL function pointer management for you"
libepoxy is essentially a glorified wrapper around dlopen()/dlsym().
Are you simply moving the failure from build time to run time?
libepoxy should be pulling in a GL implementation because t
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org core-boun...@lists.openembedded.org> On Behalf Of
> changqing...@windriver.com
> Sent: den 30 september 2018 04:00
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH] pango: fix ptest fail
15 matches
Mail list logo