[yocto] test cases: Depending on other tests

mycase2.mycaseTest.testB it gives me an error saying that mycase2.mycaseTest.testB is not available even though it clearly is. It is not a typo because no options are available at all in the failures' suggestion. Interestingly open embedded testcases are available as well as the mycase1 tests.

Re: [yocto] nativesdk-gcc tries to link with host

Hello Raj, > target sysroot poisoning is naturally not needed we could do that but it is > not useful, for nativesdk it behaves like a native gcc except that it prefers > the libraries from SDK rootfs, now should be limit it to just the > rootfs and blind > it from system rootfs .. may be I dont

[yocto] nativesdk-gcc tries to link with host

.inc "unpoisons" the sysroot. Basically gcc-target overwrites EXTRA_OECONF_PATHS that was set by gcc-7.3.inc. Let me know if you are aware of what is wrong. Paulo Neves [1] d.c #define _GNU_SOURCE #include #include #include #include #ifdef __STDC__ # i

Re: [yocto] [yocto-docs] documentation: Updated testimage targets.

are accepted. When I produced my changes I did it in the poky git repository, and split the documentation ad-hoc. I will submit the documentation with the fixes you proposed after my other commits are accepted. My apologies for the time wasted. Paulo Neves On Mon, Aug 6, 2018 at 11:12 PM Scott

[yocto] [yocto-docs] documentation: Updated testimage targets.

The documentation of available names for TEST_TARGET have been updated to match the convention of using the class names of controllers. Signed-off-by: Paulo Neves --- documentation/dev-manual/dev-manual-common-tasks.xml | 8 documentation/ref-manual/ref-variables.xml | 19

Re: [yocto] Cannot use any TEST_TARGET besides simpleremote or qemu

td. This way we give all the information that controllers might need to work. As td is retrieved by the json file generated at the image creation time the external test (bitbakeless) functionality should be unaffected. Let me know if you have different opinions. Paulo Neves On Thu, Aug 2, 2018 at

[yocto] Cannot use any TEST_TARGET besides simpleremote or qemu

'boottime' [2] https://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#var-TEST_TARGET Paulo Neves -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fwd: Basehash value changed issue

Does this happen always or only sometimes? If only sometimes you probably made changes to the recipe or dependent recipes while building. You cannot do that. On Mon, Jul 2, 2018 at 7:27 AM, techi eth wrote: > Hi, > > Can anybody give me hint over below issue. > > Thanks > > -- Forwarded m

[yocto] populate_sdk in image class

A long time ago the image class got an inherit to the populate_sdk* class which brings a lot of dependencies on python modules. Is it strictly necessary that to build an image, i need to satisfy nativesdk-libgcc among others? Is there not a performance and complexity impact? I never needed to use

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

Ouch you are right. Damn me for using pyro still? After applying this patch I will report on the remaining issues. On Fri, May 4, 2018 at 2:41 PM, Alexander Kanavin wrote: > On 05/04/2018 03:42 PM, Paulo Neves wrote: >> >> I will propose a patch with a default bb.debug, and

Re: [yocto] ROOTFS_RPM_DEBUG undocumented

is to openembedded mailing list as this effectively makes RPM unusable in a container. I will also provide a Dockerfile to reproduce this problem. [1] https://github.com/moby/moby/issues/23137#issuecomment-359097008 Paulo Neves On Thu, May 3, 2018 at 3:03 PM, Alexander Kanavin wrote: > On 05/03/2018

[yocto] ROOTFS_RPM_DEBUG undocumented

s print in verbose mode and print the output to bb.debug instead of bb.note. I am happy to provide a patch upon decision or suggestions. Paulo Neves [1] NOTE: recipe drotag-cloud-image-debug-1.0-r0: task do_rootfs: Started [2] DEBUG: drotag-cloud-image-debug-1.0-r0 do_rootfs: Executing pytho

[yocto] COMPATIBLE_MACHINE not honored in native extended recipes

201e090f031a14a Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Fri, 12 Jan 2018 15:58:39 +0100 Subject: [PATCH 1/1] Fix COMPATIBLE_MACHINE for -native recipe variants. Hello I am having a problem where I want a recipe, along with its -native version to only be available when allowed by compatib

[yocto] user space package recommends kernel fragment with builting CONFIG

Hello all, I have the idea I am doing someting in a strange way but correct me if I am wrong. I want to make hostapd RRECOMEND .config fragments which have wireless drivers. How do I achieve this? Paulo Neves -- ___ yocto mailing list yocto

[yocto] [PATCH] fetch2/__init_.py removed bb.error which caused exit code 1

on like no problem happened. but marks the exit code as 1 which is a disaster. From 140d8209895e3effd4f8ee5c92e49f0c653bf3e2 Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Wed, 5 Jul 2017 14:49:28 +0200 Subject: [PATCH 1/2] Workaround to avoid exit 1 status. The reason it happens is that t

[yocto] [PATCH] staging.bbclass: Refactored sysroot_stage_dir* functions.

3768fa5b5f8c446c96590df54dde59beadd15e5f Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Tue, 18 Jul 2017 15:15:32 +0200 Subject: [PATCH 1/1] staging.bbclass: Refactored sysroot_stage_dir* functions. Removed sysroot_stage_libdir because it just forwarded the arguments to sysroot_stage_libdir with no other function

Re: [yocto] multiconfig samples not put in the build dir.

, 2017 at 9:28 AM, Gary Thomas wrote: > On 2017-04-12 09:15, Paulo Neves wrote: >> >> Hello Gary. >> >> I didn't know it was not a coreutil. To do it in another way i think >> this simple code will grow. Before refactoring could I have other >> opinions? &g

Re: [yocto] multiconfig samples not put in the build dir.

I expect it to rename all the .conf.sample files from .conf.sample to .conf. Give it a try ;) On Wed, Apr 12, 2017 at 8:54 AM, Gary Thomas wrote: > On 2017-04-12 08:48, Paulo Neves wrote: >> >> Hello, >> >> I thought it would be consistent to have the multiconfig samp

[yocto] multiconfig samples not put in the build dir.

Hello, I thought it would be consistent to have the multiconfig samples to also be populated just like the local.conf. I produced a patch accordingly: >From 6091978f666463c46093203b74f28b82a9bf4d47 Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Mon, 3 Apr 2017 11:23:12 +0200 Subject: [PA

[yocto] Bug 11307 - sstate.bbclass tries to modify mirror files

ption 2 Related to (https://bugzilla.yoctoproject.org/show_bug.cgi?id=10857) >From aa8cab9660744c8d5277f8e82f10a844884aff78 Mon Sep 17 00:00:00 2001 From: Paulo Neves Date: Tue, 11 Apr 2017 10:57:47 +0300 Subject: [PATCH] Added test for write ability of sstate-mirror .siginfo --- meta

[yocto] (no subject)

led to download fullsysroot. Perhaps you need to run 'opkg update'? * opkg_install: Cannot install package fullsysroot. Installing run-postinsts (1.0-r0) on root. Best regards Paulo Neves -- ___ yocto mailing list yoc

Re: [yocto] Using files from package dependencies

o/40976056#40976056 Best regards Paulo Neves On Mon, Dec 5, 2016 at 10:08 AM, Nicolas Dechesne wrote: > On Mon, Dec 5, 2016 at 10:10 AM, Paulo Neves wrote: >> Sorry for my ambiguity. When I mentioned binaries I meant general >> binary data, not necessarily executable. Their onl

Re: [yocto] Using files from package dependencies

n the recipe bake. Thanks Paulo Neves On Mon, Dec 5, 2016 at 8:58 AM, Nicolas Dechesne wrote: > On Mon, Dec 5, 2016 at 9:54 AM, Paulo Neves wrote: >> The files form this other package are mostly binaries in a directory >> structure. I have to create an additional package which wor

Re: [yocto] Using files from package dependencies

es need to be additionally exported to the sysroot and this was typically done through the -dev package. Can you point me at where this is documented? I am having a huge difficulty trying to find these conventions in the manual or by googling. Thanks Paulo Neves On Mon, Dec 5, 2016 at 8:42 A

[yocto] Using files from package dependencies

Hello, I have a recipe which depends on another package's file to do it's job. How can I arbitrarily access a file from another package which my recipe depends on? I searched for this kind of problem but did not find it Best regards P