[OE-core] [PATCH] libsolv: split libsolvext into it's own pkg-config

Opkg only depends on libsolv proper, splitting libsolv-ext pkg-config reduces opkg dependencies. Signed-off-by: Alejandro del Castillo --- ...-libsolvext-into-it-s-own-pkg-config-file.patch | 67 ++

[OE-core] [PATCH 1/2] bitbake.conf: replace USE_LDCONFIG with new "ldconfig" distro feature

USE_LDCONFIG could previously be set to 0 by distros which do not require ldconfig or ld.so.conf on the target. Since more and more recipes may need to respect that option, replace the ad-hoc variable with a distro feature. Distros which previously set: USE_LDCONFIG = "0" Should now instead

[OE-core] [PATCH 2/2] systemd: check "ldconfig" distro feature when setting PACKAGECONFIG

Avoid trying to call ldconfig at run-time in distros which don't provide ldconfig on the target. Signed-off-by: Andre McCurdy --- meta/recipes-core/systemd/systemd_232.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 0/2] replace USE_LDCONFIG with ldconfig distro feature

Andre McCurdy (2): bitbake.conf: replace USE_LDCONFIG with new "ldconfig" distro feature systemd: check "ldconfig" distro feature when setting PACKAGECONFIG meta/classes/package.bbclass | 5 + meta/conf/bitbake.conf| 2 +-

[OE-core] ✗ patchtest: failure for Fix for #10835 - WIC should not rely on hddimg creation for finding all needed artifacts (rev3)

== Series Details == Series: Fix for #10835 - WIC should not rely on hddimg creation for finding all needed artifacts (rev3) Revision: 3 URL : https://patchwork.openembedded.org/series/4802/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This

[OE-core] [PATCH v3 08/11] selftest: wic: fix test_iso_image test case

Added "iso" to IMAGE_FSTYPES to build iso artifacts required to fix test of isoimage-isohybrid wic plugin. Signed-off-by: Ed Bartosh --- meta/lib/oeqa/selftest/wic.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/wic.py

[OE-core] [PATCH v3 07/11] selftest: stop using hddimg in the wic test suite

Removed hddimg from IMAGE_FEATURES as wic code doesn't use hddimg anymore. [YOCTO #10835] Signed-off-by: Ed Bartosh --- meta/lib/oeqa/selftest/wic.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/lib/oeqa/selftest/wic.py

[OE-core] [PATCH v3 05/11] wic: Look for image artifacts in a common location

From: Tom Zanussi Rather than have each image type look for artifacts in image-specific locations, move towards having them look for artifacts in a common location, in this case DEPLOY_DIR_IMAGE Use the existing deploy.bbclass to have the bootloaders put their

[OE-core] [PATCH v3 09/11] grub-efi.bbclass: use 'grub-efi-' prefix

grub-efi recipe added 'grub-efi-' prefix to the file name of efi binary. Changed grub-efi.bbclass accordingly. Signed-off-by: Ed Bartosh --- meta/classes/grub-efi.bbclass | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git

[OE-core] [PATCH v3 06/11] isoimage-isohybrid: use TRANSLATED_TARGET_ARCH instead of MACHINE_ARCH

isoimage-sihybrid plugin uses MACHINE_ARCH to get the name of initrd image. It doesn't work for all machines, for example for quemux86-64 machine MACHINE_ARCH is quemux86_64 and initrd name is core-image-minimal-initramfs-qemux86-64.cpio.gz Used TRANSLATED_TARGET_ARCH variable to get the initrd

[OE-core] [PATCH v3 10/11] wic-tools: add dependency to systemd-boot

Added systemd-boot to the list of dependencies of wic-tools as wic bootimg-efi plugin depends on it. Signed-off-by: Ed Bartosh --- meta/recipes-core/meta/wic-tools.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH v3 03/11] wic: isoimage-isohybrid: stop using HDDDIR

Stop using HDDDIR in isoimage-isohybrid wic plugin. This variable is set by hddimg code, which is going to be removed soon. All required artifacts should be available from ISODIR. wic-image.bbclass has been modified to build iso artifacts, so it should be safe to remove usage of HDDDIR. [YOCTO

[OE-core] [PATCH v3 11/11] isoimage-isohybrid: renamed variable hdd_dir

Renamed variable hdd_dir to deploy_dir as this variable is assigned to the value of DEPLOY_DIR_IMAGE. Signed-off-by: Ed Bartosh --- scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[OE-core] [PATCH v3 02/11] wic: use INITRD_LIVE in isoimage-isohybrid

INITRD variable is not set if hddimg is disabled. isoimage-isohybrid can't get correct name for initrd if INITRD variable is not set. Added INITRD_LIVE to WICVARS and used it in isoimage-isohybrid code to get initrd artifact name. Used INITRD if INITRD_LIVE is not set. Signed-off-by: Ed Bartosh

[OE-core] [PATCH v3 04/11] image-wic: remove HDDDIR from WICVARS

Removed HDDDIR as it's not used by wic anymore. Stopped usage of HDDDIR in wic test suite. Signed-off-by: Ed Bartosh --- meta/classes/image-wic.bbclass | 2 +- meta/lib/oeqa/selftest/wic.py | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH v3 01/11] image-wic: move wic code to image-wic.bbclass

There is a lot of wic code in image.bbclass and image_types.bbclass Having all code separated in one file should make it more readable and easier to maintain. Signed-off-by: Ed Bartosh --- meta/classes/image-wic.bbclass | 120 +++

[OE-core] [PATCH v3 00/11] Fix for #10835 - WIC should not rely on hddimg creation for finding all needed artifacts

Hi, This patchset usage of hddimg from wic codebase due to planned deprecation of hddimg. While working on this wic-related code in meta/classes/ has been moved to image-wic.bbclass to make it more maintainable. Changes in v2: rebased on top of ross/mut Changes in v3: removed patches that add

[OE-core] virtual/ -vs- virtual-

Is the rule about using "virtual/foo" for PROVIDES and "virtual-foo" for RPROVIDES documented somewhere? -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] ✗ patchtest: failure for Fix bugs found within runtime testing (rev2)

== Series Details == Series: Fix bugs found within runtime testing (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/4986/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCHv2 3/5] testimage.bbclass: Allow to run tests on autobuilder's images

From: Mariano Lopez With the change to the new framework data store dependecy was removed, instead a new file is generated and used in testimage. When testing builds from the autobuilders the test data values are from the autobuilder, including the paths. Some

[OE-core] [PATCHv2 5/5] oeqa/runtime/cases: Rename syslog module to oe_syslog

From: Aníbal Limón Debian based distros has a builtin syslog module so when try to load tests using unittest it references the builtin module instead of runtime/cases. [YOCTO ##10964] Signed-off-by: Aníbal Limón Signed-off-by:

[OE-core] [PATCHv2 1/5] runtime/cases: Fix case numbers, missing cases and unused classes

From: Mariano Lopez connman: oeRuntimeTest class is not used anymore as part of runtime migration, this particular case was missed, so fix it. gcc: Removed unneded lines. multilib: fixed case number. syslog: added a missing test. [YOCTO #10964] Signed-off-by:

[OE-core] [PATCHv2 4/5] oeqa/core/context.py: Add validation for run-tests option

From: Aníbal Limón The run-tests option is optional so if isn't specified set to None instead of crash on split(). Signed-off-by: Aníbal Limón --- meta/lib/oeqa/core/context.py | 6 +- 1 file changed, 5 insertions(+), 1

[OE-core] [PATCHv2 0/5] Fix bugs found within runtime testing

From: Mariano Lopez This will fix some bugs found in testimage when executing tests from images downloaded from the autobuilders. Changes in v2: - Fix some test cases that were changed during the migration. - Add createrepo-native as dependency of test image. -

[OE-core] [PATCHv2 2/5] runtime/cases/smart.py: Check for IMAGE_PKGTYPE instead of PACKAGE_CLASSES

From: Mariano Lopez smart test requires to build the image using rpm packages, this check was included, but it checked for PACKAGE_CLASSES=='package_rpm', and this is not true when building packages for rpm and deb/ipk. So this would check IMAGE_PKGTYPE instead.

Re: [OE-core] [PATCH v5 09/12] runqemu: also accept -image suffix for rootfs parameter

On Fri, 2017-01-27 at 16:54 +, Bystricky, Juro wrote: > Just curious: is this test for "image" in file name really necessary? > With qemuboot.conf the relevant files are already spelled out. > I don't see a need to force "compulsory" names for images. > If I comment out this test, everything

Re: [OE-core] why do (some) apache module recipes depend on both apache2 and apache2-native?

On 1/27/17 7:17 AM, Robert P. J. Day wrote: > > i was poking around some apache module recipes, eg, > apache-websocket_git.bb, and noticed: > > DEPENDS = "apache2 apache2-native" > RDEPENDS_${PN} += "apache2" > > i can certainly understand that run-time dependency, but why would an >

Re: [OE-core] what is the working directory for configure/compile/install tasks?

On 1/27/17 4:44 AM, Robert P. J. Day wrote: > i'm aware that most tasks are defined in terms of commands that > explicitly use directory references with "S", "B", "D", WORKDIR, and > so on and so on. but if i want to define a do_configure() task that > does nothing more than invokes the

[OE-core] [PATCH 3/7] gzip/pigz/expat/image: Simplify gzip-native/pigz-native

With recipe specific sysroots, the gzip-replacement-native dance/class is obsolete, simplify the code accordingly. Signed-off-by: Richard Purdie --- meta/classes/gzipnative.bbclass | 5 - meta/classes/image.bbclass | 2 --

[OE-core] [PATCH 4/7] sstate: Allow sstate_clean_manifest to take a prefix

Manifest files containing the same duplicated prefix are wasteful on space and ultimately this costs build time. Add support for manifest files with common prefixes removed and use the prefix if the path isn't absolute. Signed-off-by: Richard Purdie ---

[OE-core] [PATCH 5/7] staging: Drop common prefix WORKDIR from manifest files

Manifest files containing the same duplicated prefix are wasteful on space and ultimately this costs build time. Drop the WORKDIR prefix from the manifest files since this small change mounts up a lot. Signed-off-by: Richard Purdie ---

[OE-core] [PATCH 6/7] staging: Allow removal of stale sysroot objects

The main sysroot components of unreachable build targets will be removed by the core code. This currently doesn't trigger a removal in the individual workdirs. This adds in symlinking between the complete stamps and the component sysroot meaning we can detect when someting was removed and hence

[OE-core] [PATCH 2/7] allarch: Drop STAGING_DIR_HOST expansion

Now that STAGINGDIR_HOST doesn't contain MACHINE, we no longer need to expand the value. Pre-expansion can mean components like PV can be expanded too early and cause problems for certain use cases. Signed-off-by: Richard Purdie ---

[OE-core] [PATCH 7/7] libxml2: Drop docs in native case

With rss, moving these around was having an increasing overhead and we don't need them in the native case so remove them. Signed-off-by: Richard Purdie --- meta/recipes-core/libxml/libxml2_2.9.4.bb | 5 + 1 file changed, 5 insertions(+) diff --git

[OE-core] [PATCH 1/7] image/kernelsrc/packagegroups/recipes: Remove uneeded noexec tasks

We used to have issues removing tasks like do_fetch due to implications for targets like world and universe. These have now been resolved. Removing uneeded tasks has advantages compared to noexec since it means that accidentally left in dependencies are no longer needed/processed (e.g. do_patch

Re: [OE-core] [PATCH v5 09/12] runqemu: also accept -image suffix for rootfs parameter

Just curious: is this test for "image" in file name really necessary? With qemuboot.conf the relevant files are already spelled out. I don't see a need to force "compulsory" names for images. If I comment out this test, everything works just fine. Am I missing something? Juro

[OE-core] ✗ patchtest: failure for UEFI + Secure Boot + qemu (rev6)

== Series Details == Series: UEFI + Secure Boot + qemu (rev6) Revision: 6 URL : https://patchwork.openembedded.org/series/4506/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

Re: [OE-core] [PATCH v4 05/12] ovmf: deploy firmware in image directory

On Thu, 2017-01-26 at 19:25 -0800, Ricardo Neri wrote: > On Mon, 2017-01-23 at 08:45 +0100, Patrick Ohly wrote: > > > On the other hand, this is a new recipe and this may not be super > > > critical. Especially if you meant that only OVMF will not support > > > installing bios.bin in sysroot.

[OE-core] [PATCH v5 12/12] ovmf: remove BGRT patch

This patch was added to meta-luv for kernel testing purposes and probably is not relevant for OE-core. Signed-off-by: Patrick Ohly --- meta/recipes-core/ovmf/ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch | 110

[OE-core] [PATCH v5 11/12] ovmf: build image which enrolls standard keys

When booting a qemu virtual machine with ovmf.secboot, it comes up with no keys installed and thus Secure Boot disabled. To lock down the machine like a typical PC, one has to enroll the same keys that PC vendors normally install, i.e. the ones from Microsoft. This can be done manually (see

[OE-core] [PATCH v5 10/12] runqemu: support UEFI with OVMF firmware

In the simplest case, "runqemu qemux86 qcow2 ovmf" for an EFI-enabled image in the qcow2 format will locate the ovmf.qcow2 firmware file deployed by the ovmf recipe in the image deploy directory, override the graphics hardware with "-vga std" because that is all that OVMF supports, and boot with

[OE-core] [PATCH v5 09/12] runqemu: also accept -image suffix for rootfs parameter

The magic detection of the rootfs parameter only worked for image recipes which embedd the "image" string in the middle, as in "core-image-minimal". Sometimes it is more natural to call an image "something-image". To get such an image detected by runqemu, "-image" at the end of a parameter must

[OE-core] [PATCH v5 07/12] ovmf_git.bb: enable Secure Boot

When enabled via PACCKAGECONFIG = "secureboot" (off by default because of the extra work and license change), the recipe compiles OVMF twice, once without Secure Boot, once with. This is the same approach as in https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec The results are

[OE-core] [PATCH v5 05/12] ovmf: deploy firmware in image directory

When used with '-drive if=pflash', qemu will store UEFI variables inside the firmware image file. That is unexpected for a file located in the sysroot, which should be read-only, while it is normal for image files in the deploy/images directory. Therefore that directory is a better place for use

[OE-core] [PATCH v5 08/12] runqemu: fix undefined variable reference in check_arg_path()

'arg' isn't defined, the right name there is 'p'. This fixes a rather obscure error message when that code path ends up being taken: $ runqemu some/existing-file-name runqemu - ERROR - name 'arg' is not defined runqemu - ERROR - Try 'runqemu help' on how to use it Signed-off-by: Patrick Ohly

[OE-core] [PATCH v5 06/12] ovmf_git.bb: enable parallel compilation

The Fedora srpm [1] seems to have no problems with parallel compilation, so let's also use that for the target. The native tools however indeed have dependency problems: | test_Ecc_CParser (CheckPythonSyntax.Tests) ... gcc -o ../bin/EfiRom

[OE-core] [PATCH v5 03/12] ovmf: move from meta-luv to OE-core

From: meta-luv This is an unmodified copy of github.com/01org/luv-yocto/meta-luv/recipes-core/ovmf revision 4be4329. Signed-off-by: Patrick Ohly --- meta/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch | 48

[OE-core] [PATCH v5 04/12] ovmf: explicitly depend on nasm-native

Fixes a build issue when nasm was not build already because of something else. Signed-off-by: Patrick Ohly --- meta/recipes-core/ovmf/ovmf_git.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/ovmf/ovmf_git.bb

[OE-core] [PATCH v5 02/12] acpica: work around flex 2.6.2 code generation issue

Without this patch, linking fails with a missing implementation of yy_scan_string. This looks like a regression in flex, because 2.6.0 generated different code that called PrParser_scan_string resp. DtParser_scan_string. Working around that in acpica until this is better understood or fixed in

[OE-core] [PATCH v5 00/12] UEFI + Secure Boot + qemu

There seems to be a consensus that supporting UEFI in OE-core for qemu would be valuable, and there have been some (stalled) attempts to add it. For reference, see: [OE-core] [PATCH V3 0/3] Add UEFI firmware for qemux86* [OE-core] Add ovmf-native to make qemu-native/runqemu support boot UEFI

[OE-core] [PATCH v5 01/12] acpica: move from meta-oe to OE-core

From: Fathi Boudra qemu support for UEFI in OE-core depends on OVMF, which needs the iasl tools provided by this recipe. There's also an iasl recipe in meta-luv, but than can and will be replaced by this one, thus reducing overall maintenance work. Copied from

[OE-core] why do (some) apache module recipes depend on both apache2 and apache2-native?

i was poking around some apache module recipes, eg, apache-websocket_git.bb, and noticed: DEPENDS = "apache2 apache2-native" RDEPENDS_${PN} += "apache2" i can certainly understand that run-time dependency, but why would an apache module recipe have a build-time dependency on both the

[OE-core] [PATCH] oeqa/buildperf: don't archive stdout/stderr of commands

Stop capturing output of the shell commands into /commands.log. Redirecting output into a file prevented the unittest framework from capturing it, causing useless errors (with empty output) like: oeqa.utils.CommandError: Command '['bitbake', 'core-image-sato']' returned non-zero exit status 1 with

Re: [OE-core] what is the working directory for configure/compile/install tasks?

On Fri, 27 Jan 2017, Burton, Ross wrote: > > On 27 January 2017 at 12:44, Robert P. J. Day wrote: >   i've been handed a simple example of Makefile-based source to turn > into a recipe, and the configure/build process is absolutely > straightforward --

[OE-core] [PATCH] build-perf-test-wrapper.sh: fix issues with non-existing path arguments

Without the '-s' option realpath will error out if the given path does not exist. Signed-off-by: Markus Lehtonen --- scripts/contrib/build-perf-test-wrapper.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [OE-core] what is the working directory for configure/compile/install tasks?

On 27 January 2017 at 12:44, Robert P. J. Day wrote: > i've been handed a simple example of Makefile-based source to turn > into a recipe, and the configure/build process is absolutely > straightforward -- top-level "configure" and "Makefile" files to be > run -- to the

Re: [OE-core] what is the working directory for configure/compile/install tasks?

On 01/27/2017 02:44 PM, Robert P. J. Day wrote: i've been handed a simple example of Makefile-based source to turn into a recipe, and the configure/build process is absolutely straightforward -- top-level "configure" and "Makefile" files to be run -- to the point where i can simply define

[OE-core] what is the working directory for configure/compile/install tasks?

this is such a simple question, i'm kind of embarrassed to be asking it. i've been handed a simple example of Makefile-based source to turn into a recipe, and the configure/build process is absolutely straightforward -- top-level "configure" and "Makefile" files to be run -- to the point

Re: [OE-core] sysroots, wic-tools and rm_work

On 27/01/17 13:05, Patrick Ohly wrote: > On Thu, 2017-01-26 at 16:39 +0100, Kristian Amlie wrote: >> It seems like wic doesn't work together with rm_work, because of its >> dependency on wic-tools. The reason is that building wic-tools will >> result in rm_work removing the very sysroot that wic

Re: [OE-core] sysroots, wic-tools and rm_work

On Thu, 2017-01-26 at 16:39 +0100, Kristian Amlie wrote: > It seems like wic doesn't work together with rm_work, because of its > dependency on wic-tools. The reason is that building wic-tools will > result in rm_work removing the very sysroot that wic needs. > > It's easy to fix locally by

[OE-core] [PATCH][morty] libXrandr: fix for CVE-2016-7947 and CVE-2016-7948

CVE-2016-7947 Insufficient validation of server responses result in Integer overflows CVE-2016-7948 Insufficient validation of server responses result in various data mishandlings References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-7947

[OE-core] ✗ patchtest: failure for python3: support profile-optimized build

== Series Details == Series: python3: support profile-optimized build Revision: 1 URL : https://patchwork.openembedded.org/series/5027/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH RFC 10/10] python-pgo-image: change python3 profile target to pybench

Running test.regrtest was still taking ridiculously long, i.e. around 4 hours in qemux86 on my desktop machine. Change to pybench which "only" takes around 55 minutes. [YOCTO #9338] Signed-off-by: Markus Lehtonen ---

[OE-core] [PATCH RFC 00/10] python3: support profile-optimized build

This patchset implements profile-guided-optimization (PGO) for Python 3. The implementation is very similar to my previous patchset for Python 2.7. PGO for python3-native is one simple patch. PGO for target python3 is more complicated and follows the lines of Python 2.7: 1. add new

[OE-core] [PATCH RFC 08/10] python-pgo-image: exclude tests from the python3 profile target

Exlude failing tests (on qemux86 target) which would cause the profile task to fail. Also, disable some very long running tests. Running in qemux86 target on my i7-3770K: test_lib2to3: 1604.5s test_buffer: 1562.8s test_pickle: 1527.0s test_io: 1517.8s test_threading: 1384.1s

[OE-core] [PATCH RFC 05/10] python3: remove two setup.py cross-compile hacks

Remove two unneeded hacks. The first hack ("setup.py: no host headers libs" patch) is not needed because we use cross-compiler (e.g. i586-oe-linux-gcc) which has not been configured with any host system include or library directories, and thus, we don't get any host system directories when running

[OE-core] [PATCH RFC 07/10] python3: fix profile-optimized build of modules

Without this the pgo-related compiler flags are not used in cross-builds. [YOCTO #9338] Signed-off-by: Markus Lehtonen --- ...-CFLAGS-for-extensions-when-cross-compili.patch | 56 ++ meta/recipes-devtools/python/python3_3.5.2.bb | 1 +

[OE-core] [PATCH RFC 09/10] python3: add python3-tools subpackage

[YOCTO #9338] Signed-off-by: Markus Lehtonen --- meta/recipes-devtools/python/python-3.5-manifest.inc | 8 +--- meta/recipes-devtools/python/python3_3.5.2.bb| 5 + 2 files changed, 10 insertions(+), 3 deletions(-) diff --git

[OE-core] [PATCH RFC 06/10] python3: support profile optimized build

Make it possible to do profile-optimized build. The implementation is virtually identical to how we do it in Python 2.7. Basically, you need to define PYTHON3_PROFILE_OPT = "1" in your local.conf and have profile data available in the location pointed to by PYTHON3_PROFILE_DIR. Profile data can be

[OE-core] [PATCH RFC 02/10] python3: fix depends of python-tests

Similar to an earlier fix for Python 2.7. Make the tests subpackage depend on all modules as test.regrtest uses most (if not all) of them. Some tests also depend on libgcc so add that as a runtime dependency as well. [YOCTO #9338] Signed-off-by: Markus Lehtonen

[OE-core] [PATCH RFC 04/10] python-pgo-image: profiling for python3

Add a new 'do_profile3' task for python-pgo-image that runs profiling task for python3 and retrieves the profile data, similarly to 'do_profile' for python2. Profile data will be copied into a directory pointed by PYTHON3_PROFILE_DIR on the host system. The profile task may be specified with

[OE-core] [PATCH RFC 01/10] python3-native: support profile optimized build

This feature is virtually identical to that of python-native. Profile guided optimization is enabled by defining PYTHON3_NATIVE_PROFILE_OPT = "1" in local.conf. In addition, the profile task may be defined with PYTHON3_NATIVE_PROFILE_TASK. [YOCTO #9338] Signed-off-by: Markus Lehtonen

[OE-core] [PATCH RFC 03/10] python3: add python-profile-opt3 recipe

Similar to python-profile-opt for Python 2.7, this is a special version of Python3 used for profile guided optimization. It is used for generating profile data on the target device. Libpython3 is renamed to libpython-profile-opt3 in order to prevent soname clash with "normal" libpython3. [YOCTO

Re: [OE-core] ✗ patchtest: failure for Python3 packaging fixes

Hi, * Patchwork [170127 10:23]: > Series: Python3 packaging fixes > Revision: 1 > URL : https://patchwork.openembedded.org/series/5024/ > State : failure > * Issue Series does not apply on top of target branch > [test_series_merge_on_head]

[OE-core] ✗ patchtest: failure for Python3 packaging fixes

== Series Details == Series: Python3 packaging fixes Revision: 1 URL : https://patchwork.openembedded.org/series/5024/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the

Re: [OE-core] oe-core build fail package_fixsymlinks

Hi Raj, I am new to yocto and systemd. Can you please tell me how to remove meta-linaro-toolchain? On Fri, Jan 27, 2017 at 12:01 PM, Khem Raj wrote: > On Thu, Jan 26, 2017 at 10:29 PM, ANDANI PRASHANT > wrote: > > Hi Raj, > > > > Thank you for

[OE-core] [PATCH 2/7] python3-manifest: move htlm.py to python3-html

This allows us to use html.py without importing misc. Signed-off-by: Anders Darander --- 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

[OE-core] [PATCH 5/7] python-3-manifest: add _compat_pickle to python3-pickle

This allows us to depend on _compat_pickle.* wihtout having to add the whole python3-misc. Signed-off-by: Anders Darander --- meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +- scripts/contrib/python/generate-manifest-3.5.py | 2 +- 2 files changed, 2

[OE-core] [PATCH 3/7] python-3-manifest: add argparse to RDEPENDS for netclient

http/server.py requires argparse. Signed-off-by: Anders Darander --- 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

[OE-core] [PATCH 1/7] python-3-manifest: fix adding imp to importlib

Commit: 512334f102a33833d39af53467894315f0715d07 "python-3.5-manifest: Add imp to importlib" added imp to importlib in the generated manifest, but not in the generator script. Signed-off-by: Anders Darander --- scripts/contrib/python/generate-manifest-3.5.py | 2

[OE-core] [PATCH 7/7] python-3-manifest: split out typing

This allows us to use typing.py without having to add the whole python3-misc package. Signed-off-by: Anders Darander --- meta/recipes-devtools/python/python-3.5-manifest.inc | 10 +++--- scripts/contrib/python/generate-manifest-3.5.py | 3 +++ 2 files changed,

[OE-core] [PATCH 6/7] python-3-manifest: add ipaddress to python3-io

This allows us to use ipaddress without requiring the add the whole python3-misc. Signed-off-by: Anders Darander --- meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +- scripts/contrib/python/generate-manifest-3.5.py | 2 +- 2 files changed, 2 insertions(+),

[OE-core] [PATCH 4/7] python-3-manifest: add socketserver to netserver

socketserver.* should be part of python3-netserver. Signed-off-by: Anders Darander --- 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

[OE-core] [PATCH 0/7] Python3 packaging fixes

This moves a few python modules to more logical places (thus removing the need for python3-misc on more systems). A new package for typing.py is also created. 0001 add imp to importlib in the generator, the earlier commit in oe-core that made this move, only patched the generated manifest. The

Re: [OE-core] [PATCH] busybox: conditional inclusion of login utilities

On jeudi 26 janvier 2017 09:55:17 CET Christopher Larson wrote: > Question, why not use ${PN} here? It was done the same way in the recipe for other fragments so I made it look like the existing declarations. David -- ___ Openembedded-core mailing

Re: [OE-core] [Openembedded-architecture] OpenEmbedded Stand at FOSDEM

On Thu, 26 Jan 2017 22:39:17 +0100 Andreas Müller wrote: > On Thu, Jan 5, 2017 at 4:30 PM, Philip Balister > wrote: > > On 01/03/2017 08:13 PM, Andreas Müller wrote: > >> On Tue, Jan 3, 2017 at 4:32 PM, Philip Balister > >>