From: Seebs <seebs@seebs.net>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log
Date: Thu, 14 Sep 2017 09:59:23 -0500 [thread overview]
Message-ID: <20170914095923.05ad9f62@seebsdell> (raw)
In-Reply-To: <CAJTo0LZr+mFy9_behSGMpfy_=A0PUGOm_9xf2Co05PKqZQ5yOQ@mail.gmail.com>
On Thu, 14 Sep 2017 15:53:09 +0100
"Burton, Ross" <ross.burton@intel.com> 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
next prev parent reply other threads:[~2017-09-14 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 20:46 [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log Martin Jansa
2017-09-13 20:50 ` Martin Jansa
2017-09-13 22:08 ` Seebs
2017-09-13 22:28 ` Martin Jansa
2017-09-14 14:27 ` Seebs
2017-09-14 13:17 ` Burton, Ross
2017-09-13 22:09 ` Seebs
2017-09-14 14:53 ` Burton, Ross
2017-09-14 14:59 ` Seebs [this message]
2017-09-19 15:18 ` [RFC][PATCHv2] " Martin Jansa
2017-10-16 15:01 ` Martin Jansa
2017-10-16 15:10 ` Burton, Ross
2017-10-16 15:50 ` Martin Jansa
2017-12-19 16:09 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170914095923.05ad9f62@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.