Subject: Re: cap_mkdb creating empty db
To: None <current-users@netbsd.org>
From: Christos Zoulas <christos@tac.gw.com>
List: current-users
Date: 04/13/2005 00:50:45
In article <20050412232716.GA3221@moray.salmi.ch>,
Jukka Salmi  <j+nbsd@2005.salmi.ch> wrote:
>Jukka Salmi --> current-users (2005-04-12 22:36:07 +0200):
>> on a current i386 system, cap_mkdb creates an empty db if no output
>> filename (-f option) is specified (or if it's equal to the first input
>> filename):
>> 
>> 
>> $ cp /usr/share/misc/termcap .
>> $ cap_mkdb -v termcap
>> cap_mkdb: 0 capability records
>> $ rm termcap.db
>> $ cap_mkdb -v -f out termcap
>> [...]
>> cap_mkdb: 1032 capability records
>> 
>> The same commands on a netbsd-2 system:
>> 
>> $ cp /usr/share/misc/termcap .
>> $ cap_mkdb -v termcap
>> [...]
>> cap_mkdb: 1032 capability records
>> $ rm termcap.db
>> $ cap_mkdb -v -f out termcap 
>> [...]
>> cap_mkdb: 1032 capability records
>> 
>> 
>> Is this a bug, or am I missing something?
>
>Hmm, using a netbsd-2 libc seems to make it work:
>
>$ LD_LIBRARY_PATH=/opt/nbsd/2/lib cap_mkdb -v termcap
>[...]
>cap_mkdb: 1032 capability records
>
>
>Any hints?

I just fixed this.

christos