Signed-off-by: Chen Qi
---
meta/recipes-graphics/libsdl/libsdl_1.2.15.bb | 2 ++
meta/recipes-graphics/libsdl2/libsdl2_2.0.9.bb | 2 ++
2 files changed, 4 insertions(+)
diff --git a/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
b/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
index
*** BLURB HERE ***
The following changes since commit 244cbcce0ecc4691a9ddfb0a44dc487ff7af0670:
utils/multiprocess_launch: Improve failing subprocess output (2019-04-26
10:09:08 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib ChenQi/libsdl-cve
On 2019年04月28日 18:55, Richard Purdie wrote:
On Sun, 2019-04-28 at 11:38 +0200, Alexander Kanavin wrote:
Wait, why is this a problem for specifically bjam, but not the other
tools that also look into PATH? Shouldn’t you fix the nfs instead?
I have to agree that you really don't want invalids
On Sat, Apr 27, 2019 at 10:11:36AM -0700, Khem Raj wrote:
> another issue I see
>
> https://errors.yoctoproject.org/Errors/Details/238569/
Are you sure this is related to the ninja change?
The error looks more as if it would be caused by the gtk-doc.bbclass
change (commit 07d29e7cec).
cu
On Sun, 2019-04-28 at 11:38 +0200, Alexander Kanavin wrote:
> Wait, why is this a problem for specifically bjam, but not the other
> tools that also look into PATH? Shouldn’t you fix the nfs instead?
I have to agree that you really don't want invalids NFS paths in PATH.
We're not carrying a patch
Wait, why is this a problem for specifically bjam, but not the other tools that
also look into PATH? Shouldn’t you fix the nfs instead?
Alex
> On 28 Apr 2019, at 9.02,
> wrote:
>
> From: Li Wang
>
> By default, it searches all paths specified by $PATH.
>
> But if the directory of the
On 2/19/19 3:05 PM, Changqing Li wrote:
On 2/14/19 7:19 PM, Richard Purdie wrote:
On Tue, 2019-02-12 at 13:10 +0800,changqing...@windriver.com wrote:
From: Changqing Li
The SDK was unable to find the C++ header pieces correctly since
it's
using a generic compiler, not one
On Sat, 2019-04-27 at 11:32 +0200, Alexander Kanavin wrote:
> This one is not about Mesa but rather failure to build recently
> updated vte-native due to host gcc being too ancient?
Yes, the mesa+musl problem is a valid issue, I hadn't realised the
virtgl-gtk issue was actually vte-native so that
Signed-off-by: Dengke Du
---
meta/recipes-kernel/linux/linux-yocto_5.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.0.bb
b/meta/recipes-kernel/linux/linux-yocto_5.0.bb
index fe773be..005dd8c 100644
---
From: Li Wang
By default, it searches all paths specified by $PATH.
But if the directory of the $PATH variable on
build host includes nfs(build host as nfs client),
it causes the build hung when the nfs server is
unavailable.
Signed-off-by: Li Wang
Signed-off-by: Mingli Yu
---
From: Li Wang
By default, it searches all paths specified by $PATH.
But if the directory of the $PATH variable on
build host includes nfs(build host as nfs client),
it causes the build hung when the nfs server is
unavailable.
Signed-off-by: Li Wang
---
11 matches
Mail list logo
