On Thu, 14 Sep 2017 15:53:09 +0100 "Burton, Ross" <[email protected]> wrote:
> Example: > > path mismatch [5 links]: ino 27539515 db > '/data/poky-tmp/master/build/work/corei7-64-poky-linux/dbus/1.10.20-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux/x86_64-poky-linux-ld.bfd' > req > '/data/poky-tmp/master/build/sysroots-components/x86_64/binutils-cross-x86_64/usr/bin/x86_64-poky-linux/x86_64-poky-linux-ld'. > > Looks like this is just warning that there is a symlink, right? Hard link, not symlink. Symlinks are recorded separately, "links" is the hard link count in the filesystem, which doesn't include symlinks. That message is almost always Harmless. Although strictly speaking, it probably indicates that one of the links was made outside of pseudo, which in theory shouldn't happen, I think. At least, I *think* the current intent is to always use an exact match (both path and inode) if possible, so it shouldn't see a mismatch unless there's a path that got used but that isn't in the database. -s -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
