Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/lib/libpuffs/Makefile

27 lines
703 B
Makefile
Raw Normal View History

Remove suspension support from here too.
2009-12-05 15:13:08 +03:00
# $NetBSD: Makefile,v 1.23 2009/12/05 12:13:08 pooka Exp $
add libpuffs - the userspace programming interface for puffs This work was initially started and completed for Google SoC 2005 and tweaked to work a bit better in the past few weeks. While being far from complete, it is functional enough to be able and stable to host a fairly general-purpose in-memory file system in userspace. Even so, puffs should be considered experimental and no binary compatibility for interfaces or crash-freedom or zero security implications should be relied upon just yet. The GSoC project was mentored by William Studenmund and the final review for the code was done by Christos.
2006-10-23 02:52:21 +04:00
#
add the .include <bsd.own.mk>, so .d and .o files don't end up in the CWD. remove INCDIR=/usr/include, as my leenooks system doesn't have puffs .h files.
2006-10-23 03:51:37 +04:00
.include <bsd.own.mk>
Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2007-05-28 16:06:17 +04:00
USE_FORT?= yes # data-driven bugs?
add libpuffs - the userspace programming interface for puffs This work was initially started and completed for Google SoC 2005 and tweaked to work a bit better in the past few weeks. While being far from complete, it is functional enough to be able and stable to host a fairly general-purpose in-memory file system in userspace. Even so, puffs should be considered experimental and no binary compatibility for interfaces or crash-freedom or zero security implications should be relied upon just yet. The GSoC project was mentored by William Studenmund and the final review for the code was done by Christos.
2006-10-23 02:52:21 +04:00
WARNS= 4
LIB= puffs
Add some very initial support for a threading worker model as an alternative to the (vastly superior ;) continuation model. This is very preliminary stuff and not compiled by default (which it even won't do without some other patches I cannot commit yet). The raison d'commit of the patch is a snippet which ensures proper in-order dispatching of all operations, including those which don't require a response. Previously many of them would be dispatched simultaneosly, e.g. fsync and reclaim on the same node, which obviously isn't all that nice for correct operation.
2007-10-26 21:35:01 +04:00
# don't enable this unless you know what you're doing (or if you don't
# know what you're doing, it's still ok to enable this if you're me)
#LIBDPLIBS+= pthread ${.CURDIR}/../libpthread
#CPPFLAGS+= -DPUFFS_WITH_THREADS
move puffs request dispatching code into it's own module. no functional change
2007-05-12 01:42:42 +04:00
SRCS= puffs.c callcontext.c creds.c dispatcher.c flush.c \
framebuf.c null.c opdump.c paths.c pnode.c requests.c \
subr.c suspend.c
document credentials & access control methods
2007-03-22 20:38:09 +03:00
MAN= puffs.3 puffs_cc.3 puffs_cred.3 puffs_flush.3 \
Remove suspension support from here too.
2009-12-05 15:13:08 +03:00
puffs_framebuf.3 puffs_node.3 puffs_ops.3 puffs_path.3
add libpuffs - the userspace programming interface for puffs This work was initially started and completed for Google SoC 2005 and tweaked to work a bit better in the past few weeks. While being far from complete, it is functional enough to be able and stable to host a fairly general-purpose in-memory file system in userspace. Even so, puffs should be considered experimental and no binary compatibility for interfaces or crash-freedom or zero security implications should be relied upon just yet. The GSoC project was mentored by William Studenmund and the final review for the code was done by Christos.
2006-10-23 02:52:21 +04:00
INCS= puffs.h puffsdump.h
pass lint; fix install.
2006-10-23 04:22:24 +04:00
INCSDIR= /usr/include
LINTFLAGS+=-S -w
add libpuffs - the userspace programming interface for puffs This work was initially started and completed for Google SoC 2005 and tweaked to work a bit better in the past few weeks. While being far from complete, it is functional enough to be able and stable to host a fairly general-purpose in-memory file system in userspace. Even so, puffs should be considered experimental and no binary compatibility for interfaces or crash-freedom or zero security implications should be relied upon just yet. The GSoC project was mentored by William Studenmund and the final review for the code was done by Christos.
2006-10-23 02:52:21 +04:00
.include <bsd.lib.mk>