public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Punit Agrawal <punit.agrawal@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem using gtags target
Date: Tue, 23 Jul 2013 14:49:55 +0200	[thread overview]
Message-ID: <51EE7BF3.4020301@suse.cz> (raw)
In-Reply-To: <9hhtxk5nf05.fsf@arm.com>

On 8.7.2013 19:22, Punit Agrawal wrote:
> 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

So you have a command that fails

> 
> 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

...and a command that works. So you can start "bisecting" between these
two: Try removing -j5 or ARCH= or  CROSS_COMPILE= from the make command
line. Still failing? Add 'printenv >env.make' to the tags.sh script and
run it via make tags. Compare the env.make file with printenv output
from the shell. Try setting the variables from env.make in the shell and
see when ./scripts/tags.sh gtags starts failing.

FWIW, both your commands seem to work for me and produce a GRTAGS that
is 256MB big.

Michal

  reply	other threads:[~2013-07-23 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 17:22 Problem using gtags target Punit Agrawal
2013-07-23 12:49 ` Michal Marek [this message]
  -- 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=51EE7BF3.4020301@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    /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