>
> OK. Thanks and here are replies:
>
> 1. Yes, I know but it seems that gtags uses sort utility internally? See
> that sort are making lots of temp files while gtags is doing parsing.
>
> 2. It seems it's 2GB issue.
> -rw-------  1 kit kit  895279104 Jun 15 16:19 GPATH
> -rw-------  1 kit kit          0 Jun 15 15:54 GRTAGS
> -rw-------  1 kit kit 2147483647 Jun 15 16:21 GTAGS
>
> 3. sqlite. Is that because it could have tag file bigger than 2GB? If use
> sqlite, is it going be slower than using normal tag db?
>
>
> Many thanks,
> Kit
> ------
> Sorry for a terse reply or typo as sent from a mobile.
>
> 2016-06-16 0:34 GMT+01:00 Shigio YAMAGUCHI <[email protected]>:
>
>> > No since as said in the mail, /usr/bin/sort failed during building tags
>> > becuase disk was full and no more space in /tmp to create temp files.
>> > So increased a partition and no such error. Great.
>>
>> Gtags makes tag files in the current directory not in /tmp.
>> You need space in the file system which includes the current directory.
>>
>> By the way, could you please show me the file size of tag files?
>>
>> $ ls -l G*
>>
>> > Is this Answer helpful to try?
>>
>> Of course.
>>
>> There is another workaround worth trying.
>> You can use sqlite3 library to make tag files.
>>
>> $ ./configure --with-sqlite3
>> (build & install)
>> $ gtags --sqlite3
>>
>> This can afford to have PAGESIZE * 2147483646 bytes data.
>> if PAGESIZE == 8192 then maximum file size is 17592186028032 (17T).
>>
>> Regards,
>> Shigio
>>
>>
>> 2016-06-16 8:03 GMT+09:00 Park Kit <[email protected]>:
>>
>>> Hi,
>>>
>>> Thanks for a reply.
>>>
>>> No since as said in the mail, /usr/bin/sort failed during building tags
>>> becuase disk was full and no more space in /tmp to create temp files. So
>>> increased a partition and no such error. Great.
>>>
>>> However, see that error this time even if there is plenty space to use.
>>> Wonder what that error means.
>>>
>>> Is this Answer helpful to try?
>>>
>>>
>>> ----------------------------------------------------------------------------
>>> Q4. I'm using GNU system. In a large project, gtags fails in making tags
>>>     like follows:
>>>
>>>     $ gtags
>>>     gtags: cannot write to database.
>>>     $ _
>>>
>>>     File system is not full. It seems that gtags cannot make a file over
>>> 2GB.
>>>     Any solution?
>>>
>>> A4. If your GNU system supports 64-bit file offset then please try the
>>>     following configuration.
>>>
>>>     $ ./configure CFLAGS='-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64'
>>>
>>>
>>> Many thanks,
>>> Kit
>>> ------
>>> Sorry for a terse reply or typo as sent from a mobile.
>>>
>>> 2016-06-15 23:40 GMT+01:00 Shigio YAMAGUCHI <[email protected]>:
>>>
>>>> Hi,
>>>> Isn't the filesystem full?
>>>> Would you please try this?
>>>>
>>>> $ df
>>>>
>>>> Regards,
>>>> Shigio
>>>>
>>>>
>>>> 2016-06-16 0:40 GMT+09:00 Park Kit <[email protected]>:
>>>>
>>>>> Hello,
>>>>>
>>>>> I am having a problem of building tag db and it seems that there is a
>>>>> certain limit on the size of source tree. When run gtags command on
>>>>> the full tree, gets an error:
>>>>>
>>>>> gtags: dbop_put failed.
>>>>>
>>>>> Initially, suffered "not enough space" since sort utility uses creates
>>>>> temp files on /tmp so increased a partition to cope with this.
>>>>>
>>>>> Now gets the above error. Run it on the sub directory which has less
>>>>> files, works okay and no error.
>>>>>
>>>>> Does gtags have any limit on the size of source tree?
>>>>>
>>>>> Many thanks,
>>>>> Kit
>>>>> ------
>>>>> Sorry for a terse reply or typo as sent from a mobile.
>>>>>
>>>>> _______________________________________________
>>>>> Bug-global mailing list
>>>>> [email protected]
>>>>> https://lists.gnu.org/mailman/listinfo/bug-global
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Shigio YAMAGUCHI <[email protected]>
>>>> PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3
>>>>
>>>
>>>
>>
>>
>> --
>> Shigio YAMAGUCHI <[email protected]>
>> PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3
>>
>
>
_______________________________________________
Bug-global mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-global

Reply via email to