On 4/5/20 8:55 AM, Khem Raj wrote:
On Fri, Apr 3, 2020 at 5:54 PM Khem Raj wrote:
Hi Martin
I am seeing upm package failures, which I think are related to this change
https://errors.yoctoproject.org/Errors/Details/400570/
https://errors.yoctoproject.org/Errors/Details/400566/
https://errors.
elp/latest/module/FindPython3.html
Signed-off-by: Martin Kelly
---
meta/classes/cmake.bbclass | 3 +++
meta/classes/python3native.bbclass | 2 --
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index d91cf20130..94ed806
On 1/7/19 8:38 AM, Ross Burton wrote:
> Multilib SDKs differ only in the environment variables set, so
> nativesdk-meson's
> setup script needs to write a cross file for each environment.
>
> Rename the shipped meson.cross to meson.cross.template, as it cannot be used
> directly. Now that post-r
On 1/7/19 12:02 PM, Burton, Ross wrote:
> On Mon, 7 Jan 2019 at 19:03, Martin Kelly wrote:
>>> +with open(template_file) as in_file:
>>> +template = in_file.read()
>>> +output = Template(template).substitute(Environ())
>>> +
On 1/7/19 9:55 AM, Burton, Ross wrote:
> On Mon, 7 Jan 2019 at 17:54, Martin Kelly wrote:
>> Could you elaborate on exactly what is breaking, or do you have a link
>> to the autobuilder breakage?
>>
>> To give a bit of background, cmake handles this by putting en
to adding
it), so we are left with generating paths at relocate time.
> On Fri, 1 Jun 2018 at 22:04, Martin Kelly wrote:
>>
>> Currently, we can't build meson into SDKs because we don't autogenerate
>> the required meson.cross file.
>>
>> Enable this
t; ]; then
exit 0
Reviewed-by: Martin Kelly
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
On 06/05/2018 05:04 AM, Peter Kjellerstedt wrote:
-Original Message-
From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
Sent: den 5 juni 2018 12:37
To: Peter Kjellerstedt ; Martin Kelly
; openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 1/6
Currently, we can't build meson into SDKs because we don't autogenerate
the required meson.cross file.
Enable this by using the post-relocate hooks and generating a
meson.cross file based on the SDK environment passed into the
post-relocate hook.
Signed-off-by: Martin Kelly
---
me
It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order to
dynamically generate toolchain files.
To enable this, source the SDK environment script prior to calling the
relocate scripts.
Signed-off-by: Martin
: Martin Kelly
---
v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
previous patch.
...0004-Prettifying-some-output-with-pathlib.patch | 188 +
...on-command-to-use-when-we-know-what-it-is.patch | 851 +
meta/recipes-devtools/meson
Currently, if a post-relocate script fails, it fails silently. We should
be louder about this, as it likely indicates a broken SDK.
Print a message if a post-relocate script fails.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 5 +
1 file changed, 5 insertions
Two functions is uses a mix of spaces and tabs. The rest of the file
uses tabs, so switch to tabs uniformly.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/meta/classes/toolchain
.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146262.html
v3:
- Implement review feedback from Joshua Watt (thanks!).
v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
previous patch.
Martin Kelly (6):
toolchain-scripts: retab file
Currently, we look only for scripts matching *.sh, which means we can't
write post-relocate scripts in other languages.
Expand this to allow any type of script.
Signed-off-by: Martin Kelly
---
v3:
- Test for executability prior to running each script.
meta/classes/toolchain-scripts.bb
On 06/04/2018 11:42 AM, Joshua Watt wrote:
On Mon, 2018-06-04 at 11:24 -0700, Martin Kelly wrote:
On 06/04/2018 11:20 AM, Joshua Watt wrote:
On Mon, 2018-06-04 at 11:10 -0700, Martin Kelly wrote:
On 06/04/2018 10:20 AM, Joshua Watt wrote:
On Fri, 2018-06-01 at 15:24 -0700, Martin Kelly wrote
On 06/04/2018 11:20 AM, Joshua Watt wrote:
On Mon, 2018-06-04 at 11:10 -0700, Martin Kelly wrote:
On 06/04/2018 10:20 AM, Joshua Watt wrote:
On Fri, 2018-06-01 at 15:24 -0700, Martin Kelly wrote:
On 06/01/2018 03:08 PM, Joshua Watt wrote:
On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote
On 06/04/2018 10:20 AM, Joshua Watt wrote:
On Fri, 2018-06-01 at 15:24 -0700, Martin Kelly wrote:
On 06/01/2018 03:08 PM, Joshua Watt wrote:
On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:
It's useful for the post-relocate scripts to be able to see the
SDK
environment, for examp
On 06/01/2018 03:08 PM, Joshua Watt wrote:
On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:
It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order
to
dynamically generate toolchain files.
To enable
On 06/01/2018 02:57 PM, Joshua Watt wrote:
On Fri, 2018-06-01 at 14:02 -0700, Martin Kelly wrote:
Currently, if a post-relocate script fails, it fails silently. We
should
be louder about this, as it likely indicates a broken SDK.
Print a message if a post-relocate script fails.
Signed-off-by
: Martin Kelly
---
v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
previous patch.
...0004-Prettifying-some-output-with-pathlib.patch | 188 +
...on-command-to-use-when-we-know-what-it-is.patch | 851 +
meta/recipes-devtools/meson
Currently, we can't build meson into SDKs because we don't autogenerate
the required meson.cross file.
Enable this by using the post-relocate hooks and generating a
meson.cross file based on the SDK environment passed into the
post-relocate hook.
Signed-off-by: Martin Kelly
---
me
It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order to
dynamically generate toolchain files.
To enable this, source the SDK environment script prior to calling the
relocate scripts.
Signed-off-by: Martin
Currently, we look only for scripts matching *.sh, which means we can't
write post-relocate scripts in other languages.
Expand this to allow any type of script.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Currently, if a post-relocate script fails, it fails silently. We should
be louder about this, as it likely indicates a broken SDK.
Print a message if a post-relocate script fails.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 5 +
1 file changed, 5 insertions
The native override is specified in two different places, so let's move
it into a function to reduce code duplication.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/meta/classes/meson.bbcl
ore commit 8fe9fb4d5a61dcbcb3fc5b9ee0234cc135af873f
("python*native.bbclass: suppress user site dirs").
Signed-off-by: Martin Kelly
---
meta/recipes-devtools/python/python-scons-native_3.0.1.bb | 2 +-
meta/recipes-devtools/python/python3_3.5.5.bb | 2 +-
meta/recipes-devtools/python/python_2.7.1
.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146262.html
v2:
- Switch to new version of patches to fix exe wrappers, as upstream tweaked the
previous patch.
Martin Kelly (7):
meson.bbclass: refactor native override
nativesdk-python*: suppress user site dirs
: Martin Kelly
---
...ke-ExternalProgram-get_path-a-bit-smarter.patch | 58 ++
...mandrunner-make-run-handle-python-options.patch | 53 +
.../0006-mesonlib-handle-meson-exe-wrappers.patch | 231 +
meta/recipes-devtools/meson/meson_0.46.1.bb| 3 +
4 files changed
The native override is specified in two different places, so let's move
it into a function to reduce code duplication.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/meta/classes/meson.bbcl
.html
http://lists.openembedded.org/pipermail/openembedded-core/2018-January/146262.html
Martin Kelly (7):
meson.bbclass: refactor native override
nativesdk-python*: suppress user site dirs
toolchain-shar-extract: allow non-sh post-relocate
toolchain-shar-extract: print post-relocate error
It's useful for the post-relocate scripts to be able to see the SDK
environment, for example to see the values of CC, CXX etc. in order to
dynamically generate toolchain files.
To enable this, source the SDK environment script prior to calling the
relocate scripts.
Signed-off-by: Martin
Currently, we look only for scripts matching *.sh, which means we can't
write post-relocate scripts in other languages.
Expand this to allow any type of script.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Currently, if a post-relocate script fails, it fails silently. We should
be louder about this, as it likely indicates a broken SDK.
Print a message if a post-relocate script fails.
Signed-off-by: Martin Kelly
---
meta/classes/toolchain-scripts.bbclass | 5 +
1 file changed, 5 insertions
ore commit 8fe9fb4d5a61dcbcb3fc5b9ee0234cc135af873f
("python*native.bbclass: suppress user site dirs").
Signed-off-by: Martin Kelly
---
meta/recipes-devtools/python/python-scons-native_3.0.1.bb | 2 +-
meta/recipes-devtools/python/python3_3.5.5.bb | 2 +-
meta/recipes-devtools/python/python_2.7.1
Currently, we can't build meson into SDKs because we don't autogenerate
the required meson.cross file.
Enable this by using the post-relocate hooks and generating a
meson.cross file based on the SDK environment passed into the
post-relocate hook.
Signed-off-by: Martin Kelly
---
me
On 05/08/2018 12:29 PM, Martin Jansa wrote:
Hi Martin,
all meta-oe patches need to go to openembedded-devel ML.
Thanks
Of course, my bad. Resent now to oe-devel.
On Tue, May 8, 2018 at 8:49 PM, Martin Kelly <mailto:mke...@xevo.com>> wrote:
This version has a ublox plugin for
The current string used to disable mbim is "--enable-mbim=no", which is
producing a warning. It should be "--with-mdim=no", so change it.
Signed-off-by: Martin Kelly
---
meta-oe/recipes-connectivity/modemmanager/modemmanager_1.7.991.bb | 2 +-
1 file changed, 1 insertion(+),
This is needed for the next version of modemmanager.
Signed-off-by: Martin Kelly
---
A similar patch was also sent by Khem Raj; that patch is just as good, but I
wanted to send this in the same series because the modemmanager upgrade requires
a libmbim upgrade.
.../libmbim/{libmbim_1.14.0.bb
This version has a ublox plugin for expanded modem support. The underlying issue
that enum-conversion.patch fixes appears to already have been fixed upstream, so
we can drop the patch.
Signed-off-by: Martin Kelly
---
.../modemmanager/modemmanager/enum-conversion.patch | 21
On 04/25/2018 04:11 PM, Martin Jansa wrote:
There are actually 3 we need to consider for lowest common denominator.
The one we build for, the one we build on and the one where we will run
the qemu in the end.
I mean the core2duo is probably best match for core2-64 DEFAULT used by
qemux86-64
On 04/25/2018 12:54 PM, Martin Jansa wrote:
On Thu, Jun 15, 2017 at 05:37:50PM +0100, Burton, Ross wrote:
On 15 June 2017 at 17:17, Martin Kelly wrote:
I am no expert, but running qemu -cpu help just says:
kvm32 - "Common 32-bit KVM processor"
kvm64 - "Common 64-bit KVM proc
me as before.
Signed-off-by: Chen Qi
Signed-off-by: Ross Burton
Signed-off-by: Martin Kelly
---
meta/recipes-devtools/python/python3-setuptools_32.1.1.bb | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/python/python3-setuptools_32.1.1.bb
b/meta/re
On 02/06/2018 06:28 PM, Joshua Watt wrote:
On Tue, 2018-02-06 at 15:39 -0800, Martin Kelly wrote:
(ping)
Paul, what do you about the options we have here for making meson
work
properly in the SDK?
To recap, here are the available options. I'm wondering if you could
give your opinion o
time.
- Wrap meson with a shell script that dynamically generates a toolchain
file and then runs meson pointing to it.
- Change meson to support pulling in env vars in meson.cross, and use a
fixed meson.cross file that references the env vars.
On 01/17/2018 09:47 AM, Martin Kelly wrote:
Paul, any op
Also, other packages like python3-setuptools are already doing the same with
their binaries.
Signed-off-by: Denys Dmytriyenko
Signed-off-by: Ross Burton
Signed-off-by: Martin Kelly
---
meta/recipes-devtools/python/python3-nose_1.3.7.bb | 4
1 file changed, 4 insertions(+)
diff --git a
CURITY_NO_PIE_CFLAGS
Signed-off-by: Khem Raj
Signed-off-by: Ross Burton
Signed-off-by: Martin Kelly
---
meta/classes/distutils-common-base.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/distutils-common-base.bbclass
b/meta/classes/distutils-common-base.bbclass
index 824
ar in meson.cross and should be pulled in indirectly by
MESON_C_ARGS and MESON_LINK_ARGS.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index 4ab242dcfd..91ac652651 1
. This is similar to what cmake.bbclass does with
OECMAKE_C_FLAGS and OECMAKE_CXX_FLAGS.
Change c_args and cpp_args in meson.cross to include these vars, and
update write_config[vardeps] accordingly.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 10 ++
1 file changed, 6
n so meson will not add its own optimization flags.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/meson.bbclass b/meta/classes/meson.bbclass
index 4a4c51f840..f9cee00c07 100644
--- a/meta/classes/meson.bbclass
+++ b/me
Paul, any opinion?
On 01/12/2018 04:35 AM, Alexander Kanavin wrote:
On 01/11/2018 09:22 PM, Martin Kelly wrote:
Khem and Alexander, could you comment on which solution is preferable
from an SDK standpoint? Otherwise, could you nominate someone else to
do so in your place? :)
I'm not
On 01/11/2018 11:33 AM, Martin Kelly wrote:
On 01/11/2018 11:26 AM, Khem Raj wrote:
On Thu, Jan 11, 2018 at 11:22 AM, Martin Kelly wrote:
Khem and Alexander, could you comment on which solution is preferable
from
an SDK standpoint? Otherwise, could you nominate someone else to do
so in
your
On 01/11/2018 11:26 AM, Khem Raj wrote:
On Thu, Jan 11, 2018 at 11:22 AM, Martin Kelly wrote:
Khem and Alexander, could you comment on which solution is preferable from
an SDK standpoint? Otherwise, could you nominate someone else to do so in
your place? :)
Here are the possible solutions
On 01/11/2018 09:49 AM, Richard Purdie wrote:
On Thu, 2018-01-11 at 13:35 +0200, Alexander Kanavin wrote:
On 01/10/2018 09:11 PM, Martin Kelly wrote:
Yes, to be clear, I'm not griping, as I'm very happy meson landed
in
OE-core, and I'm working on SDK support now. I have an
script that dynamically generates a toolchain
file and then runs meson pointing to it.
- Change meson to support pulling in env vars in meson.cross, and use a
fixed meson.cross file that references the env vars.
On 01/09/2018 12:33 PM, Martin Kelly wrote:
On 01/09/2018 10:40 AM, Jussi Pakkanen
On 01/10/2018 10:48 AM, Richard Purdie wrote:
On Wed, 2018-01-10 at 09:55 -0800, Martin Kelly wrote:
On 01/05/2018 06:57 AM, Alexander Kanavin wrote:
On 01/05/2018 01:47 PM, Burton, Ross wrote:
Do we even need gnomebase-meson with this? I can see a future
where
GNOME is entirely Meson and
On 01/05/2018 06:57 AM, Alexander Kanavin wrote:
On 01/05/2018 01:47 PM, Burton, Ross wrote:
Do we even need gnomebase-meson with this? I can see a future where
GNOME is entirely Meson and then we could just switch the default
GNOMEBASEBUILDCLASS from autotools to meson.
(prior art being the
On 01/09/2018 10:40 AM, Jussi Pakkanen wrote:
On Tue, Jan 9, 2018 at 8:20 PM, Martin Kelly wrote:
Note the "native C compiler" line, which directly uses $CC.
I'm not sure if this is correct, but an easy way to fix the issue is to
ignore $CC for internal sanity checking when
On 01/09/2018 02:06 AM, Nirbheek Chauhan wrote:
On Tue, Jan 9, 2018 at 3:20 PM, Nirbheek Chauhan
wrote:
If we want to setup a cross-file to use these arguments, we would have to
generate the cross-file on-the-fly (not good).
Out of interest, why is that not good? That is precisely what Gentoo
+CC Khem Raj, who has done a lot of work on the SDK and may have an
opinion about handling relocatable cross files.
On 01/09/2018 01:50 AM, Nirbheek Chauhan wrote:
On Tue, Jan 9, 2018 at 5:21 AM, Martin Kelly wrote:
[Jussi Pakkanen, Nirbheek Chauhan, I know you may not be on the list; I
[Jussi Pakkanen, Nirbheek Chauhan, I know you may not be on the list; I
added you to get Yocto/OE and meson upstream all on the same thread to
discuss integrating the two]
Hi all,
Recently, we got meson added to OE-core as part of Yocto (thanks
Alexander Kanavin!). That said, it doesn't yet w
On 11/16/2017 09:52 AM, Alexander Kanavin wrote:
On 11/15/2017 07:53 PM, Martin Kelly wrote:
+meson_do_configure_prepend_class-native() {
+ export PKG_CONFIG="pkg-config-native"
+}
+
What does this bit do? Should it go to a separate patch?
Alex
This is from Ross Burton'
me service wasn't enabled when it should be. Again,
systemctl *should* fail and cause a build failure if that happens, but
there could be some bug.
On 11/09/2017 05:01 PM, Martin Kelly wrote:
Got it, thanks. My patch *should* just convert runtime failures into
compile-time failures, but it l
kport the fixes to Morty.
Regards,
Javier Viguera
--
Jan Kiszka (1):
tcf-agent: Fix daemon termination
Martin Kelly (1):
tcf-agent: kill with USR2 in systemd stop
meta/recipes-devtools/tcf-agent/tcf-agent/tcf-agent.init| 12 +---
meta/recipes-devtools/tcf-agent/tcf-agen
This is expected, as the patch is intended to apply to Alexander
Kanavin's poky-contrib akanavin/meson branch, not oe-core master.
On 11/15/2017 10:02 AM, Patchwork wrote:
== Series Details ==
Series: meson bugfix
Revision: 1
URL : https://patchwork.openembedded.org/series/9809/
State : fail
This patch is intended to be applied on top of Alexander Kanavin's poky-contrib
branch akanavin/meson in preparation for meson moving into OE-core.
Martin Kelly (1):
meson: export native env only for native build
meta/classes/meson.bbclass | 23 ---
1 file change
other native vars *only* for the
native build. For target builds, these vars will get overridden by the
cross file as we expect.
Signed-off-by: Martin Kelly
---
meta/classes/meson.bbclass | 23 ---
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git a/meta/classes
Hi,
It looks to me like there are some changes here on top of a forked
meson.bbclass from meta-oe. Did you rebase the changes on top of current
meta-oe's meson? From a look at the git logs and file contents, it looks
like it needs a rebase or we may drop some patches.
On 11/15/2017 03:08 AM,
Correction: I took another look after merging in my meson patch, and I
think your branch is fully current.
On 11/15/2017 09:27 AM, Martin Kelly wrote:
Hi,
It looks to me like there are some changes here on top of a forked
meson.bbclass from meta-oe. Did you rebase the changes on top of
ut 2/2 was implicated in a number of systemd-related boot
failures on the autobuilder
(https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/553).
I've not yet got around to looking at exactly what sanity test 5 and 7
do to trigger this.
Ross
On 8 November 2017 at 17:40, Martin Ke
(ping) for this patch series.
On 10/16/2017 09:31 AM, Martin Kelly wrote:
The regex for acceptable systemd WantedBy/RequiredBy targets does not include
target.wants, so a line like this:
WantedBy=multi-user.target.wants
gets silently ignored, even though it works fine on a real system
The regex for acceptable systemd WantedBy/RequiredBy targets does not include
target.wants, so a line like this:
WantedBy=multi-user.target.wants
gets silently ignored, even though it works fine on a real system.
Signed-off-by: Martin Kelly
---
meta/recipes-core/systemd/systemd-systemctl
so that the user can fix these issues.
Signed-off-by: Martin Kelly
---
.../systemd/systemd-systemctl/systemctl| 37 ++
1 file changed, 30 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-core/systemd/systemd-systemctl/systemctl
b/meta/recipes-core/systemd
Currently, $HOME/.local is being added into sys.path for the native
Python, causing subtle host contamination. Suppress this by exporting
PYTHONNOUSERSITE = "1" as documented in PEP 370.
Signed-off-by: Martin Kelly
---
meta/classes/python3native.bbclass | 3 +++
me
On 07/18/2017 11:37 AM, Khem Raj wrote:
On Tue, Jul 18, 2017 at 12:21 PM, Martin Kelly wrote:
On 07/17/2017 07:47 PM, Khem Raj wrote:
On Mon, Jul 17, 2017 at 8:21 PM, Martin Kelly wrote:
Previously, we had a gst-python recipe, but it supported only GStreamer
0.1. After GStreamer switched
this point, we have a gobject-introspection class, so we can
use the bindings again, this time with GStreamer 1.0.
Signed-off-by: Martin Kelly
---
.../gstreamer/gstreamer1.0-python.inc | 35 ++
.../gstreamer/gstreamer1.0-python_1.10.4.bb| 7 +
2 files
On 07/17/2017 07:47 PM, Khem Raj wrote:
On Mon, Jul 17, 2017 at 8:21 PM, Martin Kelly wrote:
Previously, we had a gst-python recipe, but it supported only GStreamer
0.1. After GStreamer switched the Python bindings to use GObject
introspection, we were no longer able to build the bindings, and
this point, we have a gobject-introspection class, so we can
use the bindings again, this time with GStreamer 1.0.
Signed-off-by: Martin Kelly
---
.../gstreamer/gstreamer1.0-python.inc | 35 ++
.../gstreamer/gstreamer1.0-python_1.10.4.bb| 7 +
2 files
(ping)
On 07/10/2017 03:18 PM, Martin Kelly wrote:
The CDDL license is now used by open-vm-tools in meta-openembedded, so
we need to add it in order to prevent warnings.
Signed-off-by: Martin Kelly
---
meta/conf/licenses.conf | 4
1 file changed, 4 insertions(+)
diff --git a/meta/conf
Hi Armin,
Could we backport this patch to morty?
On 07/11/2017 12:39 PM, Khem Raj wrote:
On Tue, Jul 11, 2017 at 12:07 PM, Martin Kelly wrote:
Hi,
Is there any issue with backporting this to morty? It would help me fix a
build crash I'm seeing on morty, and I'm currently using th
Hi,
Is there any issue with backporting this to morty? It would help me fix
a build crash I'm seeing on morty, and I'm currently using the backport
in a separate repo with no issue.
On 06/28/2017 11:06 AM, Martin Kelly wrote:
On 05/26/2017 12:03 AM, Mirza Krak wrote:
From: Khem R
The CDDL license is now used by open-vm-tools in meta-openembedded, so
we need to add it in order to prevent warnings.
Signed-off-by: Martin Kelly
---
meta/conf/licenses.conf | 4
1 file changed, 4 insertions(+)
diff --git a/meta/conf/licenses.conf b/meta/conf/licenses.conf
index
On 05/26/2017 12:03 AM, Mirza Krak wrote:
From: Khem Raj
Fixes
| /usr/bin/ld: libcrypto.a(sha1-x86_64.o): relocation R_X86_64_PC32 against
undefined symbol `OPENSSL_ia32cap_P' can not be used when making a shared
object; recompile with -fPIC
| /usr/bin/ld: final link failed: Bad value
Signed
On 06/15/2017 04:45 AM, Burton, Ross wrote:
On 2 May 2017 at 20:20, Martin Kelly mailto:mke...@xevo.com>> wrote:
-QB_CPU_KVM_x86-64 = "-cpu kvm64"
+QB_CPU_KVM_x86-64 = "-cpu core2duo"
What's the actual meaning of the "kvm64" and "kvm32&
On 05/22/2017 11:09 AM, Martin Kelly wrote:
On 05/22/2017 10:53 AM, Randy Witt wrote:
On 05/22/2017 10:29 AM, Martin Kelly wrote:
(friendly ping)
On 05/02/2017 12:20 PM, Martin Kelly wrote:
Currently, the qemu CPUs for are specified as generic, but the built
artifacts are not. For example
On 06/13/2017 09:52 AM, Burton, Ross wrote:
On 13 June 2017 at 17:46, Martin Kelly mailto:mke...@xevo.com>> wrote:
Ah, I was checking meta-openembedded by mistake. Thanks.
The Best Known Method is to have a oe-core clone that you use for
pushing stuff upstream, and then you ca
On 06/13/2017 09:38 AM, Burton, Ross wrote:
On 13 June 2017 at 17:35, Martin Kelly mailto:mke...@xevo.com>> wrote:
Alright, makes sense. Do the patches look OK to you?
Yes, they're both in master now.
Ah, I was checking meta-openembedded by mist
On 06/07/2017 12:09 PM, Burton, Ross wrote:
On 7 June 2017 at 17:33, Martin Kelly mailto:mke...@xevo.com>> wrote:
Which patch are you referring to? I used git send-email for the
systemd patch, and it applies just fine for me on OE-core master
(using patch -p1).
Sorry, for
On 06/07/2017 09:08 AM, Burton, Ross wrote:
On 6 June 2017 at 18:28, Martin Kelly mailto:mke...@xevo.com>> wrote:
I sent a separate patch for fixing the systemd issue, so I think we
can merge the two patches separately (they're both needed):
https://patchwork.opene
On 06/06/2017 03:11 AM, Jan Kiszka wrote:
On 2017-06-01 02:17, Martin Kelly wrote:
On 05/02/2017 01:41 AM, Martin Kelly wrote:
On 04/30/2017 08:28 AM, Jan Kiszka wrote:
From: Jan Kiszka
The upstream init script uses SIGUSR2 to terminate that daemon because
SIGTERM is ignored. As the
On 06/01/2017 09:17 AM, Martin Kelly wrote:
On 05/02/2017 01:41 AM, Martin Kelly wrote:
On 04/30/2017 08:28 AM, Jan Kiszka wrote:
From: Jan Kiszka
The upstream init script uses SIGUSR2 to terminate that daemon because
SIGTERM is ignored. As the killproc function does not support specifying
a
systemd service
file. This patch fixes the systemd file.
Signed-off-by: Martin Kelly
---
meta/recipes-devtools/tcf-agent/tcf-agent/tcf-agent.service | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/tcf-agent/tcf-agent/tcf-agent.service
b/meta/recipes-devtools/tcf-agent/tcf
On 05/02/2017 01:41 AM, Martin Kelly wrote:
On 04/30/2017 08:28 AM, Jan Kiszka wrote:
From: Jan Kiszka
The upstream init script uses SIGUSR2 to terminate that daemon because
SIGTERM is ignored. As the killproc function does not support specifying
a signal, switch to start-stop-daemon. Drop
On 05/22/2017 10:53 AM, Randy Witt wrote:
On 05/22/2017 10:29 AM, Martin Kelly wrote:
(friendly ping)
On 05/02/2017 12:20 PM, Martin Kelly wrote:
Currently, the qemu CPUs for are specified as generic, but the built
artifacts are not. For example, we build x86-64 artifacts targeting
core2duo
(friendly ping)
On 05/02/2017 12:20 PM, Martin Kelly wrote:
Currently, the qemu CPUs for are specified as generic, but the built
artifacts are not. For example, we build x86-64 artifacts targeting
core2duo but run them in qemu with generic qemu/kvm CPUs. This causes
some packages that take
Signed-off-by: Martin Kelly
---
scripts/runqemu.README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/runqemu.README b/scripts/runqemu.README
index 5908d83..da9abd7 100644
--- a/scripts/runqemu.README
+++ b/scripts/runqemu.README
@@ -35,7 +35,7 @@ Notes
run as
this by making packages like Qt not take advantage of CPU
features. However, we will probably keep facing similar issues over
time, so it's better to resolve them in a more enduring way.
Fix this by making the qemu -cpu arguments match the built artifacts.
Signed-off-by: Martin Kelly
---
I
Looks like this is addressing the same problem as Jan's patch from
earlier today. I think the differences are:
- kill vs start-stop-daemon
- Jan removed the retry loop while this patch does not
On 05/01/2017 02:59 PM, brian avery wrote:
The current initscript was lacking a -USR2 signal in the
On 04/30/2017 08:28 AM, Jan Kiszka wrote:
From: Jan Kiszka
The upstream init script uses SIGUSR2 to terminate that daemon because
SIGTERM is ignored. As the killproc function does not support specifying
a signal, switch to start-stop-daemon. Drop the retry loop because
SIGUSR2 is lethal for age
On 04/24/2017 09:50 AM, Aníbal Limón wrote:
Hi Martin,
It looks that we need to improve the alignment between compiler flags
and runqemu configurations. I don't know if is the right way to change
the cpu's to pentium and core2due may be could cause side-effects.
I think will be better to review
1 - 100 of 121 matches
Mail list logo
