How to fix Yocto QA error [already-stripped]

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to fix Yocto QA error [already-stripped]

Jump to solution
2,875 Views
Qiutt
Contributor II

Following UG10164 v.LF6.6.52_2.2.0 I tried to build sdk, but recived a QA error [already-stripped]. 

Does anybody have an idea how to fix it?

 

PC: ubuntu20.04 x86_64

1. Init build env: 

$ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.52-2.2.0.xml

$ repo sync

$ DISTRO=fsl-wayland MACHINE=imx8dxl-b0-lpddr4-evk source imx-setup-release.sh -b build-imx8dxl-b0

 

2. build:

$ bitbake core-image-minimal -c populate_sdk

 

QA error:

ERROR: ptest-runner-2.4.5+git-r0 do_package: QA Issue: File '/usr/bin/ptest-runner' from ptest-runner was already stripped, this will prevent future debugging! [already-stripped]
ERROR: ptest-runner-2.4.5+git-r0 do_package: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in: /work/QNX/imx-yocto-bsp/build-imx8dxl-b0/tmp/work/cortexa35-fsl-linux/ptest-runner/2.4.5+git/temp/log.do_package.2700152
ERROR: Task (/work/QNX/imx-yocto-bsp/sources/poky/meta/recipes-support/ptest-runner/ptest-runner_2.4.5.bb:do_package) failed with exit code '1'

Labels (2)
Tags (1)
1 Solution
2,813 Views
Qiutt
Contributor II

Thanks for your reply.

This QA occured on Ubuntu 20.04, but it did not happen on Ubuntu 22.04.
Although I don't know the reason, it seems to be caused by the OS version.

Adding INSANE_SKIP can skip it with ptest-runner, but there are many packages with this problem.

So, the best way may be updating the os version.

View solution in original post

0 Kudos
Reply
3 Replies
2,814 Views
Qiutt
Contributor II

Thanks for your reply.

This QA occured on Ubuntu 20.04, but it did not happen on Ubuntu 22.04.
Although I don't know the reason, it seems to be caused by the OS version.

Adding INSANE_SKIP can skip it with ptest-runner, but there are many packages with this problem.

So, the best way may be updating the os version.

0 Kudos
Reply
2,819 Views
frank58richard
Contributor I

Hello,

The QA error happens because the binary is stripped too early, blocking debugging. You can fix it by skipping the already-stripped check in the recipe or stopping the stripping during the build. Just add INSANE_SKIP_${PN} = "already-stripped" to the recipe and rebuild.

0 Kudos
Reply
2,851 Views
Harvey021
NXP TechSupport
NXP TechSupport

Hi,

I try to build again with the same steps that you've taken, that is success.

NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/4.6/x86_64-nativesdk-libc-4.6.tar.xz;sha256sum=... (will check PREMIRRORS first)
Sstate summary: Wanted 2888 Local 0 Mirrors 0 Missed 2888 Current 0 (0% match, 0% complete)############################### | ETA: 0:00:00
Initialising tasks: 100% |############################################################################################################| Time: 0:00:03
NOTE: Executing Tasks
WARNING: gnu-config-native-20240101+git-r0 do_fetch: Failed to fetch URL git://git.savannah.gnu.org/git/config.git;protocol=https;branch=master, attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 6495 tasks of which 0 didn't need to be rerun and all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 10 seconds

Summary: There were 3 WARNING messages.

 

Please try to clean the recipe "ptest-runner" and then rebuild it.

bitbake -c cleanall ptest-runner

My host: 22.04.1-Ubuntu

Regards

Harvey

0 Kudos
Reply