Results from chasing the RPATH pollution I was seeing: I don't have a fix for the underlying linker issue, but that is captured here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2965 Patch 1 is the warning fix from earlier, which is still a fix to the existing logic and should be applied. I've removed the "host-polluted" text though, as AFAICT the actual RPATH is not a problem, only the use of -rpath with the linker that produced it. Patch 2 is a fix to libtool on top of the existing fix-rpath.patch to normalize the strings. With this applied, all the link failures we have reproduced (including the one reported vs. owl_video last week) work correctly. No libraries in the resulting sysroot have a RPATH set to a default link directory. A few runnable binaries still trigger the warning though (but otherwise build successfully), I'm looking at that now -- I suspect these simply aren't using libtool, or else we've missed a spot where normalization and/or default directory pruning needs to happen. Andy _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
