For world, we don't have images to test with. But at least, add sanity check script later to check whether multilib libraries are there in the build directory. Again, that benefits those which have the images to test with, for instance, recipes in sato, sato-sdk, lsb-sdk etc.
(In reply to comment #0) > For world, we don't have images to test with. But at least, add sanity check > script later to check whether multilib libraries are there in the build > directory. > > Again, that benefits those which have the images to test with, for instance, > recipes in sato, sato-sdk, lsb-sdk etc. hi Shane, Can you please elaborate more on this task, I don't have the big picture so I don't really know where to start. For instance do you want a script run automatically for world (at the end) to check for multilib libraries?
I was looking around to get a handle on this and found https://bugzilla.yoctoproject.org/show_bug.cgi?id=1488 Do I have to add the sanity check in sanity.bbclass like to Peter did in that patch?
Looking over insane.bbclass
working to determine two aspects: 1. which is the target directory to check upon 2. how to determine from a global method what particular libraries (naming) to search for (in a particular workdir). This information is found in the makefile.
got feedback from Richard and the goal for this task is to add a package_qa_check_multilib in insane.bbclass that would * check for ${libdir} in path * check for other library directories in path
Agreed to check for wrong library installation paths. For instance, catch recipe installing /lib/bar.so when ${base_libdir}="lib32" or installing in /usr/lib64 when ${libdir}="/usr/lib"
65d1eb7788870b3e318902c827097183f2dddafc
Verified in master branch / commit eed0d8765ea92f22e26d5b3aec0b9fe98f3af57f with ERROR_QA_append = " libdir" in local.conf