Re: [yocto] Error do_compile libepoxy

On 01/19/2018 05:29 AM, Andre McCurdy wrote: Note that this same test does build fine in poky, so disabling the tests is not a good fix. You should figure out what is about the non-poky EGL headers that is causing the failure, and whether you need to configure the provider of those headers

Re: [yocto] [Pyro] Multiple toolchains

2018-01-17 17:11 GMT+01:00 Herman van Hazendonk : > Hi Philippe, > > You might want to try to patch your kernel for newer GCC versions. We've > done that successfully with our 3.4 based kernels. See for example the > commits we used on our LG Hammerhead (Nexus 5) kernel. >

[yocto] Automated license incompatibility checks

Hi, I was looking for a way to analyze in more detail how packages of different licenses was used in an image, and stumbled upon this old mail-thread: https://lists.yoctoproject.org/pipermail/yocto/2015-January/023307.html My end goal is pretty much the same as Clemens, that I want to be able

Re: [yocto] Error do_compile libepoxy

On Thu, Jan 18, 2018 at 5:49 AM, Alexander Kanavin wrote: > On 01/18/2018 03:41 PM, Andrea Galbusera wrote: >> >> Yes, this is coherent with what Alexander's commit message says. We >> started building stuff in test/ while switching to meson... >> If we can't

[linux-yocto] [yocto-4.12][PULL REQUEST] update iwlwifi dirver to newest version to support 9560NGW

Hi Bruce, This series patch use to update iwlwifi driver to the newest version to support 9000 wifi card, as you know, the iwlwifi driver has changed more so the best way is to select all iwlwifi patch, this can aviod many patches adjust, meanwhile, it is good for us to backport patch from

Re: [yocto] [opkg-utils PATCH] update-alternatives: fix the sed pattern in remove_alt

Sorry I forgot adding opkg-devel, so I just re-sent with opkg-devel added in. Thanks, Jackie > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of jackie.hu...@windriver.com > Sent: Friday, January 19, 2018 10:54 > To:

[yocto] [opkg-utils PATCH] update-alternatives: fix the sed pattern in remove_alt

From: Jackie Huang '\>' is to matches the end of a word, but the executable is not always a 'word', e.g. /usr/lib64/busybox/usr/bin/[ then such alternatives can not be removed. So change to use '\s' in the pattern since the following character of the $path is

[yocto] [opkg-utils PATCH] update-alternatives: fix the sed pattern in remove_alt

From: Jackie Huang '\>' is to matches the end of a word, but the executable is not always a 'word', e.g. /usr/lib64/busybox/usr/bin/[ then such alternatives can not be removed. So change to use '\s' in the pattern since the following character of the $path is

Re: [yocto] Error do_compile libepoxy

Thanks Trevor - going in the right direction. There are no "GL" includes or libs in the recipe sysroot becuase userland does not provide it. Adding mesa-gl to DEPENDS allows it to complete. Not sure if this is the correct solution though. Michael Gloff On Thu, Jan 18, 2018 at 2:48 PM, Trevor

[yocto] [eclipse-poky][oxygen][PATCH] Update setup.sh to Oxygen.2 (4.7.2) release

From: Chin Huat Ang Signed-off-by: Chin Huat Ang Signed-off-by: Tim Orling --- scripts/setup.sh | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/scripts/setup.sh

[yocto] [meta-oic][PATCH resend 5/5] Add recipe for IoTivity 1.3.1

Note that fail on warning flag has been added, and can be used in .bbappend if needed after reporting bugs: http://wiki.iotivity.org/report Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- Origin:

[yocto] [meta-oic][PATCH resend 4/5] iotivity-sensorboard: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0003-server-Port-to-iotivity-1.2.0.patch | 68 ++ .../files/0004-build-Use-pkg-config.patch | 48 +++ .../iotivity-sensorboard_1.0.0.bb | 11

[yocto] [meta-oic][PATCH resend 3/5] iotivity-simple-client: Support pkg-config

Since IoTivity-1.3.0 Signed-off-by: Philippe Coval --- .../files/0002-build-Use-pkg-config.patch | 43 ++ .../iotivity-simple-client_1.1.0.bb| 8 +++- 2 files changed, 50 insertions(+), 1 deletion(-) create mode

[yocto] [meta-oic][PATCH resend 2/5] Add recipe for IoTivity 1.3.0

Note that SECURITY is now enabled but might cause issues on some examples. Bug: https://jira.iotivity.org/browse/IOT-2651 Signed-off-by: Philippe Coval --- README | 2 +-

[yocto] [meta-oic][PATCH resend 1/5] iotivity_1.2.1: Hotfix: Add ORIGIN rpath for binutils-2.29

Set RPATH to ORIGIN as supported by gcc/ld (-rpath=\$ORIGIN) Observed issue on poky master was: ld: warning: libconnectivity_abstraction.so, \ needed by out/yocto/x86_64/release/liboctbstack.so, not found (try using -rpath or -rpath-link) out/yocto/x86_64/release/liboctbstack.so: \

Re: [yocto] Error do_compile libepoxy

On Thu, Jan 18, 2018 at 10:05 AM, Michael Gloff wrote: > I can confirm adding #include to test/egl_common.c gets past > the original error, but then fails with: > > thank you for checking :-) > > > Log data follows: > | DEBUG: Executing shell function do_compile > | [1/2]

Re: [yocto] [poky] Fwd: How to make the os-release package work with local walltime instead of GMT?

On Mon, Jan 15, 2018 at 9:20 PM, Trevor Woerner wrote: > On Thu, Jan 11, 2018 at 12:26 AM, Robert Yang > wrote: >> >> BUILD_ID = "${@time.strftime('%Y-%m-%d %H:%M:%S',time.localtime())}" > > Brilliant! Why isn't this the default? Using localtime

[linux-yocto] [PATCH 1/2] bsp/axxiaarm: Add initial fragments

Fragments were ported from yocto-4.9 branch. Signed-off-by: Daniel Dragomir --- bsp/axxiaarm/axxiaarm-preempt-rt.scc | 8 + bsp/axxiaarm/axxiaarm-standard.scc | 8 + bsp/axxiaarm/axxiaarm.cfg| 285 +++

[linux-yocto] [PULL REQUEST] Intel Axxia updates to linux-yocto-4.12

Hello Bruce! This is the first pull request for Axxia changes on kernel 4.12 which were ported from our 4.9 Yocto branches. I checked all the patches with checkpatch.pl script and fixed all errors. Also, I compiled Axxia BSP using both branches and successfully booted the Victoria (arm64) board.

[linux-yocto] [PATCH 0/2] Intel Axxia updates to yocto-kernel-cache yocto-4.12

Hello Bruce! Please apply those patches on the 'yocto-4.12' branch from git.yoctoproject.org/yocto-kernel-cache This is a porting from 4.9 for AXXIA bsp fragments. Thank you, Daniel Dragomir (2): bsp/axxiaarm: Add initial fragments bsp/axxiaarm64: Add initial fragments

Re: [linux-yocto] [kernel-cache] [yocto-4.9] [PATCH] bsp/axxiaarm*: Enable some Axxia specific drivers

On 18.01.2018 17:28, Bruce Ashfield wrote: merged to the 4.9 branch. Let me know if it is also required on any newer kernels. Bruce I'll send soon the initial fragments for 4.12 which include this patch. Thanks, Daniel On 01/16/2018 12:47 PM, Daniel Dragomir wrote: AXXIA_FAULT: Axxia

[yocto] Release Candidate Build for yocto-2.2.3.rc2 now available.

A release candidate build for yocto-2.2.3.rc2 is now available at: https://autobuilder.yocto.io/pub/releases/yocto-2.2.3.rc2 Please begin QA on this build as soon as possible. Build hash information: meta-intel : c781510a5a6b45e60cc32b6614ddcce3f1452121 meta-qt4 :

Re: [linux-yocto] [yocto-4.12][PATCH] Mips kernel warining:resolve some warning when compiling arch/mips/math-emu/cp1emu.c

I had already merged this, when I realized that the patch headers are wrong on this. I'm not sure how you prepared and sent this, but make sure to not modify the shortlog, and put the "commit <> upstream", after the upstream shortlog. Bruce n 01/18/2018 01:04 AM, Hongzhi.Song wrote: From:

Re: [linux-yocto] [PATCH 4.12] drm/tilcdc: Precalculate total frametime in tilcdc_crtc_set_mode()

On 01/18/2018 02:30 PM, Kevin Hao wrote: From: Jyri Sarha commit ce99f7206c9105851d97202ed08c058af6f11ac4 upstream We need the total frame refresh time to check if we are too close to vertical sync when updating the two framebuffer DMA registers and risk a collision. This new

Re: [linux-yocto] [kernel-cache] [yocto-4.9] [PATCH] bsp/axxiaarm*: Enable some Axxia specific drivers

merged to the 4.9 branch. Let me know if it is also required on any newer kernels. Bruce On 01/16/2018 12:47 PM, Daniel Dragomir wrote: AXXIA_FAULT: Axxia Fault Handlers GPIO_AXXIA: PrimeCell PL061 GPIO support for Axxia EDAC_AXXIA_L3_5500: AXXIA EDAC L3 Controller for 5500 EDAC_AXXIA_L3_5600:

Re: [yocto] Error do_compile libepoxy

I can confirm adding #include to test/egl_common.c gets past the original error, but then fails with: Log data follows: | DEBUG: Executing shell function do_compile | [1/2] Compiling c object 'test/glx_beginend@exe/glx_beginend.c.o' | [2/2] Linking target test/glx_beginend | FAILED:

Re: [yocto] do_roots braking after a SRCREV update for non master branch

I'd check (using oe-pkgdata-util and/or buildhistory-diff) that the new package is building the same files and packages as the old one. If PN wasn't being generated, that would explain why the provides isn't working. Ross On 18 January 2018 at 14:46, Alan Martinovic

[yocto] do_roots braking after a SRCREV update for non master branch

Hi, I've updated my recipe to use a review from a non master branch: Old version [python3-senichub_git.bb]: inherit setuptools3 PROVIDES += "python3-senic-hub" RPROVIDES_${PN} += "python3-senic-hub" S = "${WORKDIR}/git" SRC_URI = "git://github.com/getsenic/senic-hub.git;"

[yocto] Add Python 3 custom package to native tools

Hi all, I want to add the Python 3 custom package foo to my native host tools to execute its executable in a class. How could I do that? I already inherited distutils3 to my foo recipe, but when I launch foo with oe-run-native, the error pkg_resources.DistributionNotFound: The 'foo=1.0'

Re: [yocto] Error do_compile libepoxy

On Thu, Jan 18, 2018 at 4:05 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 01/18/2018 10:58 AM, Andrea Galbusera wrote: > >> >> Looks like my first guess was not that bad. Reverting below commit, >> which switched to meson build system brought my build back to green. >>

Re: [yocto] Running cmake in the SDK environment from a script fails

2018-01-17 20:30 GMT+01:00 Bartosz Golaszewski : > Hi, > > I'm working on a project in which a base linux distribution is built > using yocto while a set of proprietary components is built with the > generated SDK (-c populate_sdk). > > These components use cmake for building. While

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 03:41 PM, Andrea Galbusera wrote: Yes, this is coherent with what Alexander's commit message says. We started building stuff in test/ while switching to meson... If we can't easily fix the upstream ourself and/or reproduce outside of OE to ask for help from upstream devels, IMO we

Re: [yocto] Error do_compile libepoxy

On Thu, Jan 18, 2018 at 2:13 PM, Max Krummenacher wrote: > Hi > > 2018-01-18 10:05 GMT+01:00 Alexander Kanavin > : >> >> On 01/18/2018 10:58 AM, Andrea Galbusera wrote: >>> >>> >>> Looks like my first guess was not that bad. Reverting below

Re: [yocto] Error do_compile libepoxy

Hi 2018-01-18 10:05 GMT+01:00 Alexander Kanavin < alexander.kana...@linux.intel.com>: > On 01/18/2018 10:58 AM, Andrea Galbusera wrote: > >> >> Looks like my first guess was not that bad. Reverting below commit, >> which switched to meson build system brought my build back to green. >> Also

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 12:00 PM, Martin Jansa wrote: FWIW: here nativesdk-libepoxy fails in do_configure already since meson conversion FileNotFoundError: [Errno 2] No such file or directory:

[linux-yocto] [PATCH 4.12] drm/tilcdc: Precalculate total frametime in tilcdc_crtc_set_mode()

From: Jyri Sarha commit ce99f7206c9105851d97202ed08c058af6f11ac4 upstream We need the total frame refresh time to check if we are too close to vertical sync when updating the two framebuffer DMA registers and risk a collision. This new method is more accurate that the previous

Re: [yocto] Error do_compile libepoxy

FWIW: here nativesdk-libepoxy fails in do_configure already since meson conversion FileNotFoundError: [Errno 2] No such file or directory: 'TOPDIR/tmp-glibc/work/x86_64-nativesdk-oesdk-linux/nativesdk-libepoxy/1.4.3-r0/build/meson-private/sanitycheckc.exe'

[yocto] [meta-security][PATCH] conf/layer.conf: remove bbclass from BBFILES

Add bbclass to BBFILES doesn't make any sense. Signed-off-by: Robert Yang --- meta-security-compliance/conf/layer.conf | 2 +- meta-tpm/conf/layer.conf | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [yocto] Error do_compile libepoxy

On 01/18/2018 10:58 AM, Andrea Galbusera wrote: Looks like my first guess was not that bad. Reverting below commit, which switched to meson build system brought my build back to green. Also CC-ing the patch author who might suggest further investigations. libepoxy: convert to meson build

Re: [yocto] Error do_compile libepoxy

On 18 January 2018 at 08:58, Andrea Galbusera wrote: > Looks like my first guess was not that bad. Reverting below commit, > which switched to meson build system brought my build back to green. > Also CC-ing the patch author who might suggest further investigations. > So

Re: [yocto] Error do_compile libepoxy

On Wed, Jan 17, 2018 at 1:58 PM, Andrea Galbusera wrote: > Hi! > > On Wed, Jan 17, 2018 at 1:46 PM, Mathias Rudnik > wrote: >> Hello, >> >> I am trying to build libepoxy but the do_compile tasks breaks. >> I found following error messages in the