Hi Khem,
We have an internal error web server, this patch breaks it:
You're accessing the development server over HTTPS, but it only supports HTTP
So I tried to use runsslserver, but it doesn't work either since the host is
Ubuntu 14.04 (python 2.7.6):
$ python manage.py runsslserver
[snip]
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-core/meta/target-sdk-provides-dummy.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/meta/target-sdk-provides-dummy.bb
b/meta/recipes-core/meta/target-sdk-provides-dummy.bb
index edf07c4a23..13741f0a64 100644
---
On Sun, Mar 03, 2019 at 04:20:49PM -0600, Joshua Watt wrote:
> On Sun, Mar 3, 2019 at 4:11 PM Joshua Watt wrote:
> >
> > On Sun, Mar 3, 2019 at 3:25 PM Tom Rini wrote:
> > >
> > > On Sun, Mar 03, 2019 at 03:21:12PM -0600, Joshua Watt wrote:
> > > > On Sun, Mar 3, 2019, 2:47 PM Tom Rini wrote:
>
On Sun, Mar 3, 2019 at 4:11 PM Joshua Watt wrote:
>
> On Sun, Mar 3, 2019 at 3:25 PM Tom Rini wrote:
> >
> > On Sun, Mar 03, 2019 at 03:21:12PM -0600, Joshua Watt wrote:
> > > On Sun, Mar 3, 2019, 2:47 PM Tom Rini wrote:
> > >
> > > > Hey all,
> > > >
> > > > As part of the
On Sun, Mar 3, 2019 at 3:25 PM Tom Rini wrote:
>
> On Sun, Mar 03, 2019 at 03:21:12PM -0600, Joshua Watt wrote:
> > On Sun, Mar 3, 2019, 2:47 PM Tom Rini wrote:
> >
> > > Hey all,
> > >
> > > As part of the packagegroup-core-base-utils series I noticed that
> > > with rm_work enabled like I
On Sun, Mar 03, 2019 at 03:21:12PM -0600, Joshua Watt wrote:
> On Sun, Mar 3, 2019, 2:47 PM Tom Rini wrote:
>
> > Hey all,
> >
> > As part of the packagegroup-core-base-utils series I noticed that
> > with rm_work enabled like I usually have, every build was starting over
> > with rebuilding
On Sun, Mar 3, 2019, 2:47 PM Tom Rini wrote:
> Hey all,
>
> As part of the packagegroup-core-base-utils series I noticed that
> with rm_work enabled like I usually have, every build was starting over
> with rebuilding linux-libc-headers and going down from there. I
> finished bisecting this now
Hey all,
As part of the packagegroup-core-base-utils series I noticed that
with rm_work enabled like I usually have, every build was starting over
with rebuilding linux-libc-headers and going down from there. I
finished bisecting this now and it comes down to:
commit
Add explicit separator "--" between options and arguments in "tar"
command to avoid mistakenly detection file with name starts with "-" as
an unknown option
Steps for reproduce issue:
* Add next variables into "conf/local.conf":
CC_append_pn-perl = " -MD -Ml,M"
CXX_append_pn-perl = " -MD
No, I simply pointed out that the upstream-status line is unnecessary. The
patch itself is fine.
Alex
> On 3 Mar 2019, at 18.57, Ivan Efimov wrote:
>
> Hi Alex,
>
> Do you mean "master" branch of OE-core?
>
> I tried to reproduce the same bug on "master" branch, but fail.
> I know, that
Hi Alex,
Do you mean "master" branch of OE-core?
I tried to reproduce the same bug on "master" branch, but fail.
I know, that the same bug with "--" missing in "tar" command line is present
in "master" branch,
but if it does not prevent success compilation, so i'm not sure, that my
On Sun, 3 Mar 2019 at 18:38, Ivan Efimov wrote:
> Upstream-Status: Pending
This is used only in patches to upstream source, and so not needed here.
Alex
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
Add explicit separator "--" between options and arguments in "tar"
command to avoid mistakenly detection file with name starts with "-" as
an unknown option
Steps for reproduce issue:
* Add next variables into "conf/local.conf":
CC_append_pn-perl = " -MD -Ml,M"
CXX_append_pn-perl = " -MD
Command line for target "libbtrfsutil/%.o" contained
double usage of '-o $@' option and causes compilation error:
cc1: error: too many filenames given
Upsteam-Status: Pending
Signed-off-by: Ivan Efimov
---
...01-Makefile-fix-double-o-compiler-option-using.patch | 17 +
On Sun, 2019-03-03 at 18:00 +0100, Alexander Kanavin wrote:
> This has been previously discussed: qemu doesn't properly reconfigure
> itself when settings change. Wipe tmp/ and things should just work.
or just clean qemu-native...
Cheers,
Richard
--
This has been previously discussed: qemu doesn't properly reconfigure
itself when settings change. Wipe tmp/ and things should just work.
Alex
On Sun, 3 Mar 2019 at 17:54, Oleksandr Kravchuk
wrote:
>
> This fixes the following build error:
>
> ../loader-fit.c:30:10: fatal error: libfdt.h: No
This fixes the following build error:
../loader-fit.c:30:10: fatal error: libfdt.h: No such file or directory
Signed-off-by: Oleksandr Kravchuk
---
meta/recipes-devtools/qemu/qemu-native_3.1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sat, 2019-03-02 at 17:57 -0800, akuster808 wrote:
>
> On 3/2/19 4:38 PM, Khem Raj wrote:
> > This was not compiled last time when testing aarch64
>
> The subject and body have conflicting archs.
> is it both?
I've tweaked the commit message...
Cheers,
Richard
--
On Sun, Mar 3, 2019 at 2:45 AM Vincent Prince
wrote:
>
> Khem,
>
> I'm not sure if we considere this issue as closed or if we need to dig
> root-cause here?
>
> I don't have any Go stuff on my build machine nor build docker.
> Also, those random crashes came with Thud version, I didn't have any
I think you need to actually re-send the patch there, not add the list
in a reply.
Alex
On Sun, 3 Mar 2019 at 15:12, Aditya Tayade wrote:
>
> Added correct mailing list.
>
>
> Thaks Alexander!!
>
>
> Regards,
> Aditya Tayade
>
>
>
> From: Alexander Kanavin
>
do_create_extlinux_config performs its own override processing
for several variables, so we have to explicitly add the label-
suffixed variable names to its vardeps to make sure that changes
get detected.
Signed-off-by: Matt Madison
---
meta/classes/uboot-extlinux-config.bbclass | 2 ++
1 file
Signed-off-by: Alexander Kanavin
---
meta-poky/conf/local.conf.sample | 4
1 file changed, 4 deletions(-)
diff --git a/meta-poky/conf/local.conf.sample b/meta-poky/conf/local.conf.sample
index 2775e15d748..00795ae6a3f 100644
--- a/meta-poky/conf/local.conf.sample
+++
As SDL was found to be buggy for virgl-based GL passthrough,
gtk+ is enabled to allow that use case.
Signed-off-by: Alexander Kanavin
---
meta-poky/conf/local.conf.sample | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/meta-poky/conf/local.conf.sample
This hasn't been the default for a long time (as some distros don't
support it), and with gtk+ being the new default shouldn't
be needed at all.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/qemu/qemu.inc | 8
1 file changed, 8 deletions(-)
diff --git
sdl frontend remains enabled and available.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/qemu/qemu_3.1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/qemu/qemu_3.1.0.bb
b/meta/recipes-devtools/qemu/qemu_3.1.0.bb
index
When Gtk+ and SDL are both enabled, qemu defaults to Gtk+.
This option allows to revert to the 'classic' frontend.
Signed-off-by: Alexander Kanavin
---
scripts/runqemu | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/runqemu b/scripts/runqemu
index ec6188ba4a2..bbf539a8e67 100755
Note that to actually use accelerated GL passthrough, there are two options
1) a suitable frontend need to be also enabled - gtk+ seems to work well,
sdl was found to be buggy.
2) it is also possible to render off-screen with -display egl-headless option,
and see the output with a VNC viewer
Note that the tests require that the host machine has a X display,
has mesa development files installed and is able to create OpenGL contexts.
Signed-off-by: Alexander Kanavin
---
meta-selftest/lib/oeqa/runtime/cases/virgl.py | 28 ++
meta/lib/oeqa/selftest/cases/runtime_test.py | 52
This removes confusion over where qemu frontends are enabled for
native/nativesdk builds: currently they are also set in local.conf.sample
from poky distro, and with this change that becomes the only place.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/qemu/qemu_3.1.0.bb | 2 +-
1
If in the future GL is enabled for SDL frontend, or some other
frontend, it would be useful to be able to differentiate.
Signed-off-by: Alexander Kanavin
---
scripts/runqemu | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index
Khem,
I'm not sure if we considere this issue as closed or if we need to dig
root-cause here?
I don't have any Go stuff on my build machine nor build docker.
Also, those random crashes came with Thud version, I didn't have any in
Sumo, but there was a lot of changes between these two versions.
On 03.03.2019 10:08, liu.min...@gmail.com wrote:
> From: Ming Liu
>
> We need export XDG_DATA_DIRS to be ${STAGING_DATADIR} for gdk-pixbuf*
> wrappers or else they will try to load mime from /usr/share/mime of the
> host machine.
This fixes a build issue I have seen on a Ubuntu 18.04 machine
On Fri, 2019-03-01 at 17:03 +0800, Zang Ruochen wrote:
> upgrade from elfutils_0.175.bb to elfutils_0.176.bb
>
> Signed-off-by: Zang Ruochen
> ---
> .../elfutils/{elfutils_0.175.bb => elfutils_0.176.bb} | 4
> ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename
From: Ming Liu
We need export XDG_DATA_DIRS to be ${STAGING_DATADIR} for gdk-pixbuf*
wrappers or else they will try to load mime from /usr/share/mime of the
host machine.
Signed-off-by: Ming Liu
---
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf_2.38.0.bb | 5 +
1 file changed, 5 insertions(+)
34 matches
Mail list logo
