This could be a security issue since it's the "bad RPATH" WARNING: QA Issue: package pseudo contains bad RPATH /intel/poky/builds/sanity/tmp/sysroots/qemuppc/usr/lib in file /intel/poky/builds/sanity/tmp/work/ppc603e-poky-linux/pseudo-1.3-r7/packages-split/pseudo/usr/bin/pseudo WARNING: QA Issue: package pseudo contains bad RPATH /intel/poky/builds/sanity/tmp/sysroots/qemuppc/usr/lib in file /intel/poky/builds/sanity/tmp/work/ppc603e-poky-linux/pseudo-1.3-r7/packages-split/pseudo/usr/bin/pseudodb WARNING: QA Issue: package pseudo contains bad RPATH /intel/poky/builds/sanity/tmp/sysroots/qemuppc/usr/lib in file /intel/poky/builds/sanity/tmp/work/ppc603e-poky-linux/pseudo-1.3-r7/packages-split/pseudo/usr/bin/pseudolog WARNING: QA Issue: package pseudo contains bad RPATH /intel/poky/builds/sanity/tmp/sysroots/qemuppc/usr/lib in file /intel/poky/builds/sanity/tmp/work/ppc603e-poky-linux/pseudo-1.3-r7/packages-split/pseudo/usr/lib/pseudo/lib/libpseudo.so
Currently investigating...
Just some research notes: commit 6527c17d567405117bf32a51c0d8b03dc83b9b37 Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Mon Sep 26 21:12:25 2011 +0100 pseudo: Fix QA warnings ^-- this appears to try to remove RPATH in pseudo commit 35759f977eec6ef81e125a509a7148d7e53a6515 Author: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Date: Thu Jan 12 17:30:24 2012 +0100 bitbake.conf: search /lib for -native builds Changes to BUILD_LDFLAGS are required due to the recent movement of some libraries from ${libdir} to ${base_libdir}. ${base_libdir} must be now in the linker search path to avoid build problems of -native packages. ^-- this adds another rpath to BUILD_LDFLAGS It looks to surface examination as though pseudo.inc is using RPATH= in the expectation that it will remove all rpaths, but instead it's removing only one of the two, or something like that.
Oh, nevermind. That was all a red herring. pseudo sets itself a local rpath value based on --with-sqlite. Fixing this.
Created attachment 464 [details] pseudo.inc patch to disable rpath usage
Added a proposed patch. Fixed in upstream a different way, but we can fix it in yocto just by turning off the rpath generation.
Merged in master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=554cac7d13bae47999aabaa5cabb4173e7e75812