minix/usr.sbin/mkfs.mfs/Makefile

PROG=	mkfs.mfs
SRCS=	mkfs.c
BINDIR=	/sbin
MAN=

CPPFLAGS+= -D_MINIX

# LSC Adding this to activate the getline renaming macro
CPPFLAGS+= -D__NBSD_LIBC

.if ${HOST_OSTYPE:C/\-.*//:U} == "Minix" || !defined(HOSTPROGNAME)
LDADD+= -lminlib -lcompat_minix
.endif

.include <bsd.prog.mk>
Rename mkfs to mkfs.mfs and fsck to fsck.mfs. Add /sbin to root's PATH. 2010-08-05 14:35:00 +02:00			`PROG= mkfs.mfs`
			`SRCS= mkfs.c`
			`BINDIR= /sbin`
Convert boot/ and commands/ over to bsdmake 2010-05-12 18:28:54 +02:00			`MAN=`

hide block_t behind _MINIX (for gcc) 2012-08-24 17:54:07 +02:00			`CPPFLAGS+= -D_MINIX`

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			`# LSC Adding this to activate the getline renaming macro`
			`CPPFLAGS+= -D__NBSD_LIBC`

Cross compile on minix support * Remade patch so it works with minix patch tool. * New MINIX tar support -ox, so revert back to it In fetch scripts, tar had been replaced by bsdtar as the prebvious tar did not support the -o flag under minix, which is required to prevent usage of tar file stored user and group information. This introduces portability problems. As our new tar tool now support that flag revert back to improve portability. 2012-11-01 22:55:12 +01:00			`.if ${HOST_OSTYPE:C/\-.*//:U} == "Minix" \|\| !defined(HOSTPROGNAME)`
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			`LDADD+= -lminlib -lcompat_minix`
			`.endif`
Make mkfs.mfs cross compilable 2012-06-12 20:45:29 +02:00
Rename mkfiles from minix..mk to bsd..mk Makes things easier for pkgsrc 2010-06-25 20:29:09 +02:00			`.include <bsd.prog.mk>`