2002-12-21 15:49:34 +03:00
|
|
|
# $NetBSD: Makefile,v 1.182 2002/12/21 12:49:34 lukem Exp $
|
2000-02-23 20:46:11 +03:00
|
|
|
# from: @(#)Makefile 5.20 (Berkeley) 6/12/93
|
|
|
|
|
2000-06-23 10:01:10 +04:00
|
|
|
.include <bsd.own.mk>
|
|
|
|
|
2000-12-17 06:06:53 +03:00
|
|
|
SUBDIR= ac accton altq amd apm apmd arp bad144 bind bootp catman \
|
2001-12-15 06:23:11 +03:00
|
|
|
chown chroot chrtbl cnwctl config cron dev_mkdb \
|
2000-03-10 08:51:56 +03:00
|
|
|
dhcp diskpart dumpfs dumplfs edquota eeprom \
|
2002-06-09 23:31:43 +04:00
|
|
|
envstat eshconfig etcupdate grfconfig \
|
2002-04-05 02:07:35 +04:00
|
|
|
grfinfo gspa hilinfo ifwatchd inetd installboot \
|
|
|
|
iopctl iostat ipf irdaattach isdn iteconfig \
|
2002-10-01 07:50:07 +04:00
|
|
|
kgmon kvm_mkdb lastlogin link lpr mailwrapper makefs \
|
|
|
|
mdconfig memswitch mlxctl mopd mountd moused mscdlabel \
|
|
|
|
mtree ndbootd netgroup_mkdb nfsd ntp pcictl pkg_install pppd \
|
2002-09-02 00:32:43 +04:00
|
|
|
pstat pwd_mkdb quot quotacheck quotaon rarpd rbootd rdate \
|
2000-02-23 20:46:11 +03:00
|
|
|
repquota rmt rpc.bootparamd rpc.lockd rpc.pcnfsd \
|
Split the notion of building Hesiod, Kerberos, S/key, and YP
infrastructure and using that infrastructure in programs.
* MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building
of the infratsructure (libraries, support programs, etc.)
* USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control
building of support for using the corresponding API
in various libraries/programs that can use it.
As discussed on tech-toolchain.
2002-03-22 21:10:19 +03:00
|
|
|
rpc.statd rpcbind rwhod sa screenblank sesd \
|
2002-12-21 15:49:34 +03:00
|
|
|
sliplogin slstats spray sunlabel sup sushi syslogd tadpolectl tcpdchk \
|
2002-08-27 18:12:09 +04:00
|
|
|
tcpdmatch tcpdump timed tpctl traceroute trpt trsp unlink \
|
2000-02-23 20:46:11 +03:00
|
|
|
usbdevs user videomode vipw vnconfig wiconfig wsconscfg \
|
2002-06-27 03:13:04 +04:00
|
|
|
wsfontload wsmoused wsmuxctl zdump zic
|
Split the notion of building Hesiod, Kerberos, S/key, and YP
infrastructure and using that infrastructure in programs.
* MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building
of the infratsructure (libraries, support programs, etc.)
* USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control
building of support for using the corresponding API
in various libraries/programs that can use it.
As discussed on tech-toolchain.
2002-03-22 21:10:19 +03:00
|
|
|
|
|
|
|
.if (${MKKERBEROS} != "no")
|
|
|
|
SUBDIR+= hprop kadmin kdc kstash ktutil
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if (${MKYP} != "no")
|
|
|
|
SUBDIR+= rpc.yppasswdd ypbind yppoll ypserv ypset
|
|
|
|
.endif
|
2000-02-23 20:46:11 +03:00
|
|
|
|
* Eliminate the USE_NEW_TOOLCHAIN variable. Instead, split it into
two variables:
TOOLCHAIN_MISSING -- set to "yes" on platforms for which there is
no working in-tree toolchain (hppa, ns32k, sh5, x86_64).
EXTERNAL_TOOLCHAIN -- if defined by the user, points to the root of
an external toolchain (e.g. /usr/local/gnu). This enables the cross-build
framework even for TOOLCHAIN_MISSING platforms.
If TOOLCHAIN_MISSING is set to "yes", MKGDB, MKBFD, and MKGCC are all
unconditionally set to "no", since the bits are not there to build.
If EXTERNAL_TOOLCHAIN is set, MKGCC is unconditionally set to "no",
since the external toolchain's compiler is not in-sync with the
in-tree compiler support components (e.g. libgcc).
* Set MACHINE_CPU much earlier in bsd.own.mk, so that more tests in
that file can use it.
2002-09-18 03:18:25 +04:00
|
|
|
.if ${TOOLCHAIN_MISSING} == "yes"
|
2001-12-18 00:22:51 +03:00
|
|
|
SUBDIR+= mdsetimage
|
2001-12-09 03:49:09 +03:00
|
|
|
.endif
|
|
|
|
|
2000-02-23 20:46:11 +03:00
|
|
|
# IPv6
|
2001-06-03 10:09:10 +04:00
|
|
|
SUBDIR+=faithd ifmcstat mld6query ndp \
|
2000-06-13 19:15:21 +04:00
|
|
|
rip6query route6d rtadvd traceroute6 rtsold
|
2000-02-23 20:46:11 +03:00
|
|
|
|
|
|
|
# ATM PVC
|
|
|
|
SUBDIR+=pvcsif pvctxctl
|
|
|
|
|
2000-06-23 10:01:10 +04:00
|
|
|
.if (${MKCRYPTO} != "no")
|
Split the notion of building Hesiod, Kerberos, S/key, and YP
infrastructure and using that infrastructure in programs.
* MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building
of the infratsructure (libraries, support programs, etc.)
* USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control
building of support for using the corresponding API
in various libraries/programs that can use it.
As discussed on tech-toolchain.
2002-03-22 21:10:19 +03:00
|
|
|
SUBDIR+= racoon
|
2000-06-23 10:01:10 +04:00
|
|
|
.endif
|
1999-07-13 02:11:37 +04:00
|
|
|
|
1993-03-21 12:45:37 +03:00
|
|
|
.include <bsd.subdir.mk>
|