**** BEGIN LOGGING AT Sun Jul 05 02:59:58 2015 Jul 05 14:02:56 i have two machines with same arch, and libraries from one sysroot contains paths of the other... wtf oe Jul 05 14:28:17 that shouldn't even be possible, paths are adjusted when sstates are used, and when not, it was built for that sysroot. classic? Jul 05 14:31:29 nope Jul 05 14:37:49 could be the problem comes from gcc-cross- that contains path to sysroot/ ? Jul 05 14:40:47 http://lists.openembedded.org/pipermail/openembedded-core/2014-October/098253.html Jul 05 14:42:21 let's say you build gcc-cross-powerpcc for machine1, it's default sysroot will match sysroot of machine1... then building for machine2 if sysroot is not specified, it can compiles with sysroot of machine1... eww Jul 05 14:44:00 i will try to upgrade oe-core... Jul 05 14:45:59 we *always* specify --sysroot Jul 05 14:46:07 in fact, no sysroot default is even set anymore Jul 05 14:46:32 but it could be lost inside some dirty autotools/cmake scripts Jul 05 14:46:58 anyway not a problem anymore pparently, the only problem is my outdated oe-core :( Jul 05 14:49:12 again, when files are extracted into the sysroot from sstate, all files with hardcoded paths get those paths corrected with sed Jul 05 14:49:16 ah Jul 05 14:49:33 you cannot sed a binary ? :p Jul 05 14:49:55 which is why we take care of those relocation issues everywhere in other ways Jul 05 14:50:03 e.g. supplying wrapper scripts which set env vars, pass args, etc Jul 05 14:50:09 and those wrapper scripts *do* their paths substituted Jul 05 14:50:19 ok **** ENDING LOGGING AT Mon Jul 06 02:59:59 2015