bug-global
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gtags GRTAGS file is too small (only 16Kbytes) in global 6.3.2-6.3.4


From: Shigio YAMAGUCHI
Subject: Re: gtags GRTAGS file is too small (only 16Kbytes) in global 6.3.2-6.3.4 on CentOS 7 x86_64
Date: Tue, 24 Feb 2015 09:25:06 +0900

Hi,
If you don't use configuration file (gtags.conf or $HOME/.globalrc),
gtags always uses the built-in parser.

Regards
Shigio

2015-02-24 6:11 GMT+09:00 Anthony Jackson <address@hidden>:
On Sat, Feb 21, 2015 at 12:30 AM, Shigio YAMAGUCHI <address@hidden> wrote:
> Hi,
>> Unfortunately with 6.3.2-6.3.4 on CentOS 7 x86_64, gtags never creates
>> a GRTAGS file larger than 16K and therefore reverse lookups always
>> fail (return no output).  On CentOS 6 everything seems to be ok.
>
> The GRTAGS seems an empty file.
> Don't you use ctags parser? If so, ctags parser cannot generate GRTAGS
> records.
> You can see the parser of your using by the --debug option of gtags(1).
>
> $ gtags --debug
> ...
> File './yacc.c' is handled as follows:
>         suffix:   |.c|
>         language: |C|
>         parser:   |parser|
>         library:  |/usr/local/lib/gtags/exuberant-ctags.la| <= ctags parser
>
> Would you please check it?
>
>

Sure!, thank you for your response.  I confirmed that on CentOS 6 I'm getting:
   library: |built-in|

But on CentOS 7, I'm getting as you indicated:
   library: |/usr/local/lib/gtags/exuberant-ctags.la|

The reason I started using global is for the reference tag look ups so
ctags is definitely not the parser I want to use and apparently the
"built-in" parser is the one I want.

Is my build incorrectly configured to use the ctags parser by default
instead of the built-in parser?
How do I force the use of the built-in parser?

-A



--
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3

reply via email to

[Prev in Thread] Current Thread [Next in Thread]