On 5/17/19 4:49 PM, Alejandro Enedino Hernandez Samaniego wrote:
Both python-numpy and python3-numpy try to install the file:
${D}/${bindir}/f2py
which causes an error during do_rootfs since the package manager complains
about that.
The numpy packages create basically copies of f2py
On 5/14/19 11:24 AM, Randy MacLeod wrote:
On 5/14/19 1:36 PM, Richard Purdie wrote:
On Mon, 2019-05-13 at 22:53 +, Alistair Francis wrote:
Signed-off-by: Alistair Francis
---
If there are issues with the patch the branch is avaliable here:
thanks for doing this work. This looks ok.
On 5/17/19 11:51 PM, Adrian Bunk wrote:
Signed-off-by: Adrian Bunk
---
...cy-ULONG_LONG_MAX-with-the-C99-ULLON.patch | 50 +++
...udev-event.c-must-include-sys-wait.h.patch | 35 +
Extern global variable `util_cpu_caps' to multiple C source files is
not a good habit, it caused linking failure when making a shard object
in some cross compiling circumstance
...
|ld: gallium/auxiliary/.libs/libgallium.a(u_cpu_detect.o): relocation
R_386_GOTOFF against undefined symbol
On 5/18/19 10:21 AM, Adrian Bunk wrote:
There's no point in building an NSS module for a C library
that doesn't support NSS.
this patch is ok
Signed-off-by: Adrian Bunk
---
...-Check-for-nss.h-presense-before-use.patch | 53 ---
On 5/18/19 10:21 AM, Adrian Bunk wrote:
There's no point in building an NSS module for a C library
that doesn't support NSS.
Fundamentally this change looks ok however
have you tried using avahi after this change ?
Signed-off-by: Adrian Bunk
---
On 5/17/19 11:11 AM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
.../{bash-completion_2.8.bb => bash-completion_2.9.bb} | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
rename meta/recipes-support/bash-completion/{bash-completion_2.8.bb =>
On 5/17/19 11:25 AM, akuster808 wrote:
On 5/17/19 11:11 AM, Alexander Kanavin wrote:
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/go/go-1.12.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/go/go-1.12.inc
On Sat, May 18, 2019 at 03:03:27PM -0400, Tom Rini wrote:
> On Sat, May 18, 2019 at 08:57:02PM +0200, Martin Jansa wrote:
> > Thanks Tom for quick update.
> >
> > ALTERNATIVE_TARGET[xxd] = "${bindir}/xxd"
> > ALTERNATIVE_LINK_NAME[xxd] = "${bindir}/xxd"
> > looks strange, IIRC TARGET and
From: Ming Liu
- Merge some DEPENDS lines.
- Drop some unnecessary 'cd ${DEPLOYDIR}' and 'rm -f'.
Signed-off-by: Ming Liu
---
meta/recipes-bsp/u-boot/u-boot.inc | 25 -
1 file changed, 8 insertions(+), 17 deletions(-)
diff --git a/meta/recipes-bsp/u-boot/u-boot.inc
From: Ming Liu
Instead, introduce a new item 'env' into UBOOT_CONFIG.
Ming Liu (2):
u-boot: clean up some redundant code
meta: drop IMAGE_FSTYPES from UBOOT_CONFIG
meta/classes/uboot-config.bbclass | 25 +---
meta/conf/documentation.conf | 2 +-
From: Ming Liu
Currently, in most BSP layers, the uboot-config.bbclass is not being
inherited in machine conf, so the IMAGE_FSTYPES item would not take
effect since it's a image specific variable, So we can drop it from
UBOOT_CONFIG.
Instead, we introduce a new item 'env', it could be used to
From: Ming Liu
This is mandatory to support multilib build, and also to avoid being
redundant with plenty of hard-coded alsa-utils references.
Signed-off-by: Ming Liu
---
meta/recipes-multimedia/alsa/alsa-utils_1.1.8.bb | 96
1 file changed, 48 insertions(+), 48
On Sat, May 18, 2019 at 08:57:02PM +0200, Martin Jansa wrote:
> Thanks Tom for quick update.
>
> ALTERNATIVE_TARGET[xxd] = "${bindir}/xxd"
> ALTERNATIVE_LINK_NAME[xxd] = "${bindir}/xxd"
> looks strange, IIRC TARGET and LINK_NAME should always point to different
> filepath, it was added in meta-oe
Thanks Tom for quick update.
ALTERNATIVE_TARGET[xxd] = "${bindir}/xxd"
ALTERNATIVE_LINK_NAME[xxd] = "${bindir}/xxd"
looks strange, IIRC TARGET and LINK_NAME should always point to different
filepath, it was added in meta-oe commit:
commit 897c10b7c17c138a85bdeb36cf72e7201daf0e0e
Author: Dan
Now that we have a common inc file for both vim and vim-tiny move a few
bits of logic out of vim.inc and in to vim_$VER.bb so that vim adds
things rather than vim-tiny removes them.
Suggested-by: Martin Jansa
Signed-off-by: Tom Rini
---
meta/recipes-support/vim/vim-tiny_8.1.1240.bb | 3 ---
Signed-off-by: Adrian Bunk
---
...NETDB_INTERNAL-to-1-if-not-available.patch | 32 ---
.../socat/socat_1.7.3.3.bb| 1 -
2 files changed, 33 deletions(-)
delete mode 100644
There's no point in building an NSS module for a C library
that doesn't support NSS.
Signed-off-by: Adrian Bunk
---
...-Check-for-nss.h-presense-before-use.patch | 53 ---
.../nss-myhostname/nss-myhostname_0.3.bb | 3 +-
2 files changed, 2 insertions(+), 54 deletions(-)
There's no point in building an NSS module for a C library
that doesn't support NSS.
Signed-off-by: Adrian Bunk
---
.../libnss-mdns/0001-check-for-nss.h.patch| 56 ---
.../libnss-mdns/libnss-mdns_0.10.bb | 3 +-
2 files changed, 2 insertions(+), 57 deletions(-)
Both python-numpy and python3-numpy try to install the file:
${D}/${bindir}/f2py
which causes an error during do_rootfs since the package manager complains
about that.
The numpy packages create basically copies of f2py script with the following
names:
f2py (on both)
f2py2 (on python 2)
There is no hard rule here, maybe a follow up is simpler.
Alex
> On 18 May 2019, at 13.35, Tom Rini wrote:
>
>> On Fri, May 17, 2019 at 04:34:14PM +0200, Alexander Kanavin wrote:
>>
>> This is up to the recipe maintainer (Tom) to do; I only want to ensure
>> AUH does not choke on the recipe.
On Fri, May 17, 2019 at 04:37:43PM -0700, Ross Burton wrote:
> The SRC_URI almost definitely shouldn't be using ${PN}, and GitHub */archive/*
> tarballs are dynamically generated so the checksums will change over time.
>...
It might be worth mentioning that this is for archive, not releases.
On Fri, May 17, 2019 at 04:34:14PM +0200, Alexander Kanavin wrote:
> This is up to the recipe maintainer (Tom) to do; I only want to ensure
> AUH does not choke on the recipe.
What's proper etiquette here? Shall I grab, v2 and include Martin's
suggestions, or follow-up and Suggested-by them?
Both python-numpy and python3-numpy try to install the file:
${D}/${bindir}/f2py
which causes an error during do_rootfs since the package manager complains
about that.
The numpy packages create basically copies of f2py script with the following
names:
f2py (on both)
f2py2 (on python 2)
Signed-off-by: Adrian Bunk
---
meta/recipes-support/icu/icu.inc | 7 ---
1 file changed, 7 deletions(-)
diff --git a/meta/recipes-support/icu/icu.inc b/meta/recipes-support/icu/icu.inc
index e20085fbf5..6d9728903d 100644
--- a/meta/recipes-support/icu/icu.inc
+++
On Fri, 17 May 2019 at 23:43, Adrian Bunk wrote:
> > -SRCREV = "2b3fc175c252cd5a537e4b2864b572a8372473d6"
> > +SRCREV = "3f51023aca06d28ccfb1d5383d99ca7fbfb287c8"
> > PV = "0.0.1+git${SRCPV}"
> > UPSTREAM_CHECK_COMMITS = "1"
>
> Upstream git contains a tagged 1.16.0 release.
Right, this is the
Signed-off-by: Adrian Bunk
---
...cy-ULONG_LONG_MAX-with-the-C99-ULLON.patch | 50 +++
...udev-event.c-must-include-sys-wait.h.patch | 35 +
...G_LONG_MAX-definition-in-case-of-mus.patch | 27 --
...-sys-wait.h-to-avoid-compile-failure.patch | 33
27 matches
Mail list logo
