On Wed, Sep 13, 2006 at 10:20:39AM +0200, [EMAIL PROTECTED] wrote:
> Ruslan Ermilov wrote:
>
> >On Tue, Sep 12, 2006 at 04:52:32PM +0200, [EMAIL PROTECTED] wrote:
> >
> >
> >>Hi list
> >>
> >>I'm upgrading 5.4 p18 to 6.1 p6.
> >>
> >>here's my tag: RELENG_6_1
> >>
> >>I did:
> >>make update
> >>make cleanworld
> >>make buildworld
> >>
> >>which gives following issue:
> >>
> >>cap_mkdb: illegal option -i
> >>
> >>It seems a known problem on netbsd during buildworld compilation. here's
> >>the solution I'm tring:
> >>
> >>cd /usr/src/usr.bin/cap_mkdb
> >>make clean
> >>make
> >>make install
> >>
> >>and I'm building world again.
> >>
> >>is that a known problem on freebsd?
> >>
> >>
> >>
> >This shouldn't happen. The buildworld target detects the current
> >version of your system, and bootstraps cap_mkdb if necessary:
> >
> >: .if ${BOOTSTRAPPING} < 600015
> >: _cap_mkdb= usr.bin/cap_mkdb
> >: .endif
> >
> >BOOTSTRAPPING is defined as follows:
> >
> >: .if !defined(OSRELDATE)
> >: .if exists(/usr/include/osreldate.h)
> >: OSRELDATE!= awk '/^\#define[[:space:]]*__FreeBSD_version/ { print
> >$$3 }' \
> >: /usr/include/osreldate.h
> >: .else
> >: OSRELDATE= 0
> >: .endif
> >
> >That is, it's the value of __FreeBSD_version as defined in
> >/usr/include/osreldate.h. If your /usr/include/osreldate.h
> >is lying about the current version, e.g. if you accidentally
> >installed the new headers, then you can force it to zero,
> >such as:
> >
> > make buildworld OSRELDATE=0
> >
> >
> >Cheers,
> >
> >
> I'm pretty sure about what's happing
>
> i'd propably built my world twice...or something like that. anyway,
> building
>
> cap_mkdb before the world resolved the issue.
>
But that's what buildworld already does (when it detects the need
to do so). My point was to make it clear. :-)Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer
pgpQTXfDuIF8I.pgp
Description: PGP signature
