I am wondering if there is a clean way to build a system without the compiler and linker stuff.
I see no point in having these around if the respective machine will only run an application (that is built elsewhere) and never be used to build anything. And most commercial unix systems were delivered in that way (if you would not explicitely order a development system.)
Nevertheless, I do build my systems from local sources, following a procedure similar to the one described in the handbook, i.e. build it all on a development machine (within a chroot, with all the proper configs applied), then dump /usr/src and /usr/obj to the destination and there do "make installworld" etc.
I tried to kick out the toolchain stuff via /etc/src.conf - this worked, I got the /usr/obj tree created and could install from it, but now I can not even remake my sendmail config in /etc/mail:
It seems the include files for
Certainly this can be fixed by twiddling with proper settings for make - but if this tends to become laboursome, then it's not worth the effort (and new surprizes may appear after every version update).
Anyway, I think such an option should exist - why would people want to build and install the development stuff onto their dedicated production arrays?
I see no point in having these around if the respective machine will only run an application (that is built elsewhere) and never be used to build anything. And most commercial unix systems were delivered in that way (if you would not explicitely order a development system.)
Nevertheless, I do build my systems from local sources, following a procedure similar to the one described in the handbook, i.e. build it all on a development machine (within a chroot, with all the proper configs applied), then dump /usr/src and /usr/obj to the destination and there do "make installworld" etc.
I tried to kick out the toolchain stuff via /etc/src.conf - this worked, I got the /usr/obj tree created and could install from it, but now I can not even remake my sendmail config in /etc/mail:
Code:
# make
sh: cc: not found
make: "/usr/share/mk/bsd.compiler.mk" line 147: Unable to determine compiler type for CC=cc. Consider setting COMPILER_TYPE.
It seems the include files for
make
want to see a compiler, even where none is needed. I am certain I will run into greater trouble when I try to do another make installworld...Certainly this can be fixed by twiddling with proper settings for make - but if this tends to become laboursome, then it's not worth the effort (and new surprizes may appear after every version update).
Anyway, I think such an option should exist - why would people want to build and install the development stuff onto their dedicated production arrays?