public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: linux-kernel@vger.kernel.org
Subject: Problem using gtags target
Date: Mon, 08 Jul 2013 18:22:18 +0100	[thread overview]
Message-ID: <9hhtxk5nf05.fsf@arm.com> (raw)

Hi,

I am trying to use GNU global for kernel source browsing but have run
into a problem when using "gtags" target in Makefile. The index
files(GTAGS, GSYMS, GPATH, GRTAGS) don't work and on further
investigation turned out to be 16kb each in size. My command line is - 

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j5 gtags

On some digging, I traced the relevant code to scripts/tags.sh which
produces reasonably sized indices (modulo some  missing environment
variables) when run as - 

./scripts/tags.sh gtags

I used the following patch

diff --git a/scripts/tags.sh b/scripts/tags.sh
index 74f02e4..59b24ee 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -143,7 +143,8 @@ docscope()
 
 dogtags()
 {
-   all_target_sources | gtags -i -f -
+ all_target_sources > gtags.files
+ gtags -i -f gtags.files
 }
 
 exuberant()

to check the file list being produced and it seems correct but the
indices are still broken. Yet manually running

gtags -i -f gtags.files

does seem to do the right thing.

I was wondering if anybody has faced similar issues when using gtags and
how to fix this.

Thanks,
Punit

ps: Please include me in the cc as I am not subscribed to the list.


             reply	other threads:[~2013-07-08 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 17:22 Punit Agrawal [this message]
2013-07-23 12:49 ` Problem using gtags target Michal Marek
  -- strict thread matches above, loose matches on Subject: below --
2013-07-23 14:03 Punit Agrawal

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=9hhtxk5nf05.fsf@arm.com \
    --to=punit.agrawal@arm.com \
    --cc=linux-kernel@vger.kernel.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