From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Make cscope fails for me now as of lastest commits on Linus's tree
Date: Sun, 18 Jan 2015 17:14:37 -0500 [thread overview]
Message-ID: <55332.1421619277@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 17 Jan 2015 23:28:18 -0500." <54BB3662.60203@gmail.com>
On Sat, 17 Jan 2015 23:28:18 -0500, nick said:
> Greetings Kernel Developers,
> After pulling the latest kernel commits for Linus???s tree, I am
> getting a build failure with make cscope. Below is the error
> messages.
> find: unknown predicate `--cc'
> I am unsure of why I am getting this and if this is a bug or an issue
> with my machine.
Obvious first thing to do is 'make -v cscope' and see what the entire command
line that's failing is. I'm fairly sure that you've managed to mess up your
source tree or build environment somehow, because:
[/usr/src/linux-next] find [a-z]* -type f | xargs grep -e "--cc"
scripts/get_maintainer.pl: Using "--roles" or "--rolestats" with git send-email --cc-cmd or any
[/usr/src/linux-next]
There's only one occurrence of "--cc" in the current source tree, and it's not
relevant as it's part of a longer string.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150118/acf936f6/attachment.bin
next prev parent reply other threads:[~2015-01-18 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 4:28 Make cscope fails for me now as of lastest commits on Linus's tree nick
2015-01-18 22:14 ` Valdis.Kletnieks at vt.edu [this message]
2015-01-19 4:12 ` nick
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=55332.1421619277@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).