make installworld failed

Thomas Hoffmann trh411 at
Tue Apr 15 16:38:23 UTC 2014

On Tue, Apr 15, 2014 at 12:34 AM, jungleboogie0 <jungleboogie0 at>wrote:

> I build 10 stable generic. Would this work with 10-stable as opposed
> to 11 current?
> Currently my procedure is:
> 0.# cd /usr/src && svn update
> 1.# make -j `sysctl -n hw.ncpu` buildworld
> 2.# make -j `sysctl -n hw.ncpu` buildkernel
> 3.# make installkernel
> 4.# reboot
> 5.# cd /usr/src
> 6.# mergemaster -p
> 7.# make installworld
> 8.# mergemaster -iUF
> 9.# yes | make delete-old
> 10.# yes | make delete-old-libs
> 11.# cd /usr/obj && chflags -R noschg * && rm -rf *
> 12.# reboot
> and my system is also a tortoise. You recommend I insert your steps
> directly after the update?
> do you recommend any other changes to my procedure above? My builds
> generally also take
> 2-3 hours also.

Well, it depends on how often you build.

I build a new -CURRENT almost every night. For the first build of each
month I do a full 'buildworld'. For every 'buildworld' after that I use
NO_CLEAN since I'm pulling in a relatively small amount of updates.
Depending on the updates, I can complete a 'buildworld' in 15-30 minutes
using NO_CLEAN, whereas a full 'buildworld' takes 2-21/2 hours. So doing a
'buildworld' with NO_CLEAN makes sense for me given my build frequency.

However, if you are building only say once a month or less, then I would
recommend a full 'buildworld' every time since you will be pulling in a
fairly large number of updates.

In your #1, did you mean -j4? -j4 is what the Handbook recommends for most


More information about the freebsd-questions mailing list