|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
are you both using systemd or sysvinit
toggle quoted messageShow quoted text
On Thu, Sep 23, 2021 at 3:26 PM Markus Volk <f_l_k@...> wrote:
|
|
|
|
Re: googletest shared library
Federico Pellegrin
Hi, Regarding the INSANE_SKIP: as that files get packed in the "-dev" package, you should probably then accordingly have: INSANE_SKIP_${PN}-dev += "dev-elf" Cheers, Federico
Il giorno gio 23 set 2021 alle ore 16:46 Lijun Chen <lijchen@...> ha scritto:
|
|
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
Markus Volk
I'm surprised mount doesn't complain about those first 5 lines! Those are not properly-formed fstab(5) entries. No, it doesn't. Those entries are ignored except /boot. One interesting thing: i always had that bunch of malformed fstab entries. Before the change from static to uuid it looked like this in fstab: /dev/mmcblk1p1 loader1 vfat defaults 0 0 /dev/mmcblk1p2 reserved1 vfat defaults 0 0 /dev/mmcblk1p3 reserved2 vfat defaults 0 0 /dev/mmcblk1p4 loader2 vfat defaults 0 0 /dev/mmcblk1p5 atf vfat defaults 0 0 /dev/mmcblk1p6 /boot vfat defaults 0 0 Now it looks like wic fails in getting the correct value and uses sda as a best bet you're proposing (a bunch of malformed fstab(5) entries) should be considered correct. I guess i just got used to it because it has always been like this since i build for the rock-pi
In the mean time I'd like to apply your patch 2/2, if you could please add your SoB line? Have sent new patches. Just delete the first one if you dont need it
|
|
|
|
[meta-rockchip][PATCH v2 2/2] rockchip-wic.inc: dont let wic edit fstab by default
Markus Volk
Signed-off-by: MarkusVolk <f_l_k@...>
--- conf/machine/include/rockchip-wic.inc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/conf/machine/include/rockchip-wic.inc b/conf/machine/include= /rockchip-wic.inc index 15010a0..30b0d57 100644 --- a/conf/machine/include/rockchip-wic.inc +++ b/conf/machine/include/rockchip-wic.inc @@ -26,3 +26,6 @@ WICVARS:append =3D " \ SPL_BINARY \ UBOOT_SUFFIX \ " + +# Do not update fstab file while creating wic images +WIC_CREATE_EXTRA_ARGS ?=3D "--no-fstab-update" --=20 2.25.1
|
|
|
|
[meta-rockchip][PATCH v2 1/2] rockchip.wks: use uuid for all partitions
Markus Volk
My rock pi 4 refused to boot with the latest changes because there are fa=
lse entries written to fstab. Fix this by using uuid for all partitions Signed-off-by: MarkusVolk <f_l_k@...> --- wic/rockchip.wks | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/wic/rockchip.wks b/wic/rockchip.wks index 5ee276b..90bdb27 100644 --- a/wic/rockchip.wks +++ b/wic/rockchip.wks @@ -15,12 +15,12 @@ # boot 32768 229376 # root 262144 - (suggested) =20 -part loader1 --offset 32 --fixed-size 4000K --source r= awcopy --sourceparams=3D"= file=3D${SPL_BINARY}" -part reserved1 --offset 4032 --fixed-size 64K -part reserved2 --offset 4096 --fixed-size 4096K -part loader2 --offset 8192 --fixed-size 4096K --source r= awcopy --sourceparams=3D"= file=3Du-boot.${UBOOT_SUFFIX}" -part atf --offset 12288 --fixed-size 4096K -part /boot --offset 16384 --size 114688K --active --source b= ootimg-partition --fstype=3Dvfat --label boot --sourceparams=3D= "loader=3Du-boot" -part / --source r= ootfs --fstype=3Dext4 --label root --use-uuid +part loader1 --offset 32 --fixed-size 4000K --source rawcopy --sourcepar= ams=3D"file=3D${SPL_BINARY}" --use-uuid +part reserved1 --offset 4032 --fixed-size 64K --use-uuid +part reserved2 --offset 4096 --fixed-size 4096K --use-uuid +part loader2 --offset 8192 --fixed-size 4096K --source rawcopy --sourcep= arams=3D"file=3Du-boot.${UBOOT_SUFFIX}" --use-uuid +part atf --offset 12288 --fixed-size 4096K --use-uuid +part /boot --offset 16384 --size 114688K --active --source bootimg-parti= tion --fstype=3Dvfat --label boot --sourceparams=3D"loader=3Du-boot" --us= e-uuid +part / --source rootfs --fstype=3Dext4 --label root --use-uuid =20 -bootloader --ptable gpt --append=3D"console=3Dtty1 console=3D${RK_CONSOL= E_DEVICE},${RK_CONSOLE_BAUD}n8 rw rootfstype=3Dext4 init=3D/sbin/init" +bootloader --ptable gpt --append=3D"console=3Dtty1 console=3D${RK_CONSOL= E_DEVICE},${RK_CONSOLE_BAUD}n8 rw rootfstype=3Dext4 init=3D/sbin/init" --=20 2.25.1
|
|
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
Trevor Woerner
On Thu 2021-09-23 @ 09:45:06 PM, Markus Volk wrote:
Thanks for testing. It's also strange that my fstab also has those entries, but they're apparently ignored in my setup since, commented in or commented out, they don't seem to affect my board's ability to boot. I'm surprised mount doesn't complain about those first 5 lines! Those are notI wonder if just applying your 2nd patch would be enough (i.e. the one thatApplying only the second patch should be enough to hide the problem, but as soon as properly-formed fstab(5) entries. I wouldn't call only applying your second patch a form of "hiding the problem". Neither what we had before (a bunch of /dev/sda entries) and what you're proposing (a bunch of malformed fstab(5) entries) should be considered correct. If a user messes with BSP-level variables, then they should expect what they get (?). We can add the --use-uuid line to the /boot entry if you really think it should be mounted on boot, but we shouldn't use it on the others and cause wic to generate a bad fstab. There are examples of other boards that don't mount /boot by default (raspi for sure, and I think bbb too). I'll try to look deeper to figure out what's generating those /dev/sda entries. Maybe there's a way to disable them without resorting to WIC_CREATE_EXTRA_ARGS? In the mean time I'd like to apply your patch 2/2, if you could please add your SoB line? u-boot is able to find its partitons even if '--use-uuid' is set. As you mentioned u-boot doesn'tSorry, I wasn't clear. u-boot doesn't use those labels to find u-boot, my guess is that the SoC's ROM firmware blindly looks at fixed offsets for the "what to boot" (and therefore isn't using UUIDs either). Either the ROM loads the atf, which then loads u-boot's spl, or the ROM loads the atf and then loads u-boot's spl from fixed locations. Perhaps u-boot's spl uses labels to find u-boot proper, but that's irrelevant. My guess is that Khem probably likes building with a long list of layers asAre you using poky or a distro other than "nodistro"? Perhaps otherThats not unlikely. I have a long layer-list in bblayers.conf to build my image: well ;-) I'll try using poky to see if that changes anything. Using oecore, bitbake, meta-arm, and meta-rockchip I can't reproduce what you and Khem are seeing. One of these days I'll have to check to make sure meta-rockchip is behaving like it should when mixed with other layers.
|
|
|
|
scikit-learn
#gatesgarth
#yocto
abhi <abhishek.kumar@...>
hi guys,
i am trying to build scikit-learn on yocto but i am getting error of setup.py ,it is showing failed i build all dependencies but it is giving error please try to give some i dea ERROR: python3-sklearn-1.0-r0 do_compile: 'python3 setup.py build ' execution failed. ERROR: python3-sklearn-1.0-r0 do_compile: Execution of '/home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/temp/run.do_compile.17835' failed with exit code 1: /home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3: can't open file '/home/abhishek/sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/scikit-learn-1.0/setup.py': [Errno 2] No such file or directory WARNING: exit code 1 from a shell command. ERROR: Logfile of failure stored in: /home/abhishek/exaleap/sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/temp/log.do_compile.17835 Log data follows: | DEBUG: Executing shell function do_compile | /home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3: can't open file '/home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/scikit-learn-1.0/setup.py': [Errno 2] No such file or directory | ERROR: 'python3 setup.py build ' execution failed. | WARNING: exit code 1 from a shell command. | ERROR: Execution of '/home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/temp/run.do_compile.17835' failed with exit code 1: | /home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3: can't open file '/home/abhishek//sources/fu540-build/tmp-glibc/work/riscv64-oe-linux/python3-sklearn/1.0-r0/scikit-learn-1.0/setup.py': [Errno 2] No such file or directory | WARNING: exit code 1 from a shell command.
|
|
|
|
Re: [meta-rockchip][PATCH] use uuid instead of hard-coding root device
Markus Volk
Am 23.09.21 um 13:59 schrieb Trevor
Woerner:
Curious. I boot tested my patch on multiple boards and I've built and booted numerous images on my rock-pi-4b and rock64 boards in the last day or so since I applied the patch. I'll try some "clean" builds and see if that makes a difference. I don't doubt your report (especially since Khem confirmed it), I'd just like to know for myself what's different. That is really strange. As soon as there are those /dev/sda* entries in my fstab my rock-pi-4c doesn't boot up anymore. As soon as i comment them out or delete them, everything is working again. I wonder if just applying your 2nd patch would be enough (i.e. the one that removes the /dev/sda* lines from /etc/fstab)? It's odd that the first 6 entries in the wic file would need UUIDs since it's the SoC's ROM firmware that uses them, and I'm pretty sure the Rockchip firmware isn't using UUIDs (my guess is it's just blindly grabbing whatever it finds at specific offsets). The things stored in those partitions are u-boot related bits (atf, spl, the u-boot binary itself) so by the time Linux starts, those things are already "behind" us. I can't see how adding UUIDs to the partitions holding u-boot would affect how the kernel finds the root partition (?). Applying only the second patch should be enough to hide the problem, but as soon as one decides to disable WIC_CREATE_EXTRA_ARGS for example because he/she wants /boot to be mounted automatically, those non working /dev/sda* entries will be written into fstab again. With the first patch they are included like this and are mountable via fstab: UUID=0C48-9342 loader1 vfat defaults 0 0 UUID=C4D3-D17A reserved1 vfat defaults 0 0 UUID=8FBE-2551 reserved2 vfat defaults 0 0 UUID=35FA-8BBB loader2 vfat defaults 0 0 UUID=CFF3-5D80 atf vfat defaults 0 0 UUID=832C-48C4 /boot vfat defaults 0 0 u-boot is able to find its partitons even if '--use-uuid' is set. As you mentioned u-boot doesn't know about uuid but it seems to be able to find its partitions nevertheless. But if '--use-uuid' is not set, wic writes /dev/sda* instead of the correct UUID values to fstab. So its not u-boot that needs uuid to be set but fstab. Of course it would be nice, if wic didn't try to add the u-boot partitions to fstab at all. I guess nobody ever needs to have them mounted into userspace ( except possibly /boot). Are you using poky or a distro other than "nodistro"? Perhaps other layers/distros are affecting the build? Thats not unlikely. I have a long layer-list in bblayers.conf to build my image: /home/flk/build/poky/meta \ /home/flk/build/poky/meta-poky \ /home/flk/build/poky/meta-yocto-bsp \ /home/flk/build/poky/meta-rockchip \ /home/flk/build/poky/meta-rockchip-extras \ /home/flk/build/poky/meta-wayland \ /home/flk/build/poky/meta-retro \ /home/flk/build/poky/meta-retro-wayland \ /home/flk/build/poky/meta-rauc \ /home/flk/build/poky/meta-openembedded/meta-oe \ /home/flk/build/poky/meta-openembedded/meta-multimedia \ /home/flk/build/poky/meta-openembedded/meta-networking \ /home/flk/build/poky/meta-openembedded/meta-xfce \ /home/flk/build/poky/meta-openembedded/meta-gnome \ /home/flk/build/poky/meta-openembedded/meta-python \ /home/flk/build/poky/meta-openembedded/meta-filesystems \ /home/flk/build/poky/meta-arm/meta-arm \ /home/flk/build/poky/meta-arm/meta-arm-toolchain \ /home/flk/build/poky/meta-kodi \ /home/flk/build/poky/meta-browser/meta-chromium \ /home/flk/build/poky/meta-browser/meta-firefox \ /home/flk/build/poky/meta-clang \ best regards, Markus
|
|
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 9/23/2021
Steve Sakoman
On Thu, Sep 23, 2021 at 5:40 AM Trevor Gamblin
<trevor.gamblin@...> wrote: I was looking at two issues prior to the meeting. Sadly, due to inadequate caffeine blood levels and the early hour I confused the two. So this explains why I couldn't find the logs during the meeting. So nothing to post :-( Steve
|
|
|
|
Re: Using bitbake with external SDK
#sdk
#zeus
#toolchain
On Thu, Sep 23, 2021 at 6:46 AM <enrico.buffoli1994@...> wrote:
if its eSDK then you can, with standard application SDK not so much. Best regards
|
|
|
|
Re: googletest shared library
look into package-split/ directory inside googletest build area and
toggle quoted messageShow quoted text
see how things changes when you use SOLIBS option. I wonder why its ignoring .h files
On Thu, Sep 23, 2021 at 6:36 AM Lijun Chen <lijchen@...> wrote:
|
|
|
|
Re: Minutes: Yocto Project Weekly Triage Meeting 9/23/2021
Richard Purdie
On Thu, 2021-09-23 at 11:40 -0400, Trevor Gamblin wrote:
I did look at it. It was using a modified oe-selftest with threading instead of multiprocess. We're not using that so I closed it. Cheers, Richard
|
|
|
|
gcov support for target in Yocto
Lijun Chen
Hi,
Anybody knows how to enable gcov support for the target in Yocto?
Thanks, Lijun This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|
|
Re: [ptest-runner][PATCH 3/3] utils.c: add system data collection when a test gets stuck.
Alexander Kanavin
Not sure what happened here, I published the patches in https://github.com/kanavin/ptest-runner2 Alex
On Thu, 23 Sept 2021 at 18:33, Anibal Limon <anibal.limon@...> wrote:
|
|
|
|
Re: [ptest-runner][PATCH 3/3] utils.c: add system data collection when a test gets stuck.
Anibal Limon
Hi Alex, Do you have a repo/branch for this patch?. I'm having issues applying... ... alimon@blackbox:~/upstream/ptest-runner2$ git am -3 ~/Downloads/\[ptest-runner\]\[PATCH\ 3_3\]\ utils.c_\ add\ system\ data\ collection\ when\ a\ test\ gets\ stuck..eml Applying: utils.c: add system data collection when a test gets stuck. error: sha1 information is lacking or useless (utils.c). error: could not build fake ancestor Patch failed at 0001 utils.c: add system data collection when a test gets stuck. hint: Use 'git am --show-current-patch=diff' to see the failed patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort". ... Regards, Anibal
On Thu, 16 Sept 2021 at 07:46, Alexander Kanavin <alex.kanavin@...> wrote: Currently, ptest-runner simply kills the offending test without further ado,
|
|
|
|
Re: [PATCH v2 ptest-runner 2/2] main: Do not return number of failed tests when calling ptest-runner
Anibal Limon
On Mon, 20 Sept 2021 at 04:23, Alexander Kanavin <alex.kanavin@...> wrote:
I was OOO for futher you can find me with nickname alimon at #yocto at Libera.
Applied, Thanks, Anibal
|
|
|
|
[meta-security][PATCH] dmverity: Make use of DATA_BLOCK_SIZE variable in initrdscript.
Paulo Neves
From: Christer Fletcher <christer.fletcher@...>
DATA_BLOCK_SIZE variable was set in dm-verity-img.bbclass at build time but the initrdscript was not updated to pass the DATA_BLOCK_SIZE to the veritysetup. Now the functionality is complete. Signed-off-by: Paulo Neves <paulo.neves1@...> --- recipes-core/initrdscripts/initramfs-framework-dm/dmverity | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/recipes-core/initrdscripts/initramfs-framework-dm/dmverity b/recipes-core/initrdscripts/initramfs-framework-dm/dmverity index 888052c..c815940 100644 --- a/recipes-core/initrdscripts/initramfs-framework-dm/dmverity +++ b/recipes-core/initrdscripts/initramfs-framework-dm/dmverity @@ -6,6 +6,7 @@ dmverity_enabled() { dmverity_run() { DATA_SIZE="__not_set__" + DATA_BLOCK_SIZE="__not_set__" ROOT_HASH="__not_set__" . /usr/share/misc/dm-verity.env @@ -49,7 +50,7 @@ dmverity_run() { done veritysetup \ - --data-block-size=1024 \ + --data-block-size=${DATA_BLOCK_SIZE} \ --hash-offset=${DATA_SIZE} \ create rootfs \ ${RDEV} \ -- 2.25.1
|
|
|
|
Minutes: Yocto Project Weekly Triage Meeting 9/23/2021
Trevor Gamblin
Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alex, Bruce, Kiran, Randy, Richard, Ross,
Saul, Stephen, Steve, Trevor ARs: - Steve to review failure logs for 14557 and post any that might be useful - Richard to have a look at bug 11801 Notes:
- (carried over) Steve
encountered build failures such as the one in https://errors.yoctoproject.org/Errors/Details/593109/
when attempting to run dunfell builds with the PARALLEL_MAKE load
averaging added. WR is testing/investigating on internal
Autobuilder instance - Trevor is still planning on looking into
this!
Medium+ 3.4 Unassigned Enhancements/Bugs: 68 (No change) Medium+ 3.5 Unassigned Enhancements/Bugs: 10 (No
change) AB-INT Bugs: 54
(Last week 49)
|
|
|
|
"stack smashing detected" when building aarch64 kernel
Rasmus Villemoes
I've recently started getting an internal compiler error when building
an aarch64 kernel. It only happens once in a while, and re-running the task usually just succeeds, so I don't know how to reproduce or trigger this at will. Two examples: === CC [M] drivers/gpu/drm/nouveau/nvkm/subdev/fb/gm20b.o CC [M] drivers/net/ethernet/mellanox/mlx5/core/rl.o CC [M] drivers/gpu/drm/nouveau/nvkm/subdev/fb/gp100.o *** stack smashing detected ***: <unknown> terminated In file included from .../kernel-source/arch/arm64/include/asm/atomic.h:15, from .../kernel-source/include/linux/atomic.h:7, from .../kernel-source/include/asm-generic/bitops/atomic.h:5, from .../kernel-source/arch/arm64/include/asm/bitops.h:26, from .../kernel-source/include/linux/bitops.h:29, from .../kernel-source/include/linux/kernel.h:12, from .../kernel-source/include/linux/uio.h:8, from .../kernel-source/include/linux/socket.h:8, from .../kernel-source/include/uapi/linux/if.h:25, from .../kernel-source/net/mac80211/led.c:7: .../kernel-source/include/net/inet_sock.h: In function 'inet_sk_state_load': .../kernel-source/arch/arm64/include/asm/barrier.h:114:8: internal compiler error: Aborted 114 | union { __unqual_scalar_typeof(*p) __val; char __c[1]; } __u; \ | ^ .../kernel-source/include/asm-generic/barrier.h:142:29: note: in expansion of macro '__smp_load_acquire' 142 | #define smp_load_acquire(p) __smp_load_acquire(p) | ^~~~~~~~~~~~~~~~~~ .../kernel-source/include/net/inet_sock.h:312:9: note: in expansion of macro 'smp_load_acquire' 312 | return smp_load_acquire(&sk->sk_state); | ^~~~~~~~~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. .../kernel-source/scripts/Makefile.build:279: recipe for target 'net/mac80211/led.o' failed make[3]: *** [net/mac80211/led.o] Error 1 make[3]: *** Waiting for unfinished jobs.... CC [M] drivers/net/ethernet/mellanox/mlx5/core/lag.o === CC [M] drivers/gpu/drm/nouveau/nvkm/nvfw/ls.o CC [M] drivers/gpu/drm/drm_modeset_helper.o CC [M] drivers/gpu/drm/drm_scdc_helper.o *** stack smashing detected ***: <unknown> terminated In file included from .../kernel-source/include/linux/regulator/consumer.h:35, from .../kernel-source/drivers/gpu/drm/nouveau/include/nvif/os.h:27, from .../kernel-source/drivers/gpu/drm/nouveau/include/nvkm/core/os.h:4, from .../kernel-source/drivers/gpu/drm/nouveau/include/nvkm/core/oclass.h:3, from .../kernel-source/drivers/gpu/drm/nouveau/include/nvkm/core/device.h:4, from .../kernel-source/drivers/gpu/drm/nouveau/include/nvkm/core/subdev.h:4, from .../kernel-source/drivers/gpu/drm/nouveau/nvkm/nvfw/ls.c:22: .../kernel-source/include/linux/suspend.h:364:36: internal compiler error: Aborted 364 | extern void mark_free_pages(struct zone *zone); | ^~~~ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. .../kernel-source/scripts/Makefile.build:280: recipe for target 'drivers/gpu/drm/nouveau/nvkm/nvfw/ls.o' failed make[5]: *** [drivers/gpu/drm/nouveau/nvkm/nvfw/ls.o] Error 1 make[5]: *** Waiting for unfinished jobs.... CC [M] drivers/gpu/drm/drm_gem_framebuffer_helper.o === This is with hardknott, aarch64-oe-linux-gcc (GCC) 10.2.0, building 5.10.* kernels (5.10.45 and 5.10.65 in the cases above IIRC). The build is visiting drivers/gpu/drm/ in both cases, but in the former case it's not actually a TU in there that fails, but one in net/, so I'm not even sure it it has to do with something peculiar to the drivers/gpu/drm/ modules. Has anyone seem something like this, or any ideas for figuring out what's going on? Rasmus
|
|
|
|
Re: googletest shared library
Lijun Chen
I tried INSANE_SKIP_${PN} += "dev-elf" and "dev-so", still got the QA error:
ERROR: googletest-1.10.0-r0 do_package_qa: QA Issue: -dev package googletest-dev contains non-symlink .so '/usr/lib/libgmock.so'
I also tried adding " -DCMAKE_INSTALL_PREFIX=/usr/local" to EXTRA_OEMAKE, and got the following error:
-dev package googletest-dev contains non-symlink .so '/usr/lib/libgtest_main.so' -dev package googletest-dev contains non-symlink .so '/usr/lib/libgmock_main.so' -dev package googletest-dev contains non-symlink .so '/usr/lib/libgtest.so' [dev-elf] ERROR: googletest-1.10.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them. ERROR: Logfile of failure stored in: /home/lijchen/hdd/ivdp/yocto/imx8/imx-yocto-bsp-Hardknott/build-imx8qmmek/tmp/work/cortexa72-cortexa53-crypto-poky-linux/googletest/1.10.0-r0/temp/log.do_package_qa.24701 ERROR: Task (/home/lijchen/hdd/ivdp/yocto/imx8/imx-yocto-bsp-Hardknott/sources/meta-openembedded/meta-oe/recipes-test/googletest/googletest_git.bb:do_package_qa) failed with exit code '1'
ERROR: googletest-1.10.0-r0 do_package: QA Issue: googletest: Files/directories were installed but not shipped in any package:
/usr/local/include /usr/local/lib/libgmock.so /usr/local/lib/libgtest_main.so /usr/local/lib/libgmock_main.so /usr/local/lib/libgtest.so /usr/local/lib/cmake /usr/local/lib/pkgconfig /usr/local/lib/cmake/GTest /usr/local/lib/cmake/GTest/GTestTargets.cmake /usr/local/lib/cmake/GTest/GTestConfigVersion.cmake /usr/local/lib/cmake/GTest/GTestConfig.cmake /usr/local/lib/cmake/GTest/GTestTargets-noconfig.cmake /usr/local/lib/pkgconfig/gtest_main.pc /usr/local/lib/pkgconfig/gtest.pc /usr/local/lib/pkgconfig/gmock_main.pc /usr/local/lib/pkgconfig/gmock.pc /usr/local/include/gtest /usr/local/include/gmock /usr/local/include/gtest/gtest_prod.h /usr/local/include/gtest/gtest-test-part.h /usr/local/include/gtest/gtest_pred_impl.h /usr/local/include/gtest/gtest-matchers.h /usr/local/include/gtest/gtest-printers.h /usr/local/include/gtest/gtest.h /usr/local/include/gtest/gtest-param-test.h /usr/local/include/gtest/gtest-death-test.h /usr/local/include/gtest/gtest-typed-test.h /usr/local/include/gtest/gtest-message.h /usr/local/include/gtest/gtest-spi.h /usr/local/include/gtest/internal /usr/local/include/gtest/internal/gtest-death-test-internal.h /usr/local/include/gtest/internal/gtest-filepath.h /usr/local/include/gtest/internal/gtest-param-util.h /usr/local/include/gtest/internal/gtest-string.h /usr/local/include/gtest/internal/gtest-type-util.h /usr/local/include/gtest/internal/gtest-internal.h /usr/local/include/gtest/internal/gtest-type-util.h.pump /usr/local/include/gtest/internal/gtest-port-arch.h /usr/local/include/gtest/internal/gtest-port.h /usr/local/include/gtest/internal/custom /usr/local/include/gtest/internal/custom/gtest-printers.h /usr/local/include/gtest/internal/custom/gtest.h /usr/local/include/gtest/internal/custom/README.md /usr/local/include/gtest/internal/custom/gtest-port.h /usr/local/include/gmock/gmock-function-mocker.h /usr/local/include/gmock/gmock-generated-function-mockers.h /usr/local/include/gmock/gmock-generated-actions.h.pump /usr/local/include/gmock/gmock-matchers.h /usr/local/include/gmock/gmock-generated-matchers.h /usr/local/include/gmock/gmock-more-matchers.h /usr/local/include/gmock/gmock.h /usr/local/include/gmock/gmock-generated-actions.h /usr/local/include/gmock/gmock-nice-strict.h /usr/local/include/gmock/gmock-spec-builders.h /usr/local/include/gmock/gmock-more-actions.h /usr/local/include/gmock/gmock-generated-function-mockers.h.pump /usr/local/include/gmock/gmock-cardinalities.h /usr/local/include/gmock/gmock-actions.h /usr/local/include/gmock/gmock-generated-matchers.h.pump /usr/local/include/gmock/internal /usr/local/include/gmock/internal/gmock-port.h /usr/local/include/gmock/internal/gmock-pp.h /usr/local/include/gmock/internal/gmock-internal-utils.h /usr/local/include/gmock/internal/custom /usr/local/include/gmock/internal/custom/gmock-port.h /usr/local/include/gmock/internal/custom/gmock-generated-actions.h.pump /usr/local/include/gmock/internal/custom/gmock-matchers.h /usr/local/include/gmock/internal/custom/gmock-generated-actions.h /usr/local/include/gmock/internal/custom/README.md Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. googletest: 69 installed and not shipped files. [installed-vs-shipped] ERROR: googletest-1.10.0-r0 do_package: Fatal QA errors found, failing task.
From: Federico Pellegrin <fede@...>
Sent: Thursday, September 23, 2021 10:27:39 AM To: Lijun Chen Cc: yocto@... Subject: Re: [yocto] googletest shared library Hi,
To skip the QA you can use:
INSANE_SKIP_${PN} += "dev-elf"
(or any QA part you'd like to skip, ie. dev-elf or dev-so ...)
Cheers,
Federico
Il giorno gio 23 set 2021 alle ore 15:33 Lijun Chen <lijchen@...> ha scritto:
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|
|
|