Re: [OE-core] [PATCH 13/13] weston: Upgrade 1.9.0 -> 1.10.0

On Tue, May 17, 2016 at 12:31 AM, Jussi Kukkonen wrote: > On 16 May 2016 at 18:50, Khem Raj wrote: >>> As I said, I would work on 1.10.91 as it is close of 1.11 and easy the >>> upgrade. But all my patches are based on 1.10 now so it is fine with >>> me as well so please send the v2. >> >> If 1.1

Re: [OE-core] GCC recipe using git?

On Tue, Jul 12, 2016 at 8:40 PM, Gary Thomas wrote: > I see that the gcc-6.x recipe is using git instead of a tarball. > Is there any way to go back to using tar? I ship mirrored sources > to my customers (many are behind corporate firewalls and have limited > network access). The file sizes are

[OE-core] [PATCH 2/2] site: Move rsync_cv_HAVE_C99_VSNPRINTF to common-linux

If we do not cache is then configure in distcc will try to compute it using AC_TRY_RUN which will give some result on x86-64 host when target is x86-64 but it generally is wrong for cross compilation. We therefore cache it for all linux targets. This issue is highlighted by clang when compiling di

[OE-core] [PATCH 1/2] nss: Fix build with clang

Add a patch to disable a clang specific warning and avoid passing clang options to gcc when we have cross compiler is clang but host compiler is gcc We do not need to use target cflags when building native pieces and hence avoid the inter-mixing of compiler options Signed-off-by: Khem Raj --- ..

[OE-core] GCC recipe using git?

I see that the gcc-6.x recipe is using git instead of a tarball. Is there any way to go back to using tar? I ship mirrored sources to my customers (many are behind corporate firewalls and have limited network access). The file sizes are so vastly different and it's quite the burden to have to ca

[OE-core] [PATCH 9/9] linux-yocto/4.1: pinctrl backports

Integrating the following mainline commits: pinctrl: make pinctrl_register() return proper error code pinctrl: Remove .owner field pinctrl: mediatek: add pinctrl/GPIO/EINT driver for mt8127 pinctrl: mediatek: Add Pinctrl/GPIO driver for mt6397. pinctrl: add imx7d support pinctrl: sirf:

[OE-core] [PATCH 3/9] linux-yocto/4.4: cpumask: Export cpumask_any_but()

Backporting a mainline commit to Intel uncore can be completely modular. Signed-off-by: Nilesh Bacchewar Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +- meta/recipes-kernel/linux/linux-yocto_4.4.bb | 16 2 files changed, 9 inser

[OE-core] [PATCH 4/9] linux-yocto/config: mei, gpio and usb type c

Merging the following configuration changes into the 4.1 and 4.4 linux-yocto kernel meta data: mei.cfg: mei driver is no longer in staging bsp/intel-common: add keyboard-gpio to intel-common-drivers features/thermal: Enable Intel PMIC thermal feature broxton: Enable USB Type C feature for

[OE-core] [PATCH 8/9] linux-yocto: powerclamp and gpio configuration changes

Integrating the following commits to tweak the default configuration for powerclamp and gpio: features/thermal: make INTEL_POWERCLAMP driver built as module gpio: disable Intel PMIC gpio Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +- meta/recip

[OE-core] [PATCH 6/9] linux-yocto/4.4: update to v4.4.14

Updating the korg -stable release. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 6 +++--- meta/recipes-kernel/linux/linux-yocto_4.4.bb | 20 ++-- 3 files changed, 15 insert

[OE-core] [PATCH 2/9] linux-yocto/4.1/4.1: mei, usb and extcon changes

Backporting the following mainline changes to the 4.1 and 4.4 kernels: device property: Avoid potential dereferences of invalid pointers device property: convert to use match_string() helper lib/string: introduce match_string() helper device property: fix for a case of use-after-free dev

[OE-core] [PATCH 5/9] linux-yocto/4.1: update to 4.1.27

Integrating the korg -stable release. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++--- meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++--- meta/recipes-kernel/linux/linux-yocto_4.1.bb | 20 ++-- 3 files changed, 16 i

[OE-core] [PATCH 7/9] linux-yocto/4.4: pwm and mei updates

Backporting upstream mei changes, and two pwm changes from Mika Westerberg's pwm-4.4 branch: pwm: lpss: Prevent on_time_div overflow on lower frequencies pwm: lpss: fix base_unit calculation for PWM frequency mei: don't use wake_up_interruptible for wr_ctrl mei: fix waiting for wr_ctrl for

[OE-core] [PATCH 0/9] linux-yocto: consolidated pull request

Hi all, I hand't heard if there were any issues with these in any test branches, but to be safe, I'm batching up all my pending commits and sending them as a consolidated series. These commits represent mainline backports (largely for intel platform support), -stable integrations asn well as some

[OE-core] [PATCH 1/9] linux-yocto/4.1/4.4: x86, power and usb-c mainline backports

Updating the 4.1 and 4.4 kernels with mainlin backports for platform/feature support. Also updating the kernel meta data to configure and use those new features. Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 4 ++-- meta/recipes-kernel/linux/linux-yocto-

Re: [OE-core] musl 1.1.15 for krogoth?

On Tue, Jul 12, 2016 at 4:34 PM, akuster808 wrote: > > Khem, > > would updating Krogoth musl to 1.1.15 be safe? It would be, since there are no ABI breaking changes between 1.1.14 and 1.1.15 incremental fixes and new architectures primarily. > > I already pulled in the other musl tip updates. O

[OE-core] musl 1.1.15 for krogoth?

Khem, would updating Krogoth musl to 1.1.15 be safe? I already pulled in the other musl tip updates. regards, Armin -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembe

Re: [OE-core] [PATCH] report-error: replace build paths with markers not whitespace

On Tue, Jul 12, 2016 at 2:42 AM, Ross Burton wrote: > To remove potentially personal information and reduce irrelevant noise when > searching for similar reports the error reporting class removes ${TOPDIR} from > the logs. Whilst this is valid intention, the replacement of ' ' results in > potent

Re: [OE-core] Future of GCC

On Tue, Jul 12, 2016 at 3:27 PM, Richard Purdie wrote: > On Tue, 2016-07-12 at 14:34 -0700, akuster808 wrote: >> >> On 07/12/2016 02:24 PM, Burton, Ross wrote: >> > On 12 July 2016 at 22:14, akuster808 wrote: >> > >> > > > Personally I was thinking that gcc 5.x and 6.x should stay in >> > > > oe-

Re: [OE-core] [PATCH V4] rootfs.py: allow removal of support packages

On 07/12, Stephano Cetola wrote: > Changes from V3: > Split off of whitespace rather than comma. > > Stephano Cetola (1): > rootfs.py: allow removal of support packages > > meta/lib/oe/rootfs.py | 20 ++-- > 1 file changed, 18 insertions(+), 2 deletions(-) > > -- > 2.9.0 > I

[OE-core] [PATCH 1/2] toaster.bbclass: remove directory scan logic for detecting artifacts

From: Elliot Smith toaster.bbclass does a scan of the image deploy and SDK directories when a build finishes. However, this brings no benefit and could be better managed and made easier to modify if moved to toasterui and carried out when the BuildCompleted event occurs. Remove the image scan co

[OE-core] [PATCH 2/2] toaster.bbclass: only scan files-in-image.txt if it exists

From: Elliot Smith We can reach the method in toaster.bbclass which tries to read from the files-in-image.txt file via a build which doesn't create that file (e.g. "bitbake core-image-minimal -c rootfs"). This causes the build to fail with an exception. Check that this file exists before trying

[OE-core] [PATCH 0/2] toaster: Better SDK artifacts and fstypes V2

This is part of a patch set that is split over the openembedded-core and bitbake-devel mailing lists. This is a second version of the patch. These patches remove complexity from the toaster.bbclass in order to move those functions to bitbake/lib/toaster. The overall intent of this set is to impr

Re: [OE-core] Future of GCC

On Tue, 2016-07-12 at 14:34 -0700, akuster808 wrote: > > On 07/12/2016 02:24 PM, Burton, Ross wrote: > > On 12 July 2016 at 22:14, akuster808 wrote: > > > > > > Personally I was thinking that gcc 5.x and 6.x should stay in > > > > oe-core for > > > > this cycle, and then drop 5.x after the relea

Re: [OE-core] [PATCHv3 1/2] cve-check-tool: Add recipe

Mariano, On 07/11/2016 05:52 AM, mariano.lo...@linux.intel.com wrote: > From: Mariano Lopez > > cve-check-tool is a program for public CVEs checking. > This tool also seek to determine if a vulnerability has > been addressed by a patch. By tool do you mean the "cve-check-tool"? All the Nvd DB

[OE-core] [PATCH] initrdscripts/init-install*: Select install target instead of looping through

Its not immediately apparent that more than one install target could be available. With this change we list the available devices up front then prompt the user for which one to use, reducing confusion. Fixes [YOCTO #9919]. Signed-off-by: California Sullivan --- .../initrdscripts/files/init-inst

Re: [OE-core] Future of GCC

On 07/12/2016 02:24 PM, Burton, Ross wrote: > On 12 July 2016 at 22:14, akuster808 wrote: > >>> Personally I was thinking that gcc 5.x and 6.x should stay in oe-core for >>> this cycle, and then drop 5.x after the release. >> >> >> Wouldn't that be dropped iff GCC 7.0 is release? or are you say

[OE-core] [PATCH 3/3] classes/testimage: When image is systemd enable debug log level

In order to get more information about systemd boot process to be able to debug random failures due to high I/O. [YOCTO #9299] Signed-off-by: Aníbal Limón --- meta/classes/testimage.bbclass | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/meta/classes/testimage.bbclass b/

[OE-core] [PATCH 2/3] utils/qemurunner.py: QemuRunner.start() add support for specify extra kernel cmdline

Add ability to specify extra_bootargs (kernel cmdline) in order to enable systemd debug log in images that enables systemd init. [YOCTO #9299] Signed-off-by: Aníbal Limón --- meta/lib/oeqa/targetcontrol.py| 4 ++-- meta/lib/oeqa/utils/qemurunner.py | 8 ++-- 2 files changed, 8 insertio

[OE-core] [PATCH 1/3] linux-yocto: Enable debug/printk.scc KERNEL_FEATURE on qemuall machines.

We are experimenting some issues in the Autobuilder infraestructure possible due to high I/O loads, in order to provide more information about intervals of times in printk enable by default debug/printk.scc on qemu development images. [YOCTO #9299] Signed-off-by: Aníbal Limón --- meta/recipes-k

Re: [OE-core] Future of GCC

On 12 July 2016 at 22:14, akuster808 wrote: > > Personally I was thinking that gcc 5.x and 6.x should stay in oe-core for > > this cycle, and then drop 5.x after the release. > > > Wouldn't that be dropped iff GCC 7.0 is release? or are you saying we > should only have one GCC version? > Well, d

[OE-core] [PATCH 1/1] selftest/seltest.py: Add test to check imports from other layers

From: Mariano Lopez This tests adds a check of selftest itself to verify if can add test from other layers. [YOCTO #9770] Signed-off-by: Mariano Lopez --- meta-selftest/lib/oeqa/selftest/imported.py | 14 ++ meta/lib/oeqa/selftest/seltest.py | 19 +++ 2 f

Re: [OE-core] Future of GCC

On 07/12/2016 01:15 AM, Burton, Ross wrote: > On 12 July 2016 at 08:57, Gary Thomas wrote: > >> Now that GCC 4.x is gone, we're left with (currently) 5.4 & 6.1 >> Is the intention to track these both for a while, or will 5.x >> also be gone once things are working with 6.x? >> >> ... just wonde

[OE-core] [PATCH] useradd-staticids: use map() instead of imap()

In Python3 the itertools module's imap function has been migrated to the globalname space as map(). Calling itertools.imap() will fail because it no longer exists. Signed-off-by: George McCollister --- meta/classes/useradd-staticids.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[OE-core] [PATCH] db: Use cross libtool

Reintroduce the use of cross-libtool when building the target package this fails otherwise with clang | ./libtool --mode=execute true db_printlog | /usr/lib/libstdc++.so: file not recognized: File format not recognized | clang-3.9: error: linker command failed with exit code 1 (use -v to see invo

Re: [OE-core] [PATCH] initramfs-framework: make rootfs module optional

On Tue, Jul 12, 2016 at 10:24 AM, Patrick Ohly wrote: > It still gets installed by default via RRECOMMENDS without having to update > users of the framework (because without it, the framework is incomplete), > but that recommendation can be overridden on a per-image basis. > > Signed-off-by: Patri

[OE-core] [PATCH 2/8] x11-common: replace xtscal with xinput-calibrator

Replace xtscal with xinput-calibrator as part of removing xtscal. [YOCTO #9365] Signed-off-by: Maxin B. John --- meta/recipes-graphics/x11-common/x11-common_0.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/x11-common/x11-common_0.1.bb b/meta/reci

Re: [OE-core] [for-krogoth] musl backport

On 07/11/2016 10:41 AM, Khem Raj wrote: On Mon, Jul 11, 2016 at 10:39 AM, Otavio Salvador wrote: Hello Khem and OE-Core fellows, I would like to propose the backport of following changes: commit a572a1181411668a9bd4c264f5124d13f3d7cead (HEAD -> for-krogoth) Author: Khem Raj Date: Thu Jun

[OE-core] [PATCH 1/8] xtscal: remove recipe

Remove xtscal in preference of xinput-calibrator [YOCTO #9365] Signed-off-by: Maxin B. John --- .../xtscal/xtscal/30xTs_Calibrate.sh | 13 - .../xtscal/xtscal/change-cross.patch | 18 - meta/recipes-graphics/xtscal/xtscal/cleanup.patch | 621 -

[OE-core] [PATCH 3/8] pointercal-xinput: add a dummy calibration file for qemu

In qemu, the emulated PS/2 mouse reports itself as an "absolute coordinate" device and that makes xinput_calibrator think it could be calibrated. Add a dummy calibration file as a work around to prevent xinput_calibrator from popping up on every boot in qemu. [YOCTO #8380] Signed-off-by: Maxin B

[OE-core] [PATCH 4/8] pointercal: remove recipe

Remove pointercal recipe along with xtscal since we replace it with xinput-calibrator [YOCTO #9365] Signed-off-by: Maxin B. John --- meta/recipes-bsp/pointercal/pointercal/COPYING | 2 -- meta/recipes-bsp/pointercal/pointercal/pointercal | 0 .../pointercal/pointercal/qemuarm/pointerca

[OE-core] [PATCH 8/8] distro_alias.inc: remove pointercal and xtscal references

Remove pointercal and xtscal references from distro_alias.inc file since we removed those recipes. Signed-off-by: Maxin B. John --- meta/conf/distro/include/distro_alias.inc | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta/conf/distro/include/distro_alias.inc b/meta/conf/distro/includ

[OE-core] [PATCH 7/8] layer.conf: remove pointercal

Since we removed the pointercal recipe, remove it from layer.conf Signed-off-by: Maxin B. John --- meta/conf/layer.conf | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf index 81dd4be..b922234 100644 --- a/meta/conf/layer.conf +++ b/meta/conf/layer.co

[OE-core] [PATCH 6/8] packagegroup-core-x11-base.bb: replace pointercal with pointercal-xinput

Replace pointercal with pointercal-xinput since we removed pointercal recipe. Signed-off-by: Maxin B. John --- meta/recipes-graphics/packagegroups/packagegroup-core-x11-base.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/packagegroups/packagegroup-co

[OE-core] [PATCH 5/8] tslib: replace pointercal with pointercal-xinput

tslib RRECOMMENDS pointercal. Replace it with pointercal-xinput since we removed pointercal recipe. Signed-off-by: Maxin B. John --- meta/recipes-graphics/tslib/tslib_1.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/tslib/tslib_1.1.bb b/meta/recip

[OE-core] [PATCH 0/8] replace xtscal with xinput-calibrator

Remove xtscal in preference of xinput-calibrator [YOCTO #9365] Maxin B. John (8): xtscal: remove recipe x11-common: replace xtscal with xinput-calibrator pointercal-xinput: add a dummy calibration file for qemu pointercal: remove recipe tslib: replace pointercal with pointercal-xinput

Re: [OE-core] [PATCH 1/2] meta-ostro-fixes: initramfs-framework: add retry loop for slow boot devices (like USB)

On Mon, 2016-07-11 at 12:17 -0300, Otavio Salvador wrote: > On Mon, Jul 11, 2016 at 12:10 PM, Patrick Ohly wrote: > > On Mon, 2016-07-11 at 11:35 -0300, Otavio Salvador wrote: > >> Hello Ross, > >> > >> On Fri, Jul 1, 2016 at 2:50 PM, Otavio Salvador > >> wrote: > >> > Agreed but please split th

[OE-core] [PATCH] initramfs-framework: make rootfs module optional

It still gets installed by default via RRECOMMENDS without having to update users of the framework (because without it, the framework is incomplete), but that recommendation can be overridden on a per-image basis. Signed-off-by: Patrick Ohly --- .../recipes-core/initrdscripts/initramfs-framework

[OE-core] [PATCH V4] rootfs.py: allow removal of support packages

Changes from V3: Split off of whitespace rather than comma. Stephano Cetola (1): rootfs.py: allow removal of support packages meta/lib/oe/rootfs.py | 20 ++-- 1 file changed, 18 insertions(+), 2 deletions(-) -- 2.9.0 -- ___ Openem

[OE-core] [PATCH V4] rootfs.py: allow removal of support packages

For images not containing a package manager, this allows the removal of support packages based on the REMOVE_PKG_SUPPORT variable. Packages that will be uninstalled include: update-rc.d, base-passwd, shadow, run-postinsts, and update-alternatives. [ YOCTO #9491 ] Signed-off-by: Stephano Cetola -

Re: [OE-core] [PATCH 3/7] git: 2.8.4 -> 2.9.0

On 07/12/2016 05:11 AM, Burton, Ross wrote: On 7 July 2016 at 14:14, Dan McGregor mailto:danismostlik...@gmail.com>> wrote: I have no real objection to this.. in fact I've done it locally. But I do think we should wait for 2.9.1. It should be released soon hopefully. 2.9.1 was just r

[OE-core] [PATCH 2/2] testimage.bbclass: INHERIT -> IMAGE_CLASSES

Use IMAGE_CLASSES which is only seen by image recipe. Signed-off-by: Robert Yang --- meta/classes/testimage.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/testimage.bbclass b/meta/classes/testimage.bbclass index 7fd0f62..6d8cc6e 100644 --- a/meta/classes

[OE-core] [PATCH 1/2] oe-selftest: print errors when failed to find test

For example: $ oe-selftest --run-tests-by name hello world 2016-07-12 00:33:28,678 - selftest - ERROR - Failed to find test: hello 2016-07-12 00:33:28,679 - selftest - ERROR - Failed to find test: world Signed-off-by: Robert Yang --- scripts/oe-selftest | 12 ++-- 1 file changed, 10 inse

[OE-core] [PATCH 0/2] fix oe-selftest and testimage.bbclass

The following changes since commit b17f91ed06a604e3d356fe17756bfe2ca61594b7: tune-ppce500mc.inc: pass -mcpu=e500mc for ppce500mc kernel compile (2016-07-10 14:12:07 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/test http://cgit.op

Re: [OE-core] [PATCH 2/7] e2fsprogs: 1.43 -> 1.43.1

On 07/07/2016 05:53 PM, Burton, Ross wrote: On 7 July 2016 at 08:54, Andre McCurdy mailto:armccu...@gmail.com>> wrote: Based on the e2fsprogs release notes, v1.43.1 adds a new configure option, --enable-hardening http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.43.1

[OE-core] [PATCH] wic: mountpoint is an optional argument

According to wic documentation partition mount point is an optional argument. Skipping mount point also makes sense in certain configurations when one needs to specify a partition that is not mounted by the running system, such as a recovery or a mirror partition (in dual rootfs setups). Signed-of

Re: [OE-core] [for-krogoth] Backport of new libarchive release

On Mon, Jul 11, 2016 at 10:25 PM, akuster808 wrote: > On 07/11/2016 07:41 AM, Otavio Salvador wrote: >> The libarchive 3.2.1 fixes several bugs and security related issues so >> it seems like a good candidate for backport. I list below the commits >> I did in our local fork while testing it: > > C

[OE-core] [PATCHv2 5/5] piglit: Upgrade version, use python3

* Remove backported patch * Update dependencies to use python3 modules, add depencies added in the new version * install only stripped binaries to keep size down Signed-off-by: Jussi Kukkonen --- ...0001-tests-Fix-missing-include-of-Xutil.h.patch | 28 -- meta/recipes-graph

[OE-core] [PATCHv2 2/5] python3: Add compression to python3-shell dependencies

python3-shell needs python3-compression for tarfile. Signed-off-by: Jussi Kukkonen --- meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +- scripts/contrib/python/generate-manifest-3.5.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/py

[OE-core] [PATCHv2 0/5] Upgrade piglit

Changes since v1: * Sacrifice piglit debug binaries for build speed * Add a missing signed-off-by * Do not install .egg for python-six The python-six .egg install was added to avoid a build problem in python-cryptography (6b4cee975 in meta-oe). I cannot reproduce the problem: python-cryptography bu

[OE-core] [PATCHv2 3/5] python3: Add dependencies for python3-misc

http.server requires email.parser. argparse requires codecs and textutils. Signed-off-by: Jussi Kukkonen --- meta/recipes-devtools/python/python3_3.5.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/python/python3_3.5.1.bb b/meta/recipes-devtools/py

[OE-core] [PATCHv2 4/5] python3-native: Add "io" to rprovides

Signed-off-by: Jussi Kukkonen --- meta/recipes-devtools/python/python3-native_3.5.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/python/python3-native_3.5.1.bb b/meta/recipes-devtools/python/python3-native_3.5.1.bb index fbe04c6..81ea087 100644 ---

[OE-core] [PATCHv2 1/5] python-six: Add to oe-core

Recipes are moved from meta-openembedded/meta-python Changes compared to meta-python version: * Modified to not inherit pypi * Fix python-io dependency for python3 * Support native, nativesdk * Do not install .egg Signed-off-by: Jussi Kukkonen --- meta/recipes-devtools/python/python-six.inc

Re: [OE-core] [PATCH] grub-efi: run autogen.sh before configure

Hello On Tue, 12 Jul 2016 11:27:15 +0800 "Yu, Mingli" wrote: > On 2016年07月11日 18:22, Burton, Ross wrote: > > > > On 6 May 2016 at 13:13, Catalin Enache > > wrote: > > > > DEPENDS_class-target = "grub-efi-native" > > RDEPENDS_${PN}_class-target =

Re: [OE-core] [PATCH 1/5] python-six: Add to oe-core

On 07/12/2016 01:38 PM, Jussi Kukkonen wrote: Interestingly python-cryptography does not have six in "setup_requires" so I still don't understand why it would do this. I'll do a few tests on that before sending the updated patch set. Maybe it simply used to have that in the past, and no longer

Re: [OE-core] [PATCH 1/5] python-six: Add to oe-core

On 11 July 2016 at 17:27, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 07/11/2016 02:46 PM, Jussi Kukkonen wrote: > > Not sure where a URL like that comes from or why it would be accessed >> during build? Li Xin, any comment? >> > > A few recipes in meta-oe have this issue, f

Re: [OE-core] [PATCH] weston-init: De-couple framebuffer console from Weston

On Mon, Jul 11, 2016 at 7:06 PM, Tom Hochstein wrote: > The framebuffer console was using the same I/O as Weston. We fix this > by having openvt switch to the new VT when starting weston-launch. > > Signed-off-by: Tom Hochstein Acked-by: Otavio Salvador -- Otavio Salvador

[OE-core] [PATCH] report-error: replace build paths with markers not whitespace

To remove potentially personal information and reduce irrelevant noise when searching for similar reports the error reporting class removes ${TOPDIR} from the logs. Whilst this is valid intention, the replacement of ' ' results in potentially confusing logs as it appears that builds are happening

Re: [OE-core] Future of GCC

On 12 July 2016 at 08:57, Gary Thomas wrote: > Now that GCC 4.x is gone, we're left with (currently) 5.4 & 6.1 > Is the intention to track these both for a while, or will 5.x > also be gone once things are working with 6.x? > > ... just wondering where to spend my effort since I'll have to > make

[OE-core] Future of GCC

Now that GCC 4.x is gone, we're left with (currently) 5.4 & 6.1 Is the intention to track these both for a while, or will 5.x also be gone once things are working with 6.x? ... just wondering where to spend my effort since I'll have to make my targets (some are very old) work with at least 5.x A

Re: [OE-core] [PATCH] glibc: add more Imagination Meta relocation to elf.h

On 12 July 2016 at 02:24, Khem Raj wrote: > 1. Move them after BPF declarations. > Sure. > 2. Write a ChangeLog entry, something like > . Really?! :) Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists