2013-12-06 12:04:52 +01:00
|
|
|
# $NetBSD: bsd.own.mk,v 1.755 2013/10/29 16:11:46 joerg Exp $
|
2010-02-16 15:41:33 +01:00
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# This needs to be before bsd.init.mk
|
|
|
|
.if defined(BSD_MK_COMPAT_FILE)
|
|
|
|
.include <${BSD_MK_COMPAT_FILE}>
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if !defined(_BSD_OWN_MK_)
|
|
|
|
_BSD_OWN_MK_=1
|
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
.if defined(__MINIX)
|
2010-02-16 15:41:33 +01:00
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
# Some Minix deviations from NetBSD
|
|
|
|
LDSTATIC?= -static
|
|
|
|
MKDYNAMICROOT?= no
|
2013-04-24 18:57:59 +02:00
|
|
|
NO_LIBGOMP?= yes
|
2012-11-01 22:55:12 +01:00
|
|
|
|
|
|
|
BINMODE?= 755
|
|
|
|
NONBINMODE?= 644
|
|
|
|
MANDIR?= /usr/man
|
|
|
|
BINGRP?= operator
|
|
|
|
MANGRP?= operator
|
|
|
|
INFOGRP?= operator
|
|
|
|
DOCGRP?= operator
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
MKKYUA?= yes
|
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
MKGCC?= no
|
2013-04-24 18:57:59 +02:00
|
|
|
MKGCCCMDS?= no
|
2013-12-06 12:04:52 +01:00
|
|
|
MKLIBSTDCXX?= no
|
2013-04-17 13:01:55 +02:00
|
|
|
MKPROFILE?= no
|
2013-02-26 09:24:42 +01:00
|
|
|
MKSLJIT?= no
|
2012-11-01 22:55:12 +01:00
|
|
|
|
2013-04-17 13:01:55 +02:00
|
|
|
#MINIX-specific variables
|
|
|
|
MKCOVERAGE?= no
|
|
|
|
|
|
|
|
# LSC MINIX does not support these features ATM.
|
|
|
|
USE_FORT:= no
|
|
|
|
USE_SSP:= no
|
|
|
|
MKCRYPTO:= no
|
|
|
|
MKGDB:= no
|
|
|
|
MKGROFF:= no
|
|
|
|
MKHESIOD:= no
|
|
|
|
MKHTML:= no
|
|
|
|
MKINET6:= no
|
|
|
|
MKIPFILTER:= no
|
|
|
|
MKISCSI:= no
|
|
|
|
MKKERBEROS:= no
|
|
|
|
MKKMOD:= no
|
|
|
|
MKLDAP:= no
|
|
|
|
MKLINT:= no
|
|
|
|
MKLVM:= no
|
|
|
|
MKMDNS:= no
|
|
|
|
MKNLS:= no
|
|
|
|
MKNPF:= no
|
|
|
|
MKPAM:= no
|
|
|
|
MKPF:= no
|
|
|
|
MKPOSTFIX:= no
|
|
|
|
MKRUMP:= no
|
|
|
|
MKSKEY:= no
|
|
|
|
MKYP:= no
|
|
|
|
|
2010-09-15 16:09:52 +02:00
|
|
|
.ifdef CONFIG_SMP
|
|
|
|
SMP_FLAGS += -DCONFIG_SMP
|
|
|
|
.ifdef CONFIG_MAX_CPUS
|
|
|
|
SMP_FLAGS += -DCONFIG_MAX_CPUS=${CONFIG_MAX_CPUS}
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
2011-08-05 13:59:44 +02:00
|
|
|
CPPFLAGS+= ${SMP_FLAGS}
|
2010-09-15 16:09:52 +02:00
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
__uname_s!= uname -s
|
|
|
|
.if ${__uname_s:Uunknown} == "Minix"
|
|
|
|
USETOOLS?= never
|
2013-06-11 21:08:05 +02:00
|
|
|
. if ${USETOOLS:Uno} != "yes"
|
2013-12-06 12:04:52 +01:00
|
|
|
# LSC: We have to use a temporary variable, as some test are done simply on the
|
|
|
|
# definition (ifdef) of it.
|
2013-06-11 21:08:05 +02:00
|
|
|
. if ${_HAVE_LLVM:U} == ""
|
|
|
|
_HAVE_LLVM!= (exec 2>&1; clang --version || echo "")
|
|
|
|
_HAVE_LLVM:= ${_HAVE_LLVM:M[0-9]\.[0-9]}
|
|
|
|
. if ${_HAVE_LLVM} != ""
|
|
|
|
HAVE_LLVM?= ${_HAVE_LLVM}
|
|
|
|
. endif
|
|
|
|
. endif # ${_HAVE_LLVM:U} == ""
|
|
|
|
|
|
|
|
. if ${_HAVE_GOLD:U} == ""
|
|
|
|
_HAVE_GOLD!= (exec 2>&1; ld --version || echo "")
|
|
|
|
_GOLD_MATCH:=${_HAVE_GOLD:Mgold}
|
|
|
|
_HAVE_GOLD:= ${_HAVE_GOLD:M[0-9]\.[0-9][0-9]}
|
|
|
|
. if ${_GOLD_MATCH} != "" && ${_HAVE_GOLD} != ""
|
|
|
|
HAVE_GOLD?= ${_HAVE_GOLD}
|
|
|
|
CFLAGS+= -DHAVE_GOLD=${_HAVE_GOLD}
|
|
|
|
AFLAGS+= -DHAVE_GOLD=${_HAVE_GOLD}
|
2013-06-17 16:51:49 +02:00
|
|
|
. else
|
|
|
|
MKBITCODE:=no
|
2013-06-11 21:08:05 +02:00
|
|
|
. endif
|
|
|
|
. endif # ${_HAVE_GOLD:U} == ""
|
2013-04-17 13:01:55 +02:00
|
|
|
|
|
|
|
# If DESTDIR was specified, and we are not using the tools, then make sure to
|
|
|
|
# build out-of-tree and to refer only DESTDIR for target binaries
|
|
|
|
# The case when using tools is already handled below.
|
|
|
|
. if ${DESTDIR:U} != ""
|
|
|
|
CPPFLAGS+= --sysroot=${DESTDIR}
|
|
|
|
LDFLAGS+= --sysroot=${DESTDIR}
|
|
|
|
. if defined(HAVE_LLVM)
|
|
|
|
LDFLAGS+= -L${DESTDIR}/usr/lib
|
|
|
|
. endif
|
|
|
|
. endif # ${DESTDIR:U} != ""
|
2013-12-06 12:04:52 +01:00
|
|
|
|
|
|
|
MKTOOLS?=no
|
2013-06-11 21:08:05 +02:00
|
|
|
. endif # ${USETOOLS:Uno} != "yes"
|
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
. if !defined(HOSTPROG) && !defined(HOSTLIB)
|
|
|
|
# LSC FIXME: Override MACHINE as the native minix host make command will set
|
|
|
|
# it to i686.
|
|
|
|
. if ${MACHINE_ARCH} == "i386"
|
2013-06-11 21:08:05 +02:00
|
|
|
MACHINE:= i386
|
2012-11-01 22:55:12 +01:00
|
|
|
. endif
|
2013-12-06 12:04:52 +01:00
|
|
|
# LSC FIXME: On a native ARM system MACHINE_ARCH is earmv7 instead of earm...
|
|
|
|
. if !empty(${MACHINE_ARCH:Mearm*})
|
|
|
|
MACHINE_ARCH:= earm
|
|
|
|
. endif
|
2012-11-01 22:55:12 +01:00
|
|
|
. endif # !defined(HOSTPROG) && !defined(HOSTLIB)
|
|
|
|
.endif # __uname_s == "Minix"
|
2013-06-11 21:08:05 +02:00
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${MKKYUA:Uno} == "yes" || ${MKATF:Uyes} == "yes"
|
|
|
|
. if ${MKLIBCXX:Uno} == "no" && ${HAVE_GCC:Dyes} != "yes"
|
|
|
|
# No libc++ available, so we have to fallback on libstdc++.
|
|
|
|
# This implies that the compiler is GCC on a native system, or we are building
|
|
|
|
# GCC.
|
|
|
|
# If HAVE_GCC is not defined, then it is a crossbuild, and we have to build
|
|
|
|
# LIBSTDC++, otherwise we will simply use the system one.
|
|
|
|
MKLIBSTDCXX:= yes # required for Kyua / ATF
|
|
|
|
. endif # ${MKLIBCXX:Uno} == "no" && ${HAVE_GCC:Dyes} != "yes"
|
|
|
|
|
|
|
|
# If we need LIBSTDC++, then we are using the in-tree GCC.
|
|
|
|
. if ${MKLIBSTDCXX} == "yes"
|
|
|
|
CXXFLAGS+= -I${DESTDIR}/usr/include/g++
|
|
|
|
MKGCCCMDS:= yes
|
|
|
|
. endif # ${MKLIBSTDCXX} == "yes"
|
|
|
|
|
|
|
|
. if ${HAVE_GCC:Dyes} == "yes" && ${MKLIBCXX:Uno} != "yes"
|
|
|
|
# Specify the C++ system header for libstdc++
|
|
|
|
CXXFLAGS+= -I/usr/include/g++
|
|
|
|
. endif # ${HAVE_GCC:Dyes} == "yes" && ${MKLIBCXX:Uno} != "yes"
|
|
|
|
.endif # ${MKKYUA:Uno} == "yes" || ${MKATF:Uyes} == "yes"
|
|
|
|
|
|
|
|
# MKGCCCMDS == yes implies MKGCC == yes
|
|
|
|
.if ${MKGCCCMDS} == "yes"
|
|
|
|
MKGCC:= yes
|
|
|
|
MKBINUTILS?= yes # We are installing GCC, so trigger binutils.
|
|
|
|
.endif # ${MKGCCCMDS} == "yes"
|
|
|
|
|
|
|
|
# The default value of MKBINUTILS cannot be set before the previous test.
|
|
|
|
MKBINUTILS?= no
|
|
|
|
|
|
|
|
.if ${MKGCC} == "yes"
|
|
|
|
HAVE_GCC:= 45 # The in-tree gcc version is 4.5
|
|
|
|
.endif # ${MKGCC} == "yes"
|
|
|
|
|
2013-06-11 21:08:05 +02:00
|
|
|
#
|
|
|
|
# linker script files that have to be specified explicitely for the gold linker
|
|
|
|
#
|
|
|
|
|
|
|
|
LDS_PATH= ${NETBSDSRCDIR}/external/gpl3/binutils/ldscripts
|
|
|
|
LDS_STATIC_BIN= ${LDS_PATH}/elf_${MACHINE_ARCH}_minix.xc
|
|
|
|
LDS_DYNAMIC_BIN= ${LDS_PATH}/elf_${MACHINE_ARCH}_minix.xc
|
|
|
|
LDS_RELOC= ${LDS_PATH}/elf_${MACHINE_ARCH}_minix.xr
|
|
|
|
LDS_SHARED_LIB= ${LDS_PATH}/elf_${MACHINE_ARCH}_minix.xsc
|
|
|
|
LDS_N= ${LDS_PATH}/elf_${MACHINE_ARCH}_minix.xbn
|
2013-04-24 18:57:59 +02:00
|
|
|
|
|
|
|
#LSC FIXME: Needed by clang for now
|
|
|
|
.if ${MACHINE_ARCH} == "i386"
|
|
|
|
CPUFLAGS+= -march=i586
|
|
|
|
.endif
|
2013-04-03 00:42:17 +02:00
|
|
|
.endif # defined(__MINIX)
|
2012-11-01 22:55:12 +01:00
|
|
|
|
|
|
|
MAKECONF?= /etc/mk.conf
|
2010-02-16 15:41:33 +01:00
|
|
|
.-include "${MAKECONF}"
|
|
|
|
|
|
|
|
#
|
|
|
|
# CPU model, derived from MACHINE_ARCH
|
|
|
|
#
|
2013-12-06 12:04:52 +01:00
|
|
|
MACHINE_CPU= ${MACHINE_ARCH:C/mipse[bl]/mips/:C/mips64e[bl]/mips/:C/sh3e[bl]/sh3/:S/coldfire/m68k/:S/m68000/m68k/:C/arm.*/arm/:C/earm.*/arm/:S/earm/arm/:S/powerpc64/powerpc/}
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
#
|
|
|
|
# Subdirectory used below ${RELEASEDIR} when building a release
|
|
|
|
#
|
|
|
|
RELEASEMACHINEDIR?= ${MACHINE}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Subdirectory or path component used for the following paths:
|
|
|
|
# distrib/${RELEASEMACHINE}
|
|
|
|
# distrib/notes/${RELEASEMACHINE}
|
|
|
|
# etc/etc.${RELEASEMACHINE}
|
|
|
|
# Used when building a release.
|
|
|
|
#
|
|
|
|
RELEASEMACHINE?= ${MACHINE}
|
|
|
|
|
|
|
|
#
|
|
|
|
# NEED_OWN_INSTALL_TARGET is set to "no" by pkgsrc/mk/bsd.pkg.mk to
|
|
|
|
# ensure that things defined by <bsd.own.mk> (default targets,
|
|
|
|
# INSTALL_FILE, etc.) are not conflicting with bsd.pkg.mk.
|
|
|
|
#
|
|
|
|
NEED_OWN_INSTALL_TARGET?= yes
|
|
|
|
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# This lists the platforms which do not have working in-tree toolchains. For
|
|
|
|
# the in-tree gcc toolchain, this list is empty.
|
|
|
|
#
|
|
|
|
# If some future port is not supported by the in-tree toolchain, this should
|
|
|
|
# be set to "yes" for that port only.
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
TOOLCHAIN_MISSING?= no
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#
|
|
|
|
# Platforms still using GCC 4.1
|
|
|
|
#
|
|
|
|
.if ${MKGCC:Uyes} != "no"
|
|
|
|
.if ${MACHINE_CPU} == "vax"
|
|
|
|
HAVE_GCC?= 4
|
|
|
|
.else
|
|
|
|
# Otherwise, default to GCC4.5
|
|
|
|
HAVE_GCC?= 45
|
2012-06-06 16:31:59 +02:00
|
|
|
.endif
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
|
|
|
|
.if ${MACHINE_ARCH} == "ia64"
|
|
|
|
USE_COMPILERCRTSTUFF?= yes
|
|
|
|
.else
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
USE_COMPILERCRTSTUFF?= no
|
2012-03-31 00:35:32 +02:00
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if ${MKLLVM:Uno} == "yes" && (${MACHINE_ARCH} == "i386" || ${MACHINE_ARCH} == "x86_64")
|
|
|
|
HAVE_LIBGCC?= no
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.else
|
2013-12-06 12:04:52 +01:00
|
|
|
HAVE_LIBGCC?= yes
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
HAVE_GDB?= 7
|
|
|
|
|
2013-02-26 09:24:42 +01:00
|
|
|
.if (${MACHINE_ARCH} == "alpha") || \
|
|
|
|
(${MACHINE_ARCH} == "hppa") || \
|
|
|
|
(${MACHINE_ARCH} == "ia64") || \
|
2013-12-06 12:04:52 +01:00
|
|
|
(${MACHINE_CPU} == "mips")
|
2013-02-26 09:24:42 +01:00
|
|
|
HAVE_SSP?= no
|
|
|
|
.else
|
|
|
|
HAVE_SSP?= yes
|
|
|
|
.if ${USE_FORT:Uno} != "no"
|
|
|
|
USE_SSP?= yes
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if empty(.MAKEFLAGS:tW:M*-V .OBJDIR*)
|
2010-02-16 15:41:33 +01:00
|
|
|
.if defined(MAKEOBJDIRPREFIX) || defined(MAKEOBJDIR)
|
|
|
|
PRINTOBJDIR= ${MAKE} -r -V .OBJDIR -f /dev/null xxx
|
|
|
|
.else
|
|
|
|
PRINTOBJDIR= ${MAKE} -V .OBJDIR
|
|
|
|
.endif
|
|
|
|
.else
|
2013-12-06 12:04:52 +01:00
|
|
|
PRINTOBJDIR= echo /error/bsd.own.mk/PRINTOBJDIR # avoid infinite recursion
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Determine if running in the NetBSD source tree by checking for the
|
|
|
|
# existence of build.sh and tools/ in the current or a parent directory,
|
|
|
|
# and setting _SRC_TOP_ to the result.
|
|
|
|
#
|
|
|
|
.if !defined(_SRC_TOP_) # {
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
_SRC_TOP_!= cd "${.CURDIR}"; while :; do \
|
2010-02-16 15:41:33 +01:00
|
|
|
here=`pwd`; \
|
|
|
|
[ -f build.sh ] && [ -d tools ] && { echo $$here; break; }; \
|
|
|
|
case $$here in /) echo ""; break;; esac; \
|
|
|
|
cd ..; done
|
|
|
|
|
|
|
|
.MAKEOVERRIDES+= _SRC_TOP_
|
|
|
|
|
|
|
|
.endif # }
|
|
|
|
|
|
|
|
#
|
2013-12-06 12:04:52 +01:00
|
|
|
# If _SRC_TOP_ != "", we're within the NetBSD source tree.
|
|
|
|
# * Set defaults for NETBSDSRCDIR and _SRC_TOP_OBJ_.
|
|
|
|
# * Define _NETBSD_VERSION_DEPENDS. Targets that depend on the
|
|
|
|
# NetBSD version, or on variables defined at build time, can
|
|
|
|
# declare a dependency on ${_NETBSD_VERSION_DEPENDS}.
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
.if (${_SRC_TOP_} != "") # {
|
|
|
|
|
|
|
|
NETBSDSRCDIR?= ${_SRC_TOP_}
|
|
|
|
|
|
|
|
.if !defined(_SRC_TOP_OBJ_)
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
_SRC_TOP_OBJ_!= cd "${_SRC_TOP_}" && ${PRINTOBJDIR}
|
2010-02-16 15:41:33 +01:00
|
|
|
.MAKEOVERRIDES+= _SRC_TOP_OBJ_
|
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
_NETBSD_VERSION_DEPENDS= ${_SRC_TOP_OBJ_}/params
|
|
|
|
_NETBSD_VERSION_DEPENDS+= ${NETBSDSRCDIR}/sys/sys/param.h
|
|
|
|
_NETBSD_VERSION_DEPENDS+= ${NETBSDSRCDIR}/sys/conf/newvers.sh
|
|
|
|
_NETBSD_VERSION_DEPENDS+= ${NETBSDSRCDIR}/sys/conf/osrelease.sh
|
|
|
|
${_SRC_TOP_OBJ_}/params: .NOTMAIN .OPTIONAL # created by top level "make build"
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif # _SRC_TOP_ != "" # }
|
|
|
|
|
|
|
|
|
|
|
|
.if (${_SRC_TOP_} != "") && \
|
|
|
|
(${TOOLCHAIN_MISSING} == "no" || defined(EXTERNAL_TOOLCHAIN))
|
|
|
|
USETOOLS?= yes
|
|
|
|
.endif
|
|
|
|
USETOOLS?= no
|
|
|
|
|
|
|
|
|
|
|
|
.if ${MACHINE_ARCH} == "mips" || ${MACHINE_ARCH} == "mips64" || \
|
|
|
|
${MACHINE_ARCH} == "sh3"
|
|
|
|
.BEGIN:
|
|
|
|
@echo "Must set MACHINE_ARCH to one of ${MACHINE_ARCH}eb or ${MACHINE_ARCH}el"
|
|
|
|
@false
|
|
|
|
.elif defined(REQUIRETOOLS) && \
|
|
|
|
(${TOOLCHAIN_MISSING} == "no" || defined(EXTERNAL_TOOLCHAIN)) && \
|
|
|
|
${USETOOLS} == "no"
|
|
|
|
.BEGIN:
|
|
|
|
@echo "USETOOLS=no, but this component requires a version-specific host toolchain"
|
|
|
|
@false
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Host platform information; may be overridden
|
|
|
|
#
|
|
|
|
.if !defined(HOST_OSTYPE)
|
|
|
|
_HOST_OSNAME!= uname -s
|
|
|
|
_HOST_OSREL!= uname -r
|
|
|
|
# For _HOST_ARCH, if uname -p fails, or prints "unknown", or prints
|
|
|
|
# something that does not look like an identifier, then use uname -m.
|
|
|
|
_HOST_ARCH!= uname -p 2>/dev/null
|
|
|
|
_HOST_ARCH:= ${HOST_ARCH:tW:C/.*[^-_A-Za-z0-9].*//:S/unknown//}
|
|
|
|
.if empty(_HOST_ARCH)
|
|
|
|
_HOST_ARCH!= uname -m
|
|
|
|
.endif
|
|
|
|
HOST_OSTYPE:= ${_HOST_OSNAME}-${_HOST_OSREL:C/\([^\)]*\)//g:[*]:C/ /_/g}-${_HOST_ARCH:C/\([^\)]*\)//g:[*]:C/ /_/g}
|
|
|
|
.MAKEOVERRIDES+= HOST_OSTYPE
|
|
|
|
.endif # !defined(HOST_OSTYPE)
|
|
|
|
|
|
|
|
.if ${USETOOLS} == "yes" # {
|
|
|
|
|
|
|
|
#
|
|
|
|
# Provide a default for TOOLDIR.
|
|
|
|
#
|
|
|
|
.if !defined(TOOLDIR)
|
|
|
|
TOOLDIR:= ${_SRC_TOP_OBJ_}/tooldir.${HOST_OSTYPE}
|
|
|
|
.MAKEOVERRIDES+= TOOLDIR
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# This is the prefix used for the NetBSD-sourced tools.
|
|
|
|
#
|
|
|
|
_TOOL_PREFIX?= nb
|
|
|
|
|
|
|
|
#
|
|
|
|
# If an external toolchain base is specified, use it.
|
|
|
|
#
|
|
|
|
.if defined(EXTERNAL_TOOLCHAIN) # {
|
|
|
|
AR= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-ar
|
|
|
|
AS= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-as
|
|
|
|
LD= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-ld
|
|
|
|
NM= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-nm
|
|
|
|
OBJCOPY= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-objcopy
|
|
|
|
OBJDUMP= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-objdump
|
|
|
|
RANLIB= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-ranlib
|
|
|
|
SIZE= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-size
|
|
|
|
STRIP= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-strip
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_CC.gcc= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-gcc
|
|
|
|
TOOL_CPP.gcc= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-cpp
|
|
|
|
TOOL_CXX.gcc= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-c++
|
|
|
|
TOOL_FC.gcc= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-g77
|
|
|
|
TOOL_OBJC.gcc= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-gcc
|
2013-12-06 12:04:52 +01:00
|
|
|
|
|
|
|
TOOL_CC.clang= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-clang
|
|
|
|
TOOL_CPP.clang= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-clang-cpp
|
|
|
|
TOOL_CXX.clang= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-clang++
|
|
|
|
TOOL_OBJC.clang= ${EXTERNAL_TOOLCHAIN}/bin/${MACHINE_GNU_PLATFORM}-clang
|
2010-02-16 15:41:33 +01:00
|
|
|
.else # } {
|
|
|
|
# Define default locations for common tools.
|
|
|
|
.if ${USETOOLS_BINUTILS:Uyes} == "yes" # {
|
|
|
|
AR= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-ar
|
|
|
|
AS= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-as
|
|
|
|
LD= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-ld
|
|
|
|
NM= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-nm
|
|
|
|
OBJCOPY= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-objcopy
|
|
|
|
OBJDUMP= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-objdump
|
|
|
|
RANLIB= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-ranlib
|
|
|
|
SIZE= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-size
|
|
|
|
STRIP= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-strip
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# GCC supports C, C++, Fortran and Objective C
|
|
|
|
TOOL_CC.gcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-gcc
|
|
|
|
TOOL_CPP.gcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-cpp
|
|
|
|
TOOL_CXX.gcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-c++
|
|
|
|
TOOL_FC.gcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-g77
|
|
|
|
TOOL_OBJC.gcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-gcc
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif # }
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# Clang supports C, C++ and Objective C
|
|
|
|
TOOL_CC.clang= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-clang
|
|
|
|
TOOL_CPP.clang= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-clang-cpp
|
|
|
|
TOOL_CXX.clang= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-clang++
|
|
|
|
TOOL_OBJC.clang= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-clang
|
|
|
|
|
|
|
|
# PCC supports C and Fortran
|
|
|
|
TOOL_CC.pcc= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-pcc
|
|
|
|
TOOL_CPP.pcc= ${TOOLDIR}/libexec/${MACHINE_GNU_PLATFORM}-cpp
|
|
|
|
|
|
|
|
#
|
|
|
|
# Make sure DESTDIR is set, so that builds with these tools always
|
|
|
|
# get appropriate -nostdinc, -nostdlib, etc. handling. The default is
|
|
|
|
# <empty string>, meaning start from /, the root directory.
|
|
|
|
#
|
|
|
|
DESTDIR?=
|
2010-02-16 15:41:33 +01:00
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if !defined(HOSTPROG) && !defined(HOSTLIB)
|
|
|
|
. if ${DESTDIR} != ""
|
|
|
|
CPPFLAGS+= --sysroot=${DESTDIR}
|
|
|
|
LDFLAGS+= --sysroot=${DESTDIR}
|
|
|
|
. else
|
|
|
|
CPPFLAGS+= --sysroot=/
|
|
|
|
LDFLAGS+= --sysroot=/
|
|
|
|
. endif
|
|
|
|
.endif
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif # EXTERNAL_TOOLCHAIN # }
|
|
|
|
|
|
|
|
HOST_MKDEP= ${TOOLDIR}/bin/${_TOOL_PREFIX}host-mkdep
|
2013-12-06 12:04:52 +01:00
|
|
|
HOST_MKDEPCXX= ${TOOLDIR}/bin/${_TOOL_PREFIX}host-mkdep
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
DBSYM= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-dbsym
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
ELF2AOUT= ${TOOLDIR}/bin/${_TOOL_PREFIX}m68k-elf2aout
|
2010-02-16 15:41:33 +01:00
|
|
|
ELF2ECOFF= ${TOOLDIR}/bin/${_TOOL_PREFIX}mips-elf2ecoff
|
|
|
|
INSTALL= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-install
|
|
|
|
LEX= ${TOOLDIR}/bin/${_TOOL_PREFIX}lex
|
|
|
|
LINT= CC=${CC:Q} ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-lint
|
|
|
|
LORDER= NM=${NM:Q} MKTEMP=${TOOL_MKTEMP:Q} ${TOOLDIR}/bin/${_TOOL_PREFIX}lorder
|
|
|
|
MKDEP= CC=${CC:Q} ${TOOLDIR}/bin/${_TOOL_PREFIX}mkdep
|
2013-12-06 12:04:52 +01:00
|
|
|
MKDEPCXX= CC=${CXX:Q} ${TOOLDIR}/bin/${_TOOL_PREFIX}mkdep
|
2010-02-16 15:41:33 +01:00
|
|
|
PAXCTL= ${TOOLDIR}/bin/${_TOOL_PREFIX}paxctl
|
|
|
|
TSORT= ${TOOLDIR}/bin/${_TOOL_PREFIX}tsort -q
|
|
|
|
YACC= ${TOOLDIR}/bin/${_TOOL_PREFIX}yacc
|
|
|
|
|
|
|
|
TOOL_AMIGAAOUT2BB= ${TOOLDIR}/bin/${_TOOL_PREFIX}amiga-aout2bb
|
|
|
|
TOOL_AMIGAELF2BB= ${TOOLDIR}/bin/${_TOOL_PREFIX}amiga-elf2bb
|
|
|
|
TOOL_AMIGATXLT= ${TOOLDIR}/bin/${_TOOL_PREFIX}amiga-txlt
|
|
|
|
TOOL_ASN1_COMPILE= ${TOOLDIR}/bin/${_TOOL_PREFIX}asn1_compile
|
|
|
|
TOOL_AWK= ${TOOLDIR}/bin/${_TOOL_PREFIX}awk
|
|
|
|
TOOL_CAP_MKDB= ${TOOLDIR}/bin/${_TOOL_PREFIX}cap_mkdb
|
|
|
|
TOOL_CAT= ${TOOLDIR}/bin/${_TOOL_PREFIX}cat
|
|
|
|
TOOL_CKSUM= ${TOOLDIR}/bin/${_TOOL_PREFIX}cksum
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_CLANG_TBLGEN= ${TOOLDIR}/bin/${_TOOL_PREFIX}clang-tblgen
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_COMPILE_ET= ${TOOLDIR}/bin/${_TOOL_PREFIX}compile_et
|
|
|
|
TOOL_CONFIG= ${TOOLDIR}/bin/${_TOOL_PREFIX}config
|
|
|
|
TOOL_CRUNCHGEN= MAKE=${.MAKE:Q} ${TOOLDIR}/bin/${_TOOL_PREFIX}crunchgen
|
|
|
|
TOOL_CTAGS= ${TOOLDIR}/bin/${_TOOL_PREFIX}ctags
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_CTFCONVERT= ${TOOLDIR}/bin/${_TOOL_PREFIX}ctfconvert
|
|
|
|
TOOL_CTFMERGE= ${TOOLDIR}/bin/${_TOOL_PREFIX}ctfmerge
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_DB= ${TOOLDIR}/bin/${_TOOL_PREFIX}db
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_DISKLABEL= ${TOOLDIR}/bin/nbdisklabel
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_EQN= ${TOOLDIR}/bin/${_TOOL_PREFIX}eqn
|
|
|
|
TOOL_FDISK= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-fdisk
|
|
|
|
TOOL_FGEN= ${TOOLDIR}/bin/${_TOOL_PREFIX}fgen
|
|
|
|
TOOL_GENASSYM= ${TOOLDIR}/bin/${_TOOL_PREFIX}genassym
|
|
|
|
TOOL_GENCAT= ${TOOLDIR}/bin/${_TOOL_PREFIX}gencat
|
|
|
|
TOOL_GMAKE= ${TOOLDIR}/bin/${_TOOL_PREFIX}gmake
|
|
|
|
TOOL_GREP= ${TOOLDIR}/bin/${_TOOL_PREFIX}grep
|
|
|
|
TOOL_GROFF= PATH=${TOOLDIR}/lib/groff:$${PATH} ${TOOLDIR}/bin/${_TOOL_PREFIX}groff
|
|
|
|
TOOL_HEXDUMP= ${TOOLDIR}/bin/${_TOOL_PREFIX}hexdump
|
|
|
|
TOOL_HP300MKBOOT= ${TOOLDIR}/bin/${_TOOL_PREFIX}hp300-mkboot
|
|
|
|
TOOL_HP700MKBOOT= ${TOOLDIR}/bin/${_TOOL_PREFIX}hp700-mkboot
|
|
|
|
TOOL_INDXBIB= ${TOOLDIR}/bin/${_TOOL_PREFIX}indxbib
|
|
|
|
TOOL_INSTALLBOOT= ${TOOLDIR}/bin/${_TOOL_PREFIX}installboot
|
|
|
|
TOOL_INSTALL_INFO= ${TOOLDIR}/bin/${_TOOL_PREFIX}install-info
|
|
|
|
TOOL_JOIN= ${TOOLDIR}/bin/${_TOOL_PREFIX}join
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_LLVM_TBLGEN= ${TOOLDIR}/bin/${_TOOL_PREFIX}llvm-tblgen
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_M4= ${TOOLDIR}/bin/${_TOOL_PREFIX}m4
|
|
|
|
TOOL_MACPPCFIXCOFF= ${TOOLDIR}/bin/${_TOOL_PREFIX}macppc-fixcoff
|
|
|
|
TOOL_MAKEFS= ${TOOLDIR}/bin/${_TOOL_PREFIX}makefs
|
|
|
|
TOOL_MAKEINFO= ${TOOLDIR}/bin/${_TOOL_PREFIX}makeinfo
|
|
|
|
TOOL_MAKEWHATIS= ${TOOLDIR}/bin/${_TOOL_PREFIX}makewhatis
|
|
|
|
TOOL_MANDOC_ASCII= ${TOOLDIR}/bin/${_TOOL_PREFIX}mandoc -Tascii
|
|
|
|
TOOL_MANDOC_HTML= ${TOOLDIR}/bin/${_TOOL_PREFIX}mandoc -Thtml
|
|
|
|
TOOL_MANDOC_LINT= ${TOOLDIR}/bin/${_TOOL_PREFIX}mandoc -Tlint
|
|
|
|
TOOL_MDSETIMAGE= ${TOOLDIR}/bin/${MACHINE_GNU_PLATFORM}-mdsetimage
|
|
|
|
TOOL_MENUC= MENUDEF=${TOOLDIR}/share/misc ${TOOLDIR}/bin/${_TOOL_PREFIX}menuc
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_M68KELF2AOUT= ${TOOLDIR}/bin/${_TOOL_PREFIX}m68k-elf2aout
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MIPSELF2ECOFF= ${TOOLDIR}/bin/${_TOOL_PREFIX}mips-elf2ecoff
|
|
|
|
TOOL_MKCSMAPPER= ${TOOLDIR}/bin/${_TOOL_PREFIX}mkcsmapper
|
|
|
|
TOOL_MKESDB= ${TOOLDIR}/bin/${_TOOL_PREFIX}mkesdb
|
2012-06-15 16:13:12 +02:00
|
|
|
TOOL_MKFSMFS= ${TOOLDIR}/bin/${_TOOL_PREFIX}mkfs.mfs
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MKLOCALE= ${TOOLDIR}/bin/${_TOOL_PREFIX}mklocale
|
|
|
|
TOOL_MKMAGIC= ${TOOLDIR}/bin/${_TOOL_PREFIX}file
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_MKNOD= ${TOOLDIR}/bin/${_TOOL_PREFIX}mknod
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MKTEMP= ${TOOLDIR}/bin/${_TOOL_PREFIX}mktemp
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_MKUBOOTIMAGE= ${TOOLDIR}/bin/${_TOOL_PREFIX}mkubootimage
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_ELFTOSB= ${TOOLDIR}/bin/${_TOOL_PREFIX}elftosb
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MSGC= MSGDEF=${TOOLDIR}/share/misc ${TOOLDIR}/bin/${_TOOL_PREFIX}msgc
|
|
|
|
TOOL_MTREE= ${TOOLDIR}/bin/${_TOOL_PREFIX}mtree
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_NBPERF= ${TOOLDIR}/bin/${_TOOL_PREFIX}perf
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_PAX= ${TOOLDIR}/bin/${_TOOL_PREFIX}pax
|
|
|
|
TOOL_PIC= ${TOOLDIR}/bin/${_TOOL_PREFIX}pic
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_PIGZ= ${TOOLDIR}/bin/${_TOOL_PREFIX}pigz
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_PKG_CREATE= ${TOOLDIR}/bin/${_TOOL_PREFIX}pkg_create
|
|
|
|
TOOL_POWERPCMKBOOTIMAGE=${TOOLDIR}/bin/${_TOOL_PREFIX}powerpc-mkbootimage
|
|
|
|
TOOL_PWD_MKDB= ${TOOLDIR}/bin/${_TOOL_PREFIX}pwd_mkdb
|
|
|
|
TOOL_REFER= ${TOOLDIR}/bin/${_TOOL_PREFIX}refer
|
|
|
|
TOOL_ROFF_ASCII= PATH=${TOOLDIR}/lib/groff:$${PATH} ${TOOLDIR}/bin/${_TOOL_PREFIX}nroff
|
|
|
|
TOOL_ROFF_DVI= ${TOOL_GROFF} -Tdvi
|
|
|
|
TOOL_ROFF_HTML= ${TOOL_GROFF} -Tlatin1 -mdoc2html
|
|
|
|
TOOL_ROFF_PS= ${TOOL_GROFF} -Tps
|
|
|
|
TOOL_ROFF_RAW= ${TOOL_GROFF} -Z
|
|
|
|
TOOL_RPCGEN= RPCGEN_CPP=${CPP:Q} ${TOOLDIR}/bin/${_TOOL_PREFIX}rpcgen
|
|
|
|
TOOL_SED= ${TOOLDIR}/bin/${_TOOL_PREFIX}sed
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_SLC= ${TOOLDIR}/bin/${_TOOL_PREFIX}slc
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_SOELIM= ${TOOLDIR}/bin/${_TOOL_PREFIX}soelim
|
|
|
|
TOOL_SPARKCRC= ${TOOLDIR}/bin/${_TOOL_PREFIX}sparkcrc
|
|
|
|
TOOL_STAT= ${TOOLDIR}/bin/${_TOOL_PREFIX}stat
|
|
|
|
TOOL_STRFILE= ${TOOLDIR}/bin/${_TOOL_PREFIX}strfile
|
|
|
|
TOOL_SUNLABEL= ${TOOLDIR}/bin/${_TOOL_PREFIX}sunlabel
|
|
|
|
TOOL_TBL= ${TOOLDIR}/bin/${_TOOL_PREFIX}tbl
|
2012-05-02 14:33:27 +02:00
|
|
|
TOOL_TIC= ${TOOLDIR}/bin/${_TOOL_PREFIX}tic
|
2013-10-03 18:26:21 +02:00
|
|
|
TOOL_TOPROTO= ${TOOLDIR}/bin/${_TOOL_PREFIX}toproto
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_UUDECODE= ${TOOLDIR}/bin/${_TOOL_PREFIX}uudecode
|
|
|
|
TOOL_VGRIND= ${TOOLDIR}/bin/${_TOOL_PREFIX}vgrind -f
|
|
|
|
TOOL_ZIC= ${TOOLDIR}/bin/${_TOOL_PREFIX}zic
|
|
|
|
|
|
|
|
.else # USETOOLS != yes # } {
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# Clang supports C, C++ and Objective C
|
|
|
|
TOOL_CC.clang= clang
|
|
|
|
TOOL_CPP.clang= clang-cpp
|
|
|
|
TOOL_CXX.clang= clang++
|
|
|
|
TOOL_OBJC.clang= clang
|
|
|
|
|
|
|
|
# GCC supports C, C++, Fortran and Objective C
|
|
|
|
TOOL_CC.gcc= gcc
|
|
|
|
TOOL_CPP.gcc= cpp
|
|
|
|
TOOL_CXX.gcc= c++
|
|
|
|
TOOL_FC.gcc= g77
|
|
|
|
TOOL_OBJC.gcc= gcc
|
|
|
|
|
|
|
|
# PCC supports C and Fortran
|
|
|
|
TOOL_CC.pcc= pcc
|
|
|
|
TOOL_CPP.pcc= /usr/libexec/pcpp
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_AMIGAAOUT2BB= amiga-aout2bb
|
|
|
|
TOOL_AMIGAELF2BB= amiga-elf2bb
|
|
|
|
TOOL_AMIGATXLT= amiga-txlt
|
|
|
|
TOOL_ASN1_COMPILE= asn1_compile
|
|
|
|
TOOL_AWK= awk
|
|
|
|
TOOL_CAP_MKDB= cap_mkdb
|
|
|
|
TOOL_CAT= cat
|
|
|
|
TOOL_CKSUM= cksum
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_CLANG_TBLGEN= clang-tblgen
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_COMPILE_ET= compile_et
|
|
|
|
TOOL_CONFIG= config
|
|
|
|
TOOL_CRUNCHGEN= crunchgen
|
|
|
|
TOOL_CTAGS= ctags
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_CTFCONVERT= ctfconvert
|
|
|
|
TOOL_CTFMERGE= ctfmerge
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_DB= db
|
|
|
|
TOOL_DISKLABEL= disklabel
|
|
|
|
TOOL_EQN= eqn
|
|
|
|
TOOL_FDISK= fdisk
|
|
|
|
TOOL_FGEN= fgen
|
|
|
|
TOOL_GENASSYM= genassym
|
|
|
|
TOOL_GENCAT= gencat
|
|
|
|
TOOL_GMAKE= gmake
|
|
|
|
TOOL_GREP= grep
|
|
|
|
TOOL_GROFF= groff
|
|
|
|
TOOL_HEXDUMP= hexdump
|
|
|
|
TOOL_HP300MKBOOT= hp300-mkboot
|
|
|
|
TOOL_HP700MKBOOT= hp700-mkboot
|
|
|
|
TOOL_INDXBIB= indxbib
|
|
|
|
TOOL_INSTALLBOOT= installboot
|
|
|
|
TOOL_INSTALL_INFO= install-info
|
|
|
|
TOOL_JOIN= join
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_LLVM_TBLGEN= llvm-tblgen
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_M4= m4
|
|
|
|
TOOL_MACPPCFIXCOFF= macppc-fixcoff
|
|
|
|
TOOL_MAKEFS= makefs
|
|
|
|
TOOL_MAKEINFO= makeinfo
|
2011-09-26 18:19:29 +02:00
|
|
|
TOOL_MAKEWHATIS= /usr/libexec/makewhatis
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_MANDOC_ASCII= mandoc -Tascii
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_MANDOC_HTML= mandoc -Thtml
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_MANDOC_LINT= mandoc -Tlint
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MDSETIMAGE= mdsetimage
|
|
|
|
TOOL_MENUC= menuc
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_M68KELF2AOUT= m68k-elf2aout
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MIPSELF2ECOFF= mips-elf2ecoff
|
|
|
|
TOOL_MKCSMAPPER= mkcsmapper
|
|
|
|
TOOL_MKESDB= mkesdb
|
2012-06-15 16:13:12 +02:00
|
|
|
TOOL_MKFSMFS= mkfs.mfs
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MKLOCALE= mklocale
|
|
|
|
TOOL_MKMAGIC= file
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_MKNOD= mknod
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MKTEMP= mktemp
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_MKUBOOTIMAGE= mkubootimage
|
2013-12-06 12:04:52 +01:00
|
|
|
TOOL_ELFTOSB= elftosb
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_MSGC= msgc
|
|
|
|
TOOL_MTREE= mtree
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_NBPERF= nbperf
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_PAX= pax
|
|
|
|
TOOL_PIC= pic
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TOOL_PIGZ= pigz
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_PKG_CREATE= pkg_create
|
|
|
|
TOOL_POWERPCMKBOOTIMAGE= powerpc-mkbootimage
|
|
|
|
TOOL_PWD_MKDB= pwd_mkdb
|
|
|
|
TOOL_REFER= refer
|
|
|
|
TOOL_ROFF_ASCII= nroff
|
|
|
|
TOOL_ROFF_DVI= ${TOOL_GROFF} -Tdvi
|
|
|
|
TOOL_ROFF_HTML= ${TOOL_GROFF} -Tlatin1 -mdoc2html
|
|
|
|
TOOL_ROFF_PS= ${TOOL_GROFF} -Tps
|
|
|
|
TOOL_ROFF_RAW= ${TOOL_GROFF} -Z
|
|
|
|
TOOL_RPCGEN= rpcgen
|
|
|
|
TOOL_SED= sed
|
|
|
|
TOOL_SOELIM= soelim
|
|
|
|
TOOL_SPARKCRC= sparkcrc
|
|
|
|
TOOL_STAT= stat
|
|
|
|
TOOL_STRFILE= strfile
|
|
|
|
TOOL_SUNLABEL= sunlabel
|
|
|
|
TOOL_TBL= tbl
|
2012-05-02 14:33:27 +02:00
|
|
|
TOOL_TIC= tic
|
2013-10-03 18:26:21 +02:00
|
|
|
TOOL_TOPROTO= toproto
|
2010-02-16 15:41:33 +01:00
|
|
|
TOOL_UUDECODE= uudecode
|
|
|
|
TOOL_VGRIND= vgrind -f
|
|
|
|
TOOL_ZIC= zic
|
|
|
|
|
|
|
|
.endif # USETOOLS != yes # }
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# Fallback to ensure that all variables are defined to something
|
|
|
|
TOOL_CC.false= false
|
|
|
|
TOOL_CPP.false= false
|
|
|
|
TOOL_CXX.false= false
|
|
|
|
TOOL_FC.false= false
|
|
|
|
TOOL_OBJC.false= false
|
|
|
|
|
|
|
|
AVAILABLE_COMPILER?= ${HAVE_PCC:Dpcc} ${HAVE_LLVM:Dclang} ${HAVE_GCC:Dgcc} false
|
|
|
|
|
|
|
|
.for _t in CC CPP CXX FC OBJC
|
|
|
|
ACTIVE_${_t}= ${AVAILABLE_COMPILER:@.c.@ ${ !defined(UNSUPPORTED_COMPILER.${.c.}) && defined(TOOL_${_t}.${.c.}) :? ${.c.} : }@:[1]}
|
|
|
|
SUPPORTED_${_t}=${AVAILABLE_COMPILER:Nfalse:@.c.@ ${ !defined(UNSUPPORTED_COMPILER.${.c.}) && defined(TOOL_${_t}.${.c.}) :? ${.c.} : }@}
|
|
|
|
.endfor
|
|
|
|
# make bugs prevent moving this into the .for loop
|
|
|
|
CC= ${TOOL_CC.${ACTIVE_CC}}
|
|
|
|
CPP= ${TOOL_CPP.${ACTIVE_CPP}}
|
|
|
|
CXX= ${TOOL_CXX.${ACTIVE_CXX}}
|
|
|
|
FC= ${TOOL_FC.${ACTIVE_FC}}
|
|
|
|
OBJC= ${TOOL_OBJC.${ACTIVE_OBJC}}
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
.if exists(/usr/bin/${TOOL_CTFCONVERT}) || exists(${TOOL_CTFCONVERT})
|
|
|
|
CTFCONVERT= ${TOOL_CTFCONVERT}
|
|
|
|
CTFMERGE= ${TOOL_CTFMERGE}
|
|
|
|
.endif
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# OBJCOPY flags to create a.out binaries for old firmware
|
|
|
|
# shared among src/distrib and ${MACHINE}/conf/Makefile.${MACHINE}.inc
|
|
|
|
.if ${MACHINE_CPU} == "arm"
|
|
|
|
OBJCOPY_ELF2AOUT_FLAGS?= \
|
|
|
|
-O a.out-arm-netbsd \
|
|
|
|
-R .ident \
|
|
|
|
-R .ARM.attributes \
|
|
|
|
-R .ARM.exidx \
|
2013-12-06 12:04:52 +01:00
|
|
|
-R .ARM.extab \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
-R .arm.atpcs \
|
|
|
|
-R .comment \
|
|
|
|
-R .debug_abbrev \
|
2013-12-06 12:04:52 +01:00
|
|
|
-R .debug_aranges \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
-R .debug_info \
|
|
|
|
-R .debug_line \
|
|
|
|
-R .debug_frame \
|
|
|
|
-R .debug_loc \
|
|
|
|
-R .debug_pubnames \
|
|
|
|
-R .debug_pubtypes \
|
2013-12-06 12:04:52 +01:00
|
|
|
-R .debug_str \
|
|
|
|
-R .eh_frame \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
-R .note.netbsd.ident
|
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# Targets to check if DESTDIR or RELEASEDIR is provided
|
|
|
|
#
|
|
|
|
.if !target(check_DESTDIR)
|
|
|
|
check_DESTDIR: .PHONY .NOTMAIN
|
|
|
|
.if !defined(DESTDIR)
|
|
|
|
@echo "setenv DESTDIR before doing that!"
|
|
|
|
@false
|
|
|
|
.else
|
|
|
|
@true
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if !target(check_RELEASEDIR)
|
|
|
|
check_RELEASEDIR: .PHONY .NOTMAIN
|
|
|
|
.if !defined(RELEASEDIR)
|
|
|
|
@echo "setenv RELEASEDIR before doing that!"
|
|
|
|
@false
|
|
|
|
.else
|
|
|
|
@true
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Build a dynamically linked /bin and /sbin, with the necessary shared
|
|
|
|
# libraries moved from /usr/lib to /lib and the shared linker moved
|
|
|
|
# from /usr/libexec to /lib
|
|
|
|
#
|
|
|
|
# Note that if the BINDIR is not /bin or /sbin, then we always use the
|
|
|
|
# non-DYNAMICROOT behavior (i.e. it is only enabled for programs in /bin
|
|
|
|
# and /sbin). See <bsd.shlib.mk>.
|
|
|
|
#
|
|
|
|
MKDYNAMICROOT?= yes
|
|
|
|
|
|
|
|
#
|
|
|
|
# Where the system object and source trees are kept; can be configurable
|
|
|
|
# by the user in case they want them in ~/foosrc and ~/fooobj (for example).
|
|
|
|
#
|
|
|
|
BSDSRCDIR?= /usr/src
|
|
|
|
BSDOBJDIR?= /usr/obj
|
|
|
|
NETBSDSRCDIR?= ${BSDSRCDIR}
|
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
BINGRP?= wheel
|
2010-02-16 15:41:33 +01:00
|
|
|
BINOWN?= root
|
2012-11-01 22:55:12 +01:00
|
|
|
BINMODE?= 555
|
|
|
|
NONBINMODE?= 444
|
2010-02-16 15:41:33 +01:00
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# These are here mainly because we don't want suid root in case
|
|
|
|
# a Makefile defines BINMODE.
|
|
|
|
RUMPBINGRP?= wheel
|
|
|
|
RUMPBINOWN?= root
|
|
|
|
RUMPBINMODE?= 555
|
|
|
|
RUMPNONBINMODE?=444
|
|
|
|
|
2012-11-01 22:55:12 +01:00
|
|
|
MANDIR?= /usr/share/man
|
|
|
|
MANGRP?= wheel
|
2010-02-16 15:41:33 +01:00
|
|
|
MANOWN?= root
|
|
|
|
MANMODE?= ${NONBINMODE}
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MANINSTALL?= ${_MANINSTALL}
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
INFODIR?= /usr/share/info
|
2012-11-01 22:55:12 +01:00
|
|
|
INFOGRP?= wheel
|
2010-02-16 15:41:33 +01:00
|
|
|
INFOOWN?= root
|
|
|
|
INFOMODE?= ${NONBINMODE}
|
|
|
|
|
2011-06-07 14:48:31 +02:00
|
|
|
LIBDIR?= /usr/lib
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
LINTLIBDIR?= /usr/libdata/lint
|
|
|
|
LIBGRP?= ${BINGRP}
|
|
|
|
LIBOWN?= ${BINOWN}
|
|
|
|
LIBMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
DOCDIR?= /usr/share/doc
|
|
|
|
HTMLDOCDIR?= /usr/share/doc/html
|
2012-11-01 22:55:12 +01:00
|
|
|
DOCGRP?= wheel
|
2010-02-16 15:41:33 +01:00
|
|
|
DOCOWN?= root
|
|
|
|
DOCMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
NLSDIR?= /usr/share/nls
|
|
|
|
NLSGRP?= wheel
|
|
|
|
NLSOWN?= root
|
|
|
|
NLSMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
KMODULEGRP?= wheel
|
|
|
|
KMODULEOWN?= root
|
|
|
|
KMODULEMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
LOCALEDIR?= /usr/share/locale
|
|
|
|
LOCALEGRP?= wheel
|
|
|
|
LOCALEOWN?= root
|
|
|
|
LOCALEMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
FIRMWAREDIR?= /libdata/firmware
|
|
|
|
FIRMWAREGRP?= wheel
|
|
|
|
FIRMWAREOWN?= root
|
|
|
|
FIRMWAREMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
DEBUGDIR?= /usr/libdata/debug
|
|
|
|
DEBUGGRP?= wheel
|
|
|
|
DEBUGOWN?= root
|
|
|
|
DEBUGMODE?= ${NONBINMODE}
|
|
|
|
|
|
|
|
#
|
|
|
|
# Data-driven table using make variables to control how
|
|
|
|
# toolchain-dependent targets and shared libraries are built
|
|
|
|
# for different platforms and object formats.
|
|
|
|
#
|
|
|
|
# OBJECT_FMT: currently either "ELF" or "a.out".
|
|
|
|
#
|
|
|
|
# All platforms are ELF.
|
|
|
|
#
|
2010-12-10 23:20:12 +01:00
|
|
|
OBJECT_FMT= ELF
|
2011-06-07 14:48:31 +02:00
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# If this platform's toolchain is missing, we obviously cannot build it.
|
|
|
|
#
|
|
|
|
.if ${TOOLCHAIN_MISSING} != "no"
|
|
|
|
MKBINUTILS:= no
|
|
|
|
MKGDB:= no
|
|
|
|
MKGCC:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# If we are using an external toolchain, we can still build the target's
|
|
|
|
# binutils, but we cannot build GCC's support libraries, since those are
|
|
|
|
# tightly-coupled to the version of GCC being used.
|
|
|
|
#
|
|
|
|
.if defined(EXTERNAL_TOOLCHAIN)
|
|
|
|
MKGCC:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# The m68000 port is incomplete.
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "m68000"
|
|
|
|
NOPIC= # defined
|
|
|
|
MKISCSI= no
|
|
|
|
# XXX GCC 4 outputs mcount() calling sequences that try to load values
|
|
|
|
# from over 64KB away and this fails to assemble.
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if defined(HAVE_GCC)
|
2010-02-16 15:41:33 +01:00
|
|
|
NOPROFILE= # defined
|
|
|
|
.endif
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# The ia64 port is incomplete.
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "ia64"
|
|
|
|
MKLINT= no
|
|
|
|
MKGDB= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# On the MIPS, all libs are compiled with ABIcalls (and are thus PIC),
|
|
|
|
# not just shared libraries, so don't build the _pic version.
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "mipsel" || ${MACHINE_ARCH} == "mipseb" || \
|
|
|
|
${MACHINE_ARCH} == "mips64el" || ${MACHINE_ARCH} == "mips64eb"
|
|
|
|
MKPICLIB:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# On VAX using ELF, all objects are PIC, not just shared libraries,
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# so don't build the _pic version.
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "vax"
|
|
|
|
MKPICLIB= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Location of the file that contains the major and minor numbers of the
|
|
|
|
# version of a shared library. If this file exists a shared library
|
|
|
|
# will be built by <bsd.lib.mk>.
|
|
|
|
#
|
|
|
|
SHLIB_VERSION_FILE?= ${.CURDIR}/shlib_version
|
|
|
|
|
|
|
|
#
|
|
|
|
# GNU sources and packages sometimes see architecture names differently.
|
|
|
|
#
|
2013-12-06 12:04:52 +01:00
|
|
|
GNU_ARCH.coldfire=m5407
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
GNU_ARCH.earm=arm
|
2013-12-06 12:04:52 +01:00
|
|
|
GNU_ARCH.earmhf=arm
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
GNU_ARCH.earmeb=armeb
|
2013-12-06 12:04:52 +01:00
|
|
|
GNU_ARCH.earmhfeb=armeb
|
|
|
|
GNU_ARCH.earmv4=armv4
|
|
|
|
GNU_ARCH.earmv4eb=armv4eb
|
|
|
|
GNU_ARCH.earmv5=arm
|
|
|
|
GNU_ARCH.earmv5eb=armeb
|
|
|
|
GNU_ARCH.earmv6=armv6
|
|
|
|
GNU_ARCH.earmv6hf=armv6
|
|
|
|
GNU_ARCH.earmv6eb=armv6eb
|
|
|
|
GNU_ARCH.earmv6hfeb=armv6eb
|
|
|
|
GNU_ARCH.earmv7=armv7
|
|
|
|
GNU_ARCH.earmv7hf=armv7
|
|
|
|
GNU_ARCH.earmv7eb=armv7eb
|
|
|
|
GNU_ARCH.earmv7hfeb=armv7eb
|
|
|
|
GNU_ARCH.i386=i486
|
|
|
|
GCC_CONFIG_ARCH.i386=i486
|
2010-02-16 15:41:33 +01:00
|
|
|
GCC_CONFIG_TUNE.i386=nocona
|
|
|
|
GCC_CONFIG_TUNE.x86_64=nocona
|
|
|
|
GNU_ARCH.m68000=m68010
|
|
|
|
GNU_ARCH.sh3eb=sh
|
|
|
|
GNU_ARCH.sh3el=shle
|
|
|
|
GNU_ARCH.mips64eb=mips64
|
2013-12-06 12:04:52 +01:00
|
|
|
|
|
|
|
.if defined(__MINIX)
|
|
|
|
# MINIX/arm default
|
|
|
|
GCC_CONFIG_ARCH.earm=armv7-a
|
|
|
|
|
|
|
|
# MINIX/intel default
|
|
|
|
GNU_ARCH.i386=i586
|
|
|
|
GCC_CONFIG_ARCH.i386=i586
|
|
|
|
.endif # defined(__MINIX)
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
MACHINE_GNU_ARCH=${GNU_ARCH.${MACHINE_ARCH}:U${MACHINE_ARCH}}
|
|
|
|
|
|
|
|
#
|
|
|
|
# In order to identify NetBSD to GNU packages, we sometimes need
|
|
|
|
# an "elf" tag for historically a.out platforms.
|
|
|
|
#
|
2013-12-06 12:04:52 +01:00
|
|
|
.if (!empty(MACHINE_ARCH:Mearm*))
|
|
|
|
MACHINE_GNU_PLATFORM?=${MACHINE_GNU_ARCH}--netbsdelf-${MACHINE_ARCH:C/eb//:C/v[4-7]//:S/earm/eabi/}
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.elif (${MACHINE_GNU_ARCH} == "arm" || \
|
2010-02-16 15:41:33 +01:00
|
|
|
${MACHINE_GNU_ARCH} == "armeb" || \
|
|
|
|
${MACHINE_ARCH} == "i386" || \
|
|
|
|
${MACHINE_CPU} == "m68k" || \
|
|
|
|
${MACHINE_GNU_ARCH} == "sh" || \
|
|
|
|
${MACHINE_GNU_ARCH} == "shle" || \
|
|
|
|
${MACHINE_ARCH} == "sparc" || \
|
|
|
|
${MACHINE_ARCH} == "vax")
|
|
|
|
MACHINE_GNU_PLATFORM?=${MACHINE_GNU_ARCH}--netbsdelf
|
|
|
|
.else
|
|
|
|
MACHINE_GNU_PLATFORM?=${MACHINE_GNU_ARCH}--netbsd
|
|
|
|
.endif
|
|
|
|
|
2013-01-13 17:20:11 +01:00
|
|
|
.if defined(__MINIX)
|
|
|
|
# We have a simpler toolchain naming scheme
|
|
|
|
MACHINE_GNU_PLATFORM:=${MACHINE_GNU_ARCH}-elf32-minix
|
|
|
|
.endif # defined(__MINIX)
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# Determine if arch uses native kernel modules with rump
|
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "i386" || \
|
|
|
|
${MACHINE_ARCH} == "x86_64"
|
|
|
|
RUMPKMOD= # defined
|
|
|
|
.endif
|
|
|
|
|
|
|
|
TARGETS+= all clean cleandir depend dependall includes \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
install lint obj regress tags html analyze
|
2010-02-16 15:41:33 +01:00
|
|
|
PHONY_NOTMAIN = all clean cleandir depend dependall distclean includes \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
install lint obj regress beforedepend afterdepend \
|
2010-02-16 15:41:33 +01:00
|
|
|
beforeinstall afterinstall realinstall realdepend realall \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
html subdir-all subdir-install subdir-depend analyze
|
2010-02-16 15:41:33 +01:00
|
|
|
.PHONY: ${PHONY_NOTMAIN}
|
|
|
|
.NOTMAIN: ${PHONY_NOTMAIN}
|
|
|
|
|
|
|
|
.if ${NEED_OWN_INSTALL_TARGET} != "no"
|
|
|
|
.if !target(install)
|
|
|
|
install: beforeinstall .WAIT subdir-install realinstall .WAIT afterinstall
|
|
|
|
beforeinstall:
|
|
|
|
subdir-install:
|
|
|
|
realinstall:
|
|
|
|
afterinstall:
|
|
|
|
.endif
|
|
|
|
all: realall subdir-all
|
|
|
|
subdir-all:
|
|
|
|
realall:
|
|
|
|
depend: realdepend subdir-depend
|
|
|
|
subdir-depend:
|
|
|
|
realdepend:
|
|
|
|
distclean: cleandir
|
|
|
|
cleandir: clean
|
|
|
|
|
|
|
|
dependall: .NOTMAIN realdepend .MAKE
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
@cd "${.CURDIR}"; ${MAKE} realall
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Define MKxxx variables (which are either yes or no) for users
|
|
|
|
# to set in /etc/mk.conf and override in the make environment.
|
|
|
|
# These should be tested with `== "no"' or `!= "no"'.
|
|
|
|
# The NOxxx variables should only be set by Makefiles.
|
|
|
|
#
|
|
|
|
# Please keep etc/Makefile and share/man/man5/mk.conf.5 in sync
|
|
|
|
# with changes to the MK* variables here.
|
|
|
|
#
|
|
|
|
|
|
|
|
#
|
|
|
|
# Supported NO* options (if defined, MK* will be forced to "no",
|
|
|
|
# regardless of user's mk.conf setting).
|
|
|
|
#
|
|
|
|
# Source makefiles should set NO*, and not MK*, and must do so before
|
|
|
|
# including bsd.own.mk.
|
|
|
|
#
|
|
|
|
.for var in \
|
|
|
|
NOCRYPTO NODOC NOHTML NOINFO NOLINKLIB NOLINT NOMAN NONLS NOOBJ NOPIC \
|
|
|
|
NOPICINSTALL NOPROFILE NOSHARE NOSTATICLIB
|
|
|
|
.if defined(${var})
|
|
|
|
MK${var:S/^NO//}:= no
|
|
|
|
.endif
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
|
|
|
# Older-style variables that enabled behaviour when set.
|
|
|
|
#
|
|
|
|
.for var in MANZ UNPRIVED UPDATE
|
|
|
|
.if defined(${var})
|
|
|
|
MK${var}:= yes
|
|
|
|
.endif
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
|
|
|
# MK* options which have variable defaults.
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if ${MACHINE_ARCH} == "x86_64" || ${MACHINE_ARCH} == "sparc64" || \
|
|
|
|
${MACHINE_ARCH} == "mips64eb" || ${MACHINE_ARCH} == "mips64el"
|
2010-02-16 15:41:33 +01:00
|
|
|
MKCOMPAT?= yes
|
2013-12-06 12:04:52 +01:00
|
|
|
.elif !empty(MACHINE_ARCH:Mearm*)
|
|
|
|
MKCOMPAT?= no
|
2010-02-16 15:41:33 +01:00
|
|
|
.else
|
|
|
|
# Don't let this build where it really isn't supported.
|
|
|
|
MKCOMPAT:= no
|
|
|
|
.endif
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#.if ${MACHINE_ARCH} == "x86_64" || ${MACHINE_ARCH} == "i386" || \
|
|
|
|
|
|
|
|
.if ${MACHINE} == "evbppc"
|
|
|
|
MKCOMPATMODULES?= yes
|
|
|
|
.else
|
|
|
|
MKCOMPATMODULES:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Default mips64 to softfloat now.
|
2013-12-06 12:04:52 +01:00
|
|
|
# arm is always softfloat unless it isn't
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# emips is always softfloat.
|
2013-12-06 12:04:52 +01:00
|
|
|
# coldfire is always softfloat
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#
|
|
|
|
.if ${MACHINE_ARCH} == "mips64eb" || ${MACHINE_ARCH} == "mips64el" || \
|
2013-12-06 12:04:52 +01:00
|
|
|
(${MACHINE_CPU} == "arm" && ${MACHINE_ARCH:M*hf*} == "") || \
|
|
|
|
${MACHINE_ARCH} == "coldfire" || \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
${MACHINE} == "emips"
|
|
|
|
MKSOFTFLOAT?= yes
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MACHINE} == "emips"
|
|
|
|
SOFTFLOAT_BITS= 32
|
|
|
|
.endif
|
|
|
|
|
2013-02-26 09:24:42 +01:00
|
|
|
.if ${MACHINE_ARCH} == "i386" || \
|
|
|
|
${MACHINE_ARCH} == "x86_64" || \
|
|
|
|
${MACHINE_ARCH} == "sparc"
|
|
|
|
MKSLJIT?= yes
|
|
|
|
.else
|
|
|
|
MKSLJIT?= no
|
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# MK* backward compatibility.
|
|
|
|
#
|
|
|
|
.if defined(MKBFD)
|
|
|
|
MKBINUTILS?= ${MKBFD}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# We want to build zfs only for i386 and amd64 by default for now.
|
|
|
|
#
|
|
|
|
.if ${MACHINE} == "amd64" || ${MACHINE} == "i386"
|
|
|
|
MKZFS?= yes
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# MK* options which default to "yes".
|
|
|
|
#
|
|
|
|
_MKVARS.yes= \
|
|
|
|
MKATF \
|
|
|
|
MKBINUTILS \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKCRYPTO MKCOMPLEX MKCVS MKCXX \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKDOC \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKGCC MKGCCCMDS MKGDB MKGROFF \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKHESIOD MKHTML \
|
|
|
|
MKIEEEFP MKINET6 MKINFO MKIPFILTER MKISCSI \
|
|
|
|
MKKERBEROS \
|
|
|
|
MKKMOD \
|
2013-12-06 12:04:52 +01:00
|
|
|
MKLDAP MKLIBSTDCXX MKLINKLIB MKLVM \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKMAN MKMANDOC \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKMDNS \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKMAKEMANDB \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKNLS \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKNPF \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKOBJ \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKPAM MKPERFUSE \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKPF MKPIC MKPICINSTALL MKPICLIB MKPOSTFIX MKPROFILE \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKRUMP \
|
2010-02-16 15:41:33 +01:00
|
|
|
MKSHARE MKSKEY MKSTATICLIB \
|
|
|
|
MKX11FONTS \
|
|
|
|
MKYP
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
|
2011-07-29 20:36:42 +02:00
|
|
|
#MINIX-specific vars
|
|
|
|
_MKVARS.yes+= \
|
2013-10-27 01:54:37 +02:00
|
|
|
MKSYSDEBUG MKLIVEUPDATE MKLWIP
|
2012-08-28 19:34:08 +02:00
|
|
|
.if (${MACHINE_ARCH} == "i386")
|
|
|
|
_MKVARS.yes+= \
|
|
|
|
MKWATCHDOG MKACPI MKAPIC MKDEBUGREG MKINSTALLBOOT MKPCI
|
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
.for var in ${_MKVARS.yes}
|
|
|
|
${var}?= yes
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# Exceptions to the above:
|
|
|
|
#
|
|
|
|
#.if ${MACHINE} == "evbppc"
|
|
|
|
#MKKMOD= no
|
|
|
|
#.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# MK* options which default to "no". Note that MKZFS has a different
|
|
|
|
# default for some platforms, see above.
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
_MKVARS.no= \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKBSDGREP MKBSDTAR \
|
|
|
|
MKCATPAGES MKCRYPTO_RC5 MKDEBUG \
|
|
|
|
MKDEBUGLIB MKDTRACE MKEXTSRC \
|
2013-12-06 12:04:52 +01:00
|
|
|
MKKYUA MKLLD MKLLDB MKLINT \
|
|
|
|
MKMANZ MKMCLINKER MKOBJDIRS \
|
|
|
|
MKLIBCXX MKLLVM MKPCC \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKPIGZGZIP \
|
|
|
|
MKREPRO \
|
2013-12-06 12:04:52 +01:00
|
|
|
MKSOFTFLOAT MKSTRIPIDENT MKTPM \
|
|
|
|
MKUNPRIVED MKUPDATE MKX11 MKX11MOTIF MKZFS
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
|
2011-07-20 09:57:08 +02:00
|
|
|
#MINIX-specific vars
|
|
|
|
_MKVARS.no+= \
|
2013-06-17 16:51:49 +02:00
|
|
|
MKIMAGEONLY MKSMALL MKBITCODE
|
2013-12-06 12:04:52 +01:00
|
|
|
.if !empty(MACHINE_ARCH:Mearm*)
|
2012-08-28 19:34:08 +02:00
|
|
|
_MKVARS.no+= \
|
|
|
|
MKWATCHDOG MKACPI MKAPIC MKDEBUGREG MKINSTALLBOOT MKPCI
|
|
|
|
.endif
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
.for var in ${_MKVARS.no}
|
|
|
|
${var}?=no
|
|
|
|
.endfor
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
#
|
|
|
|
# Do we default to XFree86 or Xorg for this platform?
|
|
|
|
#
|
|
|
|
.if \
|
|
|
|
${MACHINE} == "acorn32" || \
|
|
|
|
${MACHINE} == "alpha" || \
|
|
|
|
${MACHINE} == "amiga" || \
|
|
|
|
${MACHINE} == "ews4800mips" || \
|
|
|
|
${MACHINE} == "mac68k" || \
|
|
|
|
${MACHINE} == "newsmips" || \
|
|
|
|
${MACHINE} == "pmax" || \
|
|
|
|
${MACHINE} == "sun3" || \
|
|
|
|
${MACHINE} == "x68k"
|
|
|
|
X11FLAVOUR?= XFree86
|
|
|
|
.else
|
|
|
|
X11FLAVOUR?= Xorg
|
|
|
|
.endif
|
|
|
|
|
2013-12-06 12:04:52 +01:00
|
|
|
#
|
|
|
|
# Which platforms build the xorg-server drivers (as opposed
|
|
|
|
# to just Xnest and Xvfb.)
|
|
|
|
#
|
|
|
|
.if ${X11FLAVOUR} == "Xorg" && \
|
|
|
|
${MACHINE} == "alpha" || \
|
|
|
|
${MACHINE} == "amd64" || \
|
|
|
|
${MACHINE} == "bebox" || \
|
|
|
|
${MACHINE} == "cats" || \
|
|
|
|
${MACHINE} == "dreamcast" || \
|
|
|
|
${MACHINE} == "ews4800mips" || \
|
|
|
|
${MACHINE} == "evbarm" || \
|
|
|
|
${MACHINE} == "evbmips" || \
|
|
|
|
${MACHINE} == "hp300" || \
|
|
|
|
${MACHINE} == "hpcarm" || \
|
|
|
|
${MACHINE} == "hpcmips" || \
|
|
|
|
${MACHINE} == "hpcsh" || \
|
|
|
|
${MACHINE} == "i386" || \
|
|
|
|
${MACHINE} == "luna68k" || \
|
|
|
|
${MACHINE} == "macppc" || \
|
|
|
|
${MACHINE} == "netwinder" || \
|
|
|
|
${MACHINE} == "newsmips" || \
|
|
|
|
${MACHINE} == "prep" || \
|
|
|
|
${MACHINE} == "ofppc" || \
|
|
|
|
${MACHINE} == "sgimips" || \
|
|
|
|
${MACHINE} == "shark" || \
|
|
|
|
${MACHINE} == "sparc" || \
|
|
|
|
${MACHINE} == "sparc64" || \
|
|
|
|
${MACHINE} == "vax" || \
|
|
|
|
${MACHINE} == "zaurus"
|
|
|
|
MKXORG_SERVER?=yes
|
|
|
|
.else
|
|
|
|
MKXORG_SERVER?=no
|
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# Force some options off if their dependencies are off.
|
|
|
|
#
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.if ${MKCXX} == "no"
|
|
|
|
MKATF:= no
|
|
|
|
MKGROFF:= no
|
2013-02-26 09:24:42 +01:00
|
|
|
MKKYUA:= no
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
.if ${MKCRYPTO} == "no"
|
|
|
|
MKKERBEROS:= no
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MKLDAP:= no
|
2010-02-16 15:41:33 +01:00
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MKMAN} == "no"
|
|
|
|
MKCATPAGES:= no
|
|
|
|
MKHTML:= no
|
|
|
|
.endif
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
_MANINSTALL= maninstall
|
|
|
|
.if ${MKCATPAGES} != "no"
|
|
|
|
_MANINSTALL+= catinstall
|
|
|
|
.endif
|
|
|
|
.if ${MKHTML} != "no"
|
|
|
|
_MANINSTALL+= htmlinstall
|
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
.if ${MKLINKLIB} == "no"
|
|
|
|
MKLINT:= no
|
|
|
|
MKPICINSTALL:= no
|
|
|
|
MKPROFILE:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MKPIC} == "no"
|
|
|
|
MKPICLIB:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MKOBJ} == "no"
|
|
|
|
MKOBJDIRS:= no
|
|
|
|
.endif
|
|
|
|
|
|
|
|
.if ${MKSHARE} == "no"
|
|
|
|
MKCATPAGES:= no
|
|
|
|
MKDOC:= no
|
|
|
|
MKINFO:= no
|
|
|
|
MKHTML:= no
|
|
|
|
MKMAN:= no
|
|
|
|
MKNLS:= no
|
|
|
|
.endif
|
|
|
|
|
2011-07-29 20:36:42 +02:00
|
|
|
# MINIX
|
2011-08-01 11:05:17 +02:00
|
|
|
.if ${MKSMALL} == "yes"
|
2011-07-29 20:36:42 +02:00
|
|
|
MKWATCHDOG:= no
|
2011-07-31 16:20:34 +02:00
|
|
|
MKACPI:= no
|
|
|
|
MKAPIC:= no
|
2011-08-16 17:18:55 +02:00
|
|
|
MKDEBUGREG:= no
|
2011-08-16 21:48:03 +02:00
|
|
|
MKSYSDEBUG:= no
|
2011-09-02 16:57:22 +02:00
|
|
|
MKLIVEUPDATE:= no
|
2011-07-29 20:36:42 +02:00
|
|
|
.endif
|
|
|
|
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
|
|
|
# install(1) parameters.
|
|
|
|
#
|
|
|
|
COPY?= -c
|
|
|
|
.if ${MKUPDATE} == "no"
|
|
|
|
PRESERVE?=
|
|
|
|
.else
|
|
|
|
PRESERVE?= -p
|
|
|
|
.endif
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
RENAME?= -r
|
2010-03-08 12:04:59 +01:00
|
|
|
HRDLINK?= -l h
|
2010-02-16 15:41:33 +01:00
|
|
|
SYMLINK?= -l s
|
|
|
|
|
|
|
|
METALOG?= ${DESTDIR}/METALOG
|
|
|
|
METALOG.add?= ${TOOL_CAT} -l >> ${METALOG}
|
|
|
|
.if (${_SRC_TOP_} != "") # only set INSTPRIV if inside ${NETBSDSRCDIR}
|
|
|
|
.if ${MKUNPRIVED} != "no"
|
|
|
|
INSTPRIV.unpriv=-U -M ${METALOG} -D ${DESTDIR} -h sha256
|
|
|
|
.else
|
|
|
|
INSTPRIV.unpriv=
|
|
|
|
.endif
|
|
|
|
INSTPRIV?= ${INSTPRIV.unpriv} -N ${NETBSDSRCDIR}/etc
|
|
|
|
.endif
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
STRIPFLAG?=
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
.if ${NEED_OWN_INSTALL_TARGET} != "no"
|
|
|
|
INSTALL_DIR?= ${INSTALL} ${INSTPRIV} -d
|
|
|
|
INSTALL_FILE?= ${INSTALL} ${INSTPRIV} ${COPY} ${PRESERVE} ${RENAME}
|
|
|
|
INSTALL_LINK?= ${INSTALL} ${INSTPRIV} ${HRDLINK} ${RENAME}
|
|
|
|
INSTALL_SYMLINK?= ${INSTALL} ${INSTPRIV} ${SYMLINK} ${RENAME}
|
|
|
|
HOST_INSTALL_FILE?= ${INSTALL} ${COPY} ${PRESERVE} ${RENAME}
|
|
|
|
HOST_INSTALL_DIR?= ${INSTALL} -d
|
|
|
|
HOST_INSTALL_SYMLINK?= ${INSTALL} ${SYMLINK} ${RENAME}
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Set defaults for the USE_xxx variables.
|
|
|
|
#
|
|
|
|
|
|
|
|
#
|
|
|
|
# USE_* options which default to "no" and will be forced to "no" if their
|
|
|
|
# corresponding MK* variable is set to "no".
|
|
|
|
#
|
|
|
|
.for var in USE_SKEY
|
|
|
|
.if (${${var:S/USE_/MK/}} == "no")
|
|
|
|
${var}:= no
|
|
|
|
.else
|
|
|
|
${var}?= no
|
|
|
|
.endif
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
|
|
|
# USE_* options which default to "yes" unless their corresponding MK*
|
|
|
|
# variable is set to "no".
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.for var in USE_HESIOD USE_INET6 USE_KERBEROS USE_LDAP USE_PAM USE_YP
|
|
|
|
.if (${${var:S/USE_/MK/}} == "no")
|
|
|
|
${var}:= no
|
|
|
|
.else
|
|
|
|
${var}?= yes
|
|
|
|
.endif
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#MINIX-specific vars
|
|
|
|
.for var in \
|
2013-10-27 01:54:37 +02:00
|
|
|
USE_WATCHDOG USE_ACPI USE_APIC USE_DEBUGREG USE_SYSDEBUG \
|
|
|
|
USE_LIVEUPDATE USE_PCI USE_BITCODE
|
2010-02-16 15:41:33 +01:00
|
|
|
.if (${${var:S/USE_/MK/}} == "no")
|
|
|
|
${var}:= no
|
|
|
|
.else
|
|
|
|
${var}?= yes
|
|
|
|
.endif
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
|
|
|
# USE_* options which default to "yes".
|
|
|
|
#
|
|
|
|
.for var in USE_JEMALLOC
|
|
|
|
${var}?= yes
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
#
|
|
|
|
# USE_* options which default to "no".
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# For now, disable pigz as compressor by default
|
|
|
|
.for var in USE_PIGZGZIP USE_LIBTRE
|
|
|
|
${var}?= no
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.if ${USE_PIGZGZIP} != "no"
|
|
|
|
TOOL_GZIP= ${TOOL_PIGZ}
|
|
|
|
.else
|
|
|
|
TOOL_GZIP= gzip
|
|
|
|
.endif
|
|
|
|
|
|
|
|
#
|
|
|
|
# Where X11 sources are and where it is installed to.
|
|
|
|
#
|
|
|
|
.if !defined(X11SRCDIR)
|
|
|
|
.if exists(${NETBSDSRCDIR}/../xsrc)
|
|
|
|
X11SRCDIR!= cd "${NETBSDSRCDIR}/../xsrc" && pwd
|
|
|
|
.else
|
|
|
|
X11SRCDIR= /usr/xsrc
|
|
|
|
.endif
|
|
|
|
.endif # !defined(X11SRCDIR)
|
|
|
|
|
|
|
|
X11SRCDIR.xc?= ${X11SRCDIR}/xfree/xc
|
|
|
|
X11SRCDIR.local?= ${X11SRCDIR}/local
|
|
|
|
.if ${X11FLAVOUR} == "Xorg"
|
|
|
|
X11ROOTDIR?= /usr/X11R7
|
|
|
|
.else
|
|
|
|
X11ROOTDIR?= /usr/X11R6
|
|
|
|
.endif
|
|
|
|
X11BINDIR?= ${X11ROOTDIR}/bin
|
|
|
|
X11ETCDIR?= /etc/X11
|
|
|
|
X11FONTDIR?= ${X11ROOTDIR}/lib/X11/fonts
|
|
|
|
X11INCDIR?= ${X11ROOTDIR}/include
|
|
|
|
X11LIBDIR?= ${X11ROOTDIR}/lib/X11
|
|
|
|
X11MANDIR?= ${X11ROOTDIR}/man
|
|
|
|
X11SHAREDIR?= ${X11ROOTDIR}/share
|
|
|
|
X11USRLIBDIR?= ${X11ROOTDIR}/lib
|
|
|
|
|
|
|
|
#
|
|
|
|
# New modular-xorg based builds
|
|
|
|
#
|
|
|
|
X11SRCDIRMIT?= ${X11SRCDIR}/external/mit
|
|
|
|
.for _lib in \
|
|
|
|
FS ICE SM X11 XScrnSaver XTrap Xau Xcomposite Xcursor Xdamage \
|
|
|
|
Xdmcp Xevie Xext Xfixes Xfont Xft Xi Xinerama Xmu Xpm \
|
|
|
|
Xrandr Xrender Xres Xt Xtst Xv XvMC Xxf86dga Xxf86misc Xxf86vm drm \
|
|
|
|
fontenc xkbfile xkbui Xaw lbxutil Xfontcache pciaccess xcb
|
|
|
|
X11SRCDIR.${_lib}?= ${X11SRCDIRMIT}/lib${_lib}/dist
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.for _proto in \
|
|
|
|
xcmisc xext xf86bigfont bigreqs input kb x fonts fixes scrnsaver \
|
|
|
|
xinerama dri2 render resource record video xf86dga xf86misc \
|
|
|
|
xf86vidmode composite damage trap gl randr fontcache xf86dri \
|
|
|
|
xcb-
|
|
|
|
X11SRCDIR.${_proto}proto?= ${X11SRCDIRMIT}/${_proto}proto/dist
|
|
|
|
.endfor
|
2010-02-16 15:41:33 +01:00
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
.for _dir in \
|
|
|
|
xtrans fontconfig expat freetype evieext mkfontscale bdftopcf \
|
|
|
|
xkbcomp xorg-cf-files imake xorg-server xbiff xkbdata xkeyboard-config \
|
|
|
|
xbitmaps appres xeyes xev xedit sessreg pixman \
|
|
|
|
beforelight bitmap editres makedepend fonttosfnt fslsfonts \
|
|
|
|
fstobdf MesaDemos MesaGLUT MesaLib ico iceauth lbxproxy listres lndir \
|
|
|
|
luit xproxymanagementprotocol mkfontdir oclock proxymngr rgb \
|
|
|
|
setxkbmap smproxy twm viewres x11perf xauth xcalc xclipboard \
|
|
|
|
xclock xcmsdb xconsole xcutsel xditview xdpyinfo xdriinfo xdm \
|
|
|
|
xfd xf86dga xfindproxy xfontsel xfwp xgamma xgc xhost xinit \
|
|
|
|
xkill xload xlogo xlsatoms xlsclients xlsfonts xmag xmessage \
|
|
|
|
xmh xmodmap xmore xman xprop xrandr xrdb xrefresh xset \
|
|
|
|
xsetmode xsetpointer xsetroot xsm xstdcmap xvidtune xvinfo \
|
|
|
|
xwininfo xwud xprehashprinterlist xplsprinters xkbprint xkbevd \
|
|
|
|
xterm xwd xfs xfsinfo xphelloworld xtrap xkbutils xkbcomp \
|
2013-12-06 12:04:52 +01:00
|
|
|
xkeyboard-config xinput xcb-util xorg-docs \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
font-adobe-100dpi font-adobe-75dpi font-adobe-utopia-100dpi \
|
|
|
|
font-adobe-utopia-75dpi font-adobe-utopia-type1 \
|
|
|
|
font-alias \
|
|
|
|
font-bh-100dpi font-bh-75dpi font-bh-lucidatypewriter-100dpi \
|
|
|
|
font-bh-lucidatypewriter-75dpi font-bh-ttf font-bh-type1 \
|
|
|
|
font-bitstream-100dpi font-bitstream-75dpi font-bitstream-type1 \
|
|
|
|
font-cursor-misc font-daewoo-misc font-dec-misc font-ibm-type1 \
|
|
|
|
font-isas-misc font-jis-misc font-misc-misc font-mutt-misc \
|
|
|
|
font-sony-misc font-util ttf-bitstream-vera encodings
|
|
|
|
X11SRCDIR.${_dir}?= ${X11SRCDIRMIT}/${_dir}/dist
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.for _i in \
|
|
|
|
elographics keyboard mouse synaptics vmmouse void ws
|
|
|
|
X11SRCDIR.xf86-input-${_i}?= ${X11SRCDIRMIT}/xf86-input-${_i}/dist
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.for _v in \
|
|
|
|
ag10e apm ark ast ati chips cirrus crime \
|
|
|
|
geode glint i128 i740 igs imstt intel mach64 mga \
|
|
|
|
neomagic newport nsc nv nvxbox openchrome pnozz \
|
|
|
|
r128 radeonhd rendition \
|
|
|
|
s3 s3virge savage siliconmotion sis suncg14 \
|
|
|
|
suncg6 sunffb sunleo suntcx \
|
|
|
|
tdfx tga trident tseng vesa vga via vmware wsfb xgi
|
|
|
|
X11SRCDIR.xf86-video-${_v}?= ${X11SRCDIRMIT}/xf86-video-${_v}/dist
|
|
|
|
.endfor
|
|
|
|
|
|
|
|
.if ${X11FLAVOUR} == "Xorg"
|
|
|
|
X11DRI?= yes
|
|
|
|
.endif
|
|
|
|
|
|
|
|
X11DRI?= no
|
|
|
|
X11LOADABLE?= yes
|
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
# Where extsrc sources are and where it is installed to.
|
|
|
|
#
|
|
|
|
.if !defined(EXTSRCSRCDIR)
|
|
|
|
.if exists(${NETBSDSRCDIR}/../extsrc)
|
|
|
|
EXTSRCSRCDIR!= cd "${NETBSDSRCDIR}/../extsrc" && pwd
|
|
|
|
.else
|
|
|
|
EXTSRCSRCDIR= /usr/extsrc
|
|
|
|
.endif
|
|
|
|
.endif # !defined(EXTSRCSRCDIR)
|
|
|
|
|
|
|
|
EXTSRCROOTDIR?= /usr/ext
|
|
|
|
EXTSRCBINDIR?= ${EXTSRCROOTDIR}/bin
|
|
|
|
EXTSRCETCDIR?= /etc/ext
|
|
|
|
EXTSRCINCDIR?= ${EXTSRCROOTDIR}/include
|
|
|
|
EXTSRCLIBDIR?= ${EXTSRCROOTDIR}/lib/ext
|
|
|
|
EXTSRCMANDIR?= ${EXTSRCROOTDIR}/man
|
|
|
|
EXTSRCUSRLIBDIR?= ${EXTSRCROOTDIR}/lib
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
#
|
|
|
|
# MAKEDIRTARGET dir target [extra make(1) params]
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
# run "cd $${dir} && ${MAKEDIRTARGETENV} ${MAKE} [params] $${target}", with a pretty message
|
2010-02-16 15:41:33 +01:00
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MAKEDIRTARGETENV?=
|
2010-02-16 15:41:33 +01:00
|
|
|
MAKEDIRTARGET=\
|
|
|
|
@_makedirtarget() { \
|
|
|
|
dir="$$1"; shift; \
|
|
|
|
target="$$1"; shift; \
|
|
|
|
case "$${dir}" in \
|
|
|
|
/*) this="$${dir}/"; \
|
|
|
|
real="$${dir}" ;; \
|
|
|
|
.) this="${_THISDIR_}"; \
|
|
|
|
real="${.CURDIR}" ;; \
|
|
|
|
*) this="${_THISDIR_}$${dir}/"; \
|
|
|
|
real="${.CURDIR}/$${dir}" ;; \
|
|
|
|
esac; \
|
|
|
|
show=$${this:-.}; \
|
|
|
|
echo "$${target} ===> $${show%/}$${1:+ (with: $$@)}"; \
|
|
|
|
cd "$${real}" \
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
&& ${MAKEDIRTARGETENV} ${MAKE} _THISDIR_="$${this}" "$$@" $${target}; \
|
2010-02-16 15:41:33 +01:00
|
|
|
}; \
|
|
|
|
_makedirtarget
|
|
|
|
|
|
|
|
#
|
|
|
|
# MAKEVERBOSE support. Levels are:
|
|
|
|
# 0 Minimal output ("quiet")
|
|
|
|
# 1 Describe what is occurring
|
|
|
|
# 2 Describe what is occurring and echo the actual command
|
|
|
|
# 3 Ignore the effect of the "@" prefix in make commands
|
|
|
|
# 4 Trace shell commands using the shell's -x flag
|
|
|
|
#
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
MAKEVERBOSE?= 2
|
2010-02-16 15:41:33 +01:00
|
|
|
|
|
|
|
.if ${MAKEVERBOSE} == 0
|
|
|
|
_MKMSG?= @\#
|
|
|
|
_MKSHMSG?= : echo
|
|
|
|
_MKSHECHO?= : echo
|
|
|
|
.SILENT:
|
|
|
|
.elif ${MAKEVERBOSE} == 1
|
|
|
|
_MKMSG?= @echo ' '
|
|
|
|
_MKSHMSG?= echo ' '
|
|
|
|
_MKSHECHO?= : echo
|
|
|
|
.SILENT:
|
|
|
|
.else # MAKEVERBOSE >= 2
|
|
|
|
_MKMSG?= @echo '\# '
|
|
|
|
_MKSHMSG?= echo '\# '
|
|
|
|
_MKSHECHO?= echo
|
|
|
|
.SILENT: __makeverbose_dummy_target__
|
|
|
|
.endif # MAKEVERBOSE >= 2
|
|
|
|
.if ${MAKEVERBOSE} >= 3
|
|
|
|
.MAKEFLAGS: -dl
|
|
|
|
.endif # ${MAKEVERBOSE} >= 3
|
|
|
|
.if ${MAKEVERBOSE} >= 4
|
|
|
|
.MAKEFLAGS: -dx
|
|
|
|
.endif # ${MAKEVERBOSE} >= 4
|
|
|
|
|
|
|
|
_MKMSG_BUILD?= ${_MKMSG} " build "
|
|
|
|
_MKMSG_CREATE?= ${_MKMSG} " create "
|
|
|
|
_MKMSG_COMPILE?= ${_MKMSG} "compile "
|
|
|
|
_MKMSG_FORMAT?= ${_MKMSG} " format "
|
|
|
|
_MKMSG_INSTALL?= ${_MKMSG} "install "
|
|
|
|
_MKMSG_LINK?= ${_MKMSG} " link "
|
|
|
|
_MKMSG_LEX?= ${_MKMSG} " lex "
|
|
|
|
_MKMSG_REMOVE?= ${_MKMSG} " remove "
|
|
|
|
_MKMSG_YACC?= ${_MKMSG} " yacc "
|
|
|
|
|
|
|
|
_MKSHMSG_CREATE?= ${_MKSHMSG} " create "
|
|
|
|
_MKSHMSG_INSTALL?= ${_MKSHMSG} "install "
|
|
|
|
|
|
|
|
_MKTARGET_BUILD?= ${_MKMSG_BUILD} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_CREATE?= ${_MKMSG_CREATE} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_COMPILE?= ${_MKMSG_COMPILE} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_FORMAT?= ${_MKMSG_FORMAT} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_INSTALL?= ${_MKMSG_INSTALL} ${.TARGET}
|
|
|
|
_MKTARGET_LINK?= ${_MKMSG_LINK} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_LEX?= ${_MKMSG_LEX} ${.CURDIR:T}/${.TARGET}
|
|
|
|
_MKTARGET_REMOVE?= ${_MKMSG_REMOVE} ${.TARGET}
|
|
|
|
_MKTARGET_YACC?= ${_MKMSG_YACC} ${.CURDIR:T}/${.TARGET}
|
|
|
|
|
|
|
|
.if ${MKMANDOC} == "yes"
|
|
|
|
TARGETS+= lintmanpages
|
|
|
|
.endif
|
|
|
|
|
Upgrading build system to new NetBSD revision
The tested targets are the followgin ones:
* tools
* distribution
* sets
* release
The remaining NetBSD targets have not been disabled nor tested
*at all*. Try them at your own risk, they may reboot the earth.
For all compliant Makefiles, objects and generated files are put in
MAKEOBJDIR, which means you can now keep objects between two branch
switching. Same for DESTDIR, please refer to build.sh options.
Regarding new or modifications of Makefiles a few things:
* Read share/mk/bsd.README
* If you add a subdirectory, add a Makefile in it, and have it called
by the parent through the SUBDIR variable.
* Do not add arbitrary inclusion which crosses to another branch of
the hierarchy; If you can't do without it, put a comment on why.
If possible, do not use inclusion at all.
* Use as much as possible the infrastructure, it is here to make
life easier, do not fight it.
Sets and package are now used to track files.
We have one set called "minix", composed of one package called "minix-sys"
2012-09-12 09:37:05 +02:00
|
|
|
TESTSBASE= /usr/tests
|
|
|
|
|
|
|
|
.endif # !defined(_BSD_OWN_MK_)
|