On Thu, May 24, 2018 at 4:58 AM, Khem Raj wrote:
> On Wed, May 23, 2018 at 9:26 PM, Andre McCurdy wrote:
>> On Tue, May 22, 2018 at 4:20 PM, Khem Raj wrote:
>>> Hi All,
>>>
>>> I am writing this to just paraphrase the patch flight
On Wed, May 23, 2018 at 9:26 PM, Andre McCurdy wrote:
> On Tue, May 22, 2018 at 4:20 PM, Khem Raj wrote:
>> Hi All,
>>
>> I am writing this to just paraphrase the patch flight process that is
>> in place more or less
>> and I am going to follow.
>>
>> We
On Tue, May 22, 2018 at 4:20 PM, Khem Raj wrote:
> Hi All,
>
> I am writing this to just paraphrase the patch flight process that is
> in place more or less
> and I am going to follow.
>
> We have patchwork instance where all patches from mailing list are captured
>
>
On Wed, May 23, 2018 at 9:03 PM, Alistair Francis wrote:
> On Wed, May 23, 2018 at 5:37 PM, Khem Raj wrote:
>> On Wed, May 23, 2018 at 5:58 PM, Alistair Francis
>> wrote:
>>> Update redis to the latest 4.0.8 release. This also
On Wed, May 23, 2018 at 5:58 PM, Alistair Francis
wrote:
> Update redis to the latest 4.0.8 release. This also involves updating
> the redis.conf while maintaining some OE specific config options.
>
fails on mips
| networking.o: In function `createClient':
|
Add native dependency on autoconf-archive as it is now used by the
libgpiod autotools.
Signed-off-by: Martin Hundebøll
---
meta-oe/recipes-support/libgpiod/libgpiod_1.0.1.bb | 4
meta-oe/recipes-support/libgpiod/libgpiod_1.1.bb | 6 ++
2 files changed, 6
Signed-off-by: Martin Hundebøll
---
meta-oe/recipes-support/libgpiod/libgpiod_1.1.bb | 8
1 file changed, 8 insertions(+)
diff --git a/meta-oe/recipes-support/libgpiod/libgpiod_1.1.bb
b/meta-oe/recipes-support/libgpiod/libgpiod_1.1.bb
index c2e11ad38..1bda8bc3a 100644
Some older compilers do not support security flags like -fstack-protector=strong
and if we do not set this then it will use the target flags to pass here
which will fail with gcc < 5.x, especially a problem building distros with
security flags on host with 4.x gcc e.g. ubuntu 14.04
Signed-off-by:
Some older compilers do not support security flags like -fstack-protector=strong
and if we do not set this then it will use the target flags to pass here
which will fail with gcc < 5.x, especially a problem building distros with
security flags on host with 4.x gcc e.g. ubuntu 14.04
Signed-off-by:
Signed-off-by: Khem Raj
---
.../0001-Fix-a-build-problem-on-Clang.patch | 28 +++
.../0002-Define-virtual-destructor.patch | 28 +++
.../recipes-support/cpprest/cpprest_2.10.2.bb | 8 --
3 files changed, 61 insertions(+), 3
Update redis to the latest 4.0.8 release. This also involves updating
the redis.conf while maintaining some OE specific config options.
Signed-off-by: Alistair Francis
---
...Makefile-to-add-symbols-to-staticlib.patch | 19 -
The ffmpeg no longer makes use of the AVFMT_RAWPICTURE format, but
opencv still has code in it for dealing with this type of exported
format. For now it is easier to work around it and allow the code to
compile and it will just not get used. A future version of OpenCV
will remove the
Update to new version and drop accepted patches.
Use autotools and packageconfig (for xattrs).
Signed-off-by: Andrea Adami
---
.../0001-Makefile-build-ubi-utils-only.patch | 87 --
.../0002-common.mk-for-klibc-CC-is-klcc.patch | 27 --
On Wed, 2018-05-23 at 12:37 +0100, André Draszik wrote:
> It looks like the files have changed, as the checksums for this 162b12
> update aren't right anymore...
>
> Starting to look into this, I wonder if the URLs used by the OpenJDK-8
> recipes are actually meant to be stable? The URL pattern
It looks like the files have changed, as the checksums for this 162b12
update aren't right anymore...
Starting to look into this, I wonder if the URLs used by the OpenJDK-8
recipes are actually meant to be stable? The URL pattern is
It is an efficient and necessary tool to reflect the status of X86
processors. Turbostat reports processor topology, frequency, idle
power-state statistics, temperature and power on X86 processors.
Signed-off-by: Hongzhi.Song
---
On 05/23/2018 10:54 AM, Martin Jansa wrote:
> Don't use github archives which are regenerated from time to time with
> different checksums (read older discussions for more details).
What should we use instead?
git clone?
My comments on that from the last patch version:
> Why should we change
Don't use github archives which are regenerated from time to time with
different checksums (read older discussions for more details).
On Wed, May 23, 2018 at 10:42 AM Richard Leitner <
richard.leit...@skidata.com> wrote:
> Add recipe for version 1.3 of pam-plugin-ldapdb, a PAM module for
>
Add recipe for version 1.3 of pam-plugin-ldapdb, a PAM module for
directly binding a user DN to an LDAP server.
Signed-off-by: Richard Leitner
---
Changes v2:
+ assign DEPENDS (instead of appending to it)
+ add downloadfilename to SRC_URI
+ append to FILES
On 05/22/2018 08:09 PM, Khem Raj wrote:
> On Tue, May 22, 2018 at 7:10 AM, Richard Leitner
> wrote:
>> Add recipe for version 1.3 of pam-plugin-ldapdb, a PAM module for
>> directly binding a user DN to an LDAP server.
>>
>> Signed-off-by: Richard Leitner
Hi Andre,
thank you for your feedback. Please find my comments below.
On 05/23/2018 02:51 AM, Andre McCurdy wrote:
> On Tue, May 22, 2018 at 4:10 AM, Richard Leitner
> wrote:
>> Add recipe for version 1.3 of pam-plugin-ldapdb, a PAM module for
>> directly binding a
21 matches
Mail list logo