From: Rustam Kovhaev <rkovhaev@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: xujialu <xujialu@vimux.org>,
masahiroy@kernel.org, Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: realpath "No such file or directory" warnings when building tags from KBUILD_OUTPUT directory
Date: Sun, 9 Aug 2020 14:00:56 -0700 [thread overview]
Message-ID: <20200809210056.GA1344537@thinkpad> (raw)
In-Reply-To: <20200809071627.GC1098830@kroah.com>
On Sun, Aug 09, 2020 at 09:16:27AM +0200, Greg Kroah-Hartman wrote:
> On Sat, Aug 08, 2020 at 01:28:22PM -0700, Rustam Kovhaev wrote:
> > running 'make ARCH=x86_64 COMPILED_SOURCE=1 cscope tags' in
> > KBUILD_OUTPUT directory produces lots of "No such file or directory"
> > warnings from realpath
> >
> > it seems like commit 4f491bb6ea2a greatly improved tags generation when
> > COMPILED_SOURCE=1 is set, but should we add "-q" flag for realpath in
> > all_compiled_sources() or probably it would be better to fix root cause
> > and make sure that for example we don't try to find objtool sources and
> > exclude other similar dirs during tags generation? what do you think?
> >
> > ...
> > realpath: special.h: No such file or directory
> > realpath: warn.h: No such file or directory
> > realpath: sigchain.c: No such file or directory
> > realpath: sigchain.h: No such file or directory
> > realpath: orc_gen.c: No such file or directory
> > realpath: objtool.c: No such file or directory
> > ...
>
> Care to send a patch for this?
hi Greg, yes i do, thank you!
prev parent reply other threads:[~2020-08-09 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 20:28 realpath "No such file or directory" warnings when building Rustam Kovhaev
2020-08-09 7:16 ` Greg Kroah-Hartman
2020-08-09 21:00 ` Rustam Kovhaev [this message]
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=20200809210056.GA1344537@thinkpad \
--to=rkovhaev@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=xujialu@vimux.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.