GSocketClient in GNOME GLib through 2.62.4 may occasionally connect directly
to a target address instead of connecting via a proxy server when configured
to do so, because the proxy_addr field is mishandled. This bug is
timing-dependent
and may occur only sporadically depending on network delays.
From: Changqing Li
Otherwise .gir files installed in the sysroot will not be found when
multilib is in use.
for vapigen, it need to find .vapi and .gir files under XDG_DATA_DIRS,
for gobject-introspection, multilib configurations use libdir rather
than datadir
Signed-off-by: Changqing Li
---
For distros such as CentOS-7 where the default buildtools are too
old we need to make it easy for users to install a pre-built SDK
with all of "build-essentials" included.
Other uses may include building older Yocto Project releases with
a distro where buildtools are too new.
For convenience,
This patch has not yet been merged upstream and upstream has disputed the
security impact of this CVE. So I am not sure if we should take this.
https://github.com/glennrp/libpng/issues/269
Has any distro taken this?
Thanks,
Anuj
> -Original Message-
> From:
Trying to build mesa-gl without X11 enabled, results in numerous errors
about being incorrectly configured, such as:
ERROR: Problem encountered: building dri drivers require at least one
windowing system or classic osmesa
A rendering engine must be available, so per the error we enable osmesa
Set the json result output dir in the oeqe runtime context to create
testresults.json file by default for exported runtime test runs.
Use current datetime for the json result property name (not DATETIME
from build) to allow multiple result entries.
Signed-off-by: Stefan Kral
---
On Wed, Mar 25, 2020 at 3:15 PM Mark Hatle
wrote:
>
> Trying to build mesa-gl without X11 enabled, results in numerous errors
> about being incorrectly configured, such as:
>
> ERROR: Problem encountered: building dri drivers require at least one
> windowing system or classic osmesa
>
> After
On Wed, Mar 25, 2020 at 10:37:55PM +0100, Andrey Zhizhikin wrote:
> On Wed, Mar 25, 2020 at 9:36 PM Mark Hatle
> wrote:
> >
> > > On Wed, Mar 25, 2020 at 7:15 PM Mark Hatle
> > > wrote:
> > >>
> > >> Trying to build mesa-gl without X11 enabled, results in numerous errors
> > >> about being
On Wed, Mar 25, 2020 at 9:36 PM Mark Hatle
wrote:
>
> > On Wed, Mar 25, 2020 at 7:15 PM Mark Hatle
> > wrote:
> >>
> >> Trying to build mesa-gl without X11 enabled, results in numerous errors
> >> about being incorrectly configured, such as:
> >>
> >> ERROR: Problem encountered: building dri
> On Wed, Mar 25, 2020 at 7:15 PM Mark Hatle
> wrote:
>>
>> Trying to build mesa-gl without X11 enabled, results in numerous errors
>> about being incorrectly configured, such as:
>>
>> ERROR: Problem encountered: building dri drivers require at least one
>> windowing system or classic osmesa
>
On Wed, Mar 25, 2020 at 7:15 PM Mark Hatle
wrote:
>
> Trying to build mesa-gl without X11 enabled, results in numerous errors
> about being incorrectly configured, such as:
>
> ERROR: Problem encountered: building dri drivers require at least one
> windowing system or classic osmesa
I believe
> To be honest, I would just take the entire recipe out. It's causing
> trouble
> during updates, isn't being tested neither for builds nor at runtime, and
> is supposed to provide some specific configuration which as this
> discussion
> makes clear, nobody seems to quite understand.
With the
To be honest, I would just take the entire recipe out. It's causing trouble
during updates, isn't being tested neither for builds nor at runtime, and
is supposed to provide some specific configuration which as this discussion
makes clear, nobody seems to quite understand.
Alex
On Wed, 25 Mar
>> On Wed, Mar 25, 2020 at 01:14:47PM -0500, Mark Hatle wrote:
>>> Trying to build mesa-gl without X11 enabled, results in numerous errors
>>> about being incorrectly configured, such as:
>>>
>>> ERROR: Problem encountered: building dri drivers require at least one
>>> windowing system or
> On Wed, Mar 25, 2020 at 01:14:47PM -0500, Mark Hatle wrote:
>> Trying to build mesa-gl without X11 enabled, results in numerous errors
>> about being incorrectly configured, such as:
>>
>> ERROR: Problem encountered: building dri drivers require at least one
>> windowing system or classic
On Wed, Mar 25, 2020 at 01:14:47PM -0500, Mark Hatle wrote:
> Trying to build mesa-gl without X11 enabled, results in numerous errors
> about being incorrectly configured, such as:
>
> ERROR: Problem encountered: building dri drivers require at least one
> windowing system or classic osmesa
>
Trying to build mesa-gl without X11 enabled, results in numerous errors
about being incorrectly configured, such as:
ERROR: Problem encountered: building dri drivers require at least one
windowing system or classic osmesa
After consulting with the author of this recipe, it was clear that it
The fetcher GITDIR variable wase dropped a while back, drop the
obsolete reference to it (thanks Robert Day).
Signed-off-by: Richard Purdie
---
meta/lib/oe/recipeutils.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/lib/oe/recipeutils.py b/meta/lib/oe/recipeutils.py
index
On Mon, 2020-03-23 at 08:19 -0400, rpj...@crashcourse.ca wrote:
> cleaning up docs, and just noticed this from several months back:
>
> commit 4ff058226cfc3e7d5bf9a873d1de4475f65ef2f2
> Author: Andre McCurdy
> Date: Fri Aug 23 13:51:32 2019 -0700
>
> bitbake.conf: drop FETCHCMD, GITDIR,
These fetcher *DIR variables were dropped a while back, drop the docs
that reference them (thanks Robert Day).
Signed-off-by: Richard Purdie
---
meta/conf/documentation.conf | 3 ---
1 file changed, 3 deletions(-)
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index
On Fri, Mar 20, 2020 at 05:44:36PM -0700, Michael Halstead wrote:
> The migration to Groups.io is nearly complete. All functionality is ready
> to use and you can send e-mail now. Archives are in place except for the
> most recent from the Openembedded-commits list. Those are continuing to
>
Spilts out the inc file for u-boot-tools so that BSPs can include it for
their forked version of the tools, just like u-boot.inc.
As an example, this recipe [1] builds mkimage u-boot as part of the
u-boot recipe itself. This is incorrect because u-boot is a target
recipe, which means that the
The security flags were missing from the SDK toolchain
because they were added specifically to class-target.
Add them to class-cross-canadian as well (since the SDK environment
file is created from cross-canadian target flags).
Signed-off-by: Tom Hochstein
Signed-off-by: Antoine Manache
From: Lee Chee Yang
prevent cve-check from fatal error cause by network issue.
[YOCTO #13680]
Signed-off-by: Lee Chee Yang
---
meta/recipes-core/meta/cve-update-db-native.bb | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
On Wed, 2020-03-25 at 01:33 +, Tom Hochstein wrote:
> > -Original Message-
> > From: Richard Purdie
> > Sent: Tuesday, March 24, 2020 5:58 PM
> > To: Antoine Manache ; Tom Hochstein <
> > tom.hochst...@nxp.com>
> > Cc: openembedded-core@lists.openembedded.org
> > Subject: Re:
Spaces were previously converted to dashes, and underscores caused the
next character in the title/key to be printed using subscript due to the
enhanced string support in gnuplot.
Signed-off-by: Peter Kjellerstedt
---
scripts/contrib/bb-perf/buildstats-plot.sh | 4 ++--
1 file changed, 2
26 matches
Mail list logo
