Subject: Re: Build error with more.
To: None <current-users@NetBSD.org>
From: Matthias Scheler <firstname.lastname@example.org>
Date: 08/03/2005 21:29:02
In article <email@example.com>,
Marcin Jessa <firstname.lastname@example.org> writes:
> I somehow feel like I should not report any bugs on compilation of
> NetBSD CURRENT since noone really responds to those email.
You get what you pay for. ;-)
> Is email@example.com the right place for this ...
Yes, it is.
> Or is just CURRENT never meant to cleanly compile due to lack of quality
> checks or maybe something else?
I compile and install NetBSD-current almost daily on my desktop at home.
I've got to fix problems occasionally but it works fine most of the time.
Remember that NetBSD-current is "bleeding edge" OpenSource software. And
users which find and report build problems and other bugs are an important
part of such a project because they actually *are* the quality testers.
If that scheme doesn't work for you I would suggest to use one of NetBSD's
> Well, either way, let's try again.
> Freshly fetched sources with the old tree removed before that
> Running './build.sh -O ../obj -T ../tools tools' went fine.
> Running './build.sh -O ../obj -T ../tools distribution' gives following errors:
> # create set lists
> cd /usr/src/distrib/sets && DESTDIR=/usr/src/../obj/destdir.i386 MACHINE=i386 MACHINE_ARCH=i386 CKSUM=/usr/src/../tools/bin/nbcksum MAKE=/usr/src/../tools/bin/nbmake MTREE=/usr/src/../tools/bin/nbmtree MKTEMP=/usr/src/../tools/bin/nbmktemp PAX=/usr/src/../tools/bin/nbpax HOST_SH=sh sh ./maketars -S -d /usr/src/../obj/destdir.i386 -N /usr/src/etc -t /usr/src/../obj/releasedir/i386/binary/sets
> postinstall-fix-obsolete ===> .
> === Removing obsolete files ===
> sh /usr/src/usr.sbin/postinstall/postinstall -s /usr/src -d /usr/src/../obj/destdir.i386/ fix obsolete
> Source directory: /usr/src
> Target directory: /usr/src/../obj/destdir.i386/
> obsolete fix:
> postinstall fixes passed: obsolete
> postinstall fixes failed:
> ========= end of 1 extra files ===========
This is most likely caused by inconsistent build options. You must either
use "-U" in both of the above "./build.sh" commands or in none of them.
Matthias Scheler http://scheler.de/~matthias/