You should not copy things between sysroot and ${D}. There is
post-processing between those steps, so do it only between sysroots
please.

Alex

On Wed, 1 Mar 2023 at 07:28, Sundeep KOKKONDA
<sundeep.kokko...@windriver.com> wrote:
>
> Hello,
>
>
>
> I tried to copy the libLTO.so to ${D}. But this shows ERROR: 
> rust-llvm-1.67.0-r0 do_package_qa: QA Issue: -dev package rust-llvm-dev 
> contains non-symlink .so '/usr/lib/llvm-rust/lib/libLTO.so' [dev-elf] and I 
> had a look into symlink where it points... The libLTO.so files RPATH in ${D} 
> & sysroot-destdir are different as below,
>
>
>
> $ objdump -x 
> ./image/wdr/poky/buildA/tmp/work/x86_64-linux/rust-llvm-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib/libLTO.so
>  | grep 'R.*PATH'
>
>   RUNPATH              
> /wdr/poky/buildA/tmp/work/x86_64-linux/rust-llvm-native/1.67.0-r0/recipe-sysroot-native/usr/lib:/wdr/poky/buildA/tmp/work/x86_64-linux/rust-llvm-native/1.67.0-r0/recipe-sysroot-native/lib::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>
> $ objdump -x 
> ./sysroot-destdir/wdr/poky/buildA/tmp/work/x86_64-linux/rust-llvm-native/1.67.0-r0/recipe-sysroot-native/usr/lib/llvm-rust/lib/libLTO.so
>  | grep 'R.*PATH'
>
>   RUNPATH              
> $ORIGIN/../..:$ORIGIN/../../../../lib:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.:.
>
>
>
> Also, the libLTO.so is a symlink for libLTO.so.15. So, I tried copying both 
> libLTO.so & libLTO.so.15 but again getting below QA error:
>
> ERROR: rust-llvm-1.67.0-r0 do_package: QA Issue: File 
> '/usr/lib/llvm-rust/lib/libLTO.so' from rust-llvm was already stripped, this 
> will prevent future debugging! [already-stripped]
>
> ERROR: rust-llvm-1.67.0-r0 do_package: QA Issue: File 
> '/usr/lib/llvm-rust/lib/libLTO.so.15' from rust-llvm was already stripped, 
> this will prevent future debugging! [already-stripped]
>
> WARNING: rust-llvm-1.67.0-r0 do_package: rust-llvm-liblto-1.67.0 was 
> registered as shlib provider for libLTO.so.15, changing it to 
> rust-llvm-dev-1.67.0 because it was built later
>
> ERROR: rust-llvm-1.67.0-r0 do_package: Fatal QA errors were found, failing 
> task.
>
>
>
> So, I disabled stripping of binaries in kernel.bbclass (@line 743 : 
> #oe.package.runstrip((kernel_image_stripped, 8, strip, extra_sections))) but 
> still facing below errors.
>
> WARNING: rust-llvm-1.67.0-r0 do_package: rust-llvm-liblto-1.67.0 was 
> registered as shlib provider for libLTO.so.15, changing it to 
> rust-llvm-dev-1.67.0 because it was built later
>
> WARNING: rust-llvm-1.67.0-r0 do_package_qa: QA Issue: File 
> /usr/lib/llvm-rust/lib/libLTO.so.15 in package rust-llvm-liblto contains 
> reference to TMPDIR [buildpaths]
>
> WARNING: rust-llvm-1.67.0-r0 do_package_qa: QA Issue: File 
> /usr/lib/llvm-rust/lib/libLTO.so in package rust-llvm-dev contains reference 
> to TMPDIR [buildpaths]
>
> ERROR: rust-llvm-1.67.0-r0 do_package_qa: QA Issue: -dev package 
> rust-llvm-dev contains non-symlink .so '/usr/lib/llvm-rust/lib/libLTO.so' 
> [dev-elf]
>
> ERROR: rust-llvm-1.67.0-r0 do_package_qa: Fatal QA errors were found, failing 
> task.
>
>
> I tried to do the same with by adding my own task with 'addtask patchso after 
> do_install' but that is also having some issues while calling that task and 
> that is not recommended way to do it by Richard.
>
> Is there any way I can fix it or disable these checks for my testing?
>
>
>
>
>
> Thanks,
>
> Sundeep K.
>
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177869): 
https://lists.openembedded.org/g/openembedded-core/message/177869
Mute This Topic: https://lists.openembedded.org/mt/97113152/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to