Error doing 'make installworld'

[BSD]

On Sat, Jul 19, 2003 at 03:21:27PM +0200, Juan Jos? S?nchez Mesa wrote:
> Hi!
> 
> (sorry for my bad english)
> 
> After an upgrade to 4.8-RELEASE from 4.7-RELEASE (using cvsup), when I do 
> the 'make installworld', I got this error:
> 
> --------------------------------------------------------------
> >>> Installing everything..
> --------------------------------------------------------------
> cd /usr/src; make -f Makefile.inc1 install
> ===> share/info
> ===> include
> creating osreldate.h from newvers.sh
> setvar PARAMFILE /usr/src/include/../sys/sys/param.h;  . 
> /usr/src/include/../sys/conf/newvers.sh;                echo "$COPYRIGHT" > 
> osreldate.h;                         echo "#ifdef _KERNEL" >> 
> osreldate.h;                   echo '#error "osreldate.h must not be used 
> in the kernel, use sys/param.h"' >> osreldate.h;  echo "#else" >> 
> osreldate.h;                                 echo \#'undef 
> __FreeBSD_version' >> osreldate.h;        echo \#'define __FreeBSD_version' 
> $RELDATE >> osreldate.h;  echo "#endif" >> osreldate.h
> touch: not found
> *** Error code 127
> 
> Stop in /usr/src/include.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> gameserver1#
> 
> 
> The kernel compilation was ok, and the 'make buildworld' too. But this step 
> is wrong. Note the 'touch: not found' line, but 'touch' is installed and 
> working. This step is done is single user mode.
> 
> This server is a new installation. First installed from a CD with 
> 4.7-RELEASE and next upgraded to 4.8-RELEASE using cvsup.
> 
> Output from 'uname -a':
> 
> gameserver1# uname -a
> FreeBSD gameserver1.dobleJ.net 4.8-RELEASE FreeBSD 4.8-RELEASE #0: Wed Jul 
> 16 23:22:18 CEST 
> 2003     juanjo at gameserver1.dobleJ.net:/usr/obj/usr/src/sys/GAMESERVER1  
> i386
> gameserver1#
> 
> 
> Any ideas ?

Check your system time/date. It will probably show that it is incorrect.
Correct it, then try your upgrade again, it should go through.