Ruslan Ermilov said: > On Sat, Oct 16, 2004 at 12:50:55AM +1000, Warren Liddell wrote: >> Voyager# make installworld >> mkdir -p /tmp/install.9nPYzwyq >> for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find >> grep >> ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc >> zic; do >> cp `which $prog` /tmp/install.9nPYzwyq; done >> +cd /usr/FreeBSD5/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 >> MACHINE=i386 CPUTYPE= >> GROFF_BIN_PATH=/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/bin >> GROFF_FONT_PATH=/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/share/groff_font >> GROFF_TMAC_PATH=/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/share/tmac >> PATH=/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/sbin:/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/bin:/usr/obj/usr/FreeBSD5/src/i386/legacy/usr/games:/usr/obj/usr/FreeBSD5/src/i386/usr/sbin:/usr/obj/usr/FreeBSD5/src/i386/usr/bin:/usr/obj/usr/FreeBSD5/src/i386/usr/games:/tmp/install.9nPYzwyq >> make -f Makefile.inc1 reinstall >> +cd: not found >> *** Error code 127 >> >> Stop in /usr/FreeBSD5/src. >> *** Error code 1 >> >> Stop in /usr/FreeBSD5/src. >> >> =======> >> Why has it got +cd ?? >> > You're supposed to "make buildworld" before doing "make installworld". > It will build (and cause "installworld" to use) the new make binary > that understands the `+' syntax. From the new make(1) manpage: > >> A `+' causes the command to be executed even if -n is specified >> on the command line. I suspect, from your earlier message, that your build environment, although non-standard isn't setup quite right. Are you mounting the /usr/src and /usr/ports over NFS? Where are you mounting them? What command are you using to build world? I frequently build with an NFS mounted /usr/src and /usr/ports. From your previous post it looks like you are using somewhat different paths, which although might not be a problem, it might if your object directory is different and you aren't using it in all the commands. If the machine is too small to hold the src and ports trees, is it large enough to hold /usr/obj? I would suggest the following. On your 'big' host, export a directory to use as /usr/ports, another as /usr/src, and if needed another as /usr/obj. On the 'small' host, NFS mount those directories to /usr/src, /usr/ports and /usr/obj. Then you can build and install just as if they weren't NFS mounted, which makes it somewhat easier to not forget to set make variables. When you reboot though, you won't be able to do the 'installworld' from single user unless you bring up your networking components and NFS mounts first. -- Ryan Sommers ryans_at_gamersimpact.comReceived on Fri Oct 15 2004 - 13:54:38 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:17 UTC