NetBSD/lib/librumphijack/Makefile

#	$NetBSD: Makefile,v 1.5 2011/01/25 12:56:57 pooka Exp $
#

LIB=		rumphijack
NOSTATICLIB=	dlfun
NOPROFILE=	dlfun
LIBDPLIBS+=	pthread ${.CURDIR}/../libpthread
MAN=		rumphijack.3

SRCS=		hijack.c

CPPFLAGS+=	-D_DIAGNOSTIC -D_REENTRANT

WARNS=		4

#DBG=-g
#NOGCCERROR=1

.include <bsd.lib.mk>
enable WARNS=4 2011-01-25 15:56:57 +03:00			`# $NetBSD: Makefile,v 1.5 2011/01/25 12:56:57 pooka Exp $`
Begin work on a syscall hijacking library which can be LD_PRELOADed to convince non-rumped applications to communicate with a rump kernel instead of the host kernel. The precision of what goes where is not exactly surgical, but for example when wanting to debug a web server's TCP/IP stack interaction, it might be enough. When all you have is a hand grenade, all problems look like a .... hmm? There's still plenty to figure out. For example, I'm not sure what the user interface will be like. Now it just attempts to hijack network communication. It also needs to sync with symbol renaming in libc, and maybe autogenerate the non-schizophrenic wrappers where the communication is heading to exactly one destination, lest I'll be a mummmy by the time I finish writing them all. As a fun example of a non-non-schizophrenic one, consider poll(). Work in progress, but I managed to get two non-rumped netcats talking to each other or fetching the index from a non-rumped thttpd. telnet works in one direction (i can read the data from netcat, but anything i send back is not printed). bozohttpd uses dup2() which i haven't bothered to address yet, etcetc. (not hooking this up the build for now) 2011-01-07 22:52:43 +03:00			`#`

			`LIB= rumphijack`
			`NOSTATICLIB= dlfun`
			`NOPROFILE= dlfun`
comment out DBG and NOGCCERROR, use proper LIBDPLIBS form 2011-01-18 22:53:23 +03:00			`LIBDPLIBS+= pthread ${.CURDIR}/../libpthread`
manual page for rumphijack 2011-01-25 15:56:25 +03:00			`MAN= rumphijack.3`
Begin work on a syscall hijacking library which can be LD_PRELOADed to convince non-rumped applications to communicate with a rump kernel instead of the host kernel. The precision of what goes where is not exactly surgical, but for example when wanting to debug a web server's TCP/IP stack interaction, it might be enough. When all you have is a hand grenade, all problems look like a .... hmm? There's still plenty to figure out. For example, I'm not sure what the user interface will be like. Now it just attempts to hijack network communication. It also needs to sync with symbol renaming in libc, and maybe autogenerate the non-schizophrenic wrappers where the communication is heading to exactly one destination, lest I'll be a mummmy by the time I finish writing them all. As a fun example of a non-non-schizophrenic one, consider poll(). Work in progress, but I managed to get two non-rumped netcats talking to each other or fetching the index from a non-rumped thttpd. telnet works in one direction (i can read the data from netcat, but anything i send back is not printed). bozohttpd uses dup2() which i haven't bothered to address yet, etcetc. (not hooking this up the build for now) 2011-01-07 22:52:43 +03:00
			`SRCS= hijack.c`

use -D_REENTRANT (should currently have no effect, but better safe than sorry if someone adds uses of stdio macros) 2011-01-18 18:00:22 +03:00			`CPPFLAGS+= -D_DIAGNOSTIC -D_REENTRANT`
Begin work on a syscall hijacking library which can be LD_PRELOADed to convince non-rumped applications to communicate with a rump kernel instead of the host kernel. The precision of what goes where is not exactly surgical, but for example when wanting to debug a web server's TCP/IP stack interaction, it might be enough. When all you have is a hand grenade, all problems look like a .... hmm? There's still plenty to figure out. For example, I'm not sure what the user interface will be like. Now it just attempts to hijack network communication. It also needs to sync with symbol renaming in libc, and maybe autogenerate the non-schizophrenic wrappers where the communication is heading to exactly one destination, lest I'll be a mummmy by the time I finish writing them all. As a fun example of a non-non-schizophrenic one, consider poll(). Work in progress, but I managed to get two non-rumped netcats talking to each other or fetching the index from a non-rumped thttpd. telnet works in one direction (i can read the data from netcat, but anything i send back is not printed). bozohttpd uses dup2() which i haven't bothered to address yet, etcetc. (not hooking this up the build for now) 2011-01-07 22:52:43 +03:00
enable WARNS=4 2011-01-25 15:56:57 +03:00			`WARNS= 4`

comment out DBG and NOGCCERROR, use proper LIBDPLIBS form 2011-01-18 22:53:23 +03:00			`#DBG=-g`
			`#NOGCCERROR=1`
Begin work on a syscall hijacking library which can be LD_PRELOADed to convince non-rumped applications to communicate with a rump kernel instead of the host kernel. The precision of what goes where is not exactly surgical, but for example when wanting to debug a web server's TCP/IP stack interaction, it might be enough. When all you have is a hand grenade, all problems look like a .... hmm? There's still plenty to figure out. For example, I'm not sure what the user interface will be like. Now it just attempts to hijack network communication. It also needs to sync with symbol renaming in libc, and maybe autogenerate the non-schizophrenic wrappers where the communication is heading to exactly one destination, lest I'll be a mummmy by the time I finish writing them all. As a fun example of a non-non-schizophrenic one, consider poll(). Work in progress, but I managed to get two non-rumped netcats talking to each other or fetching the index from a non-rumped thttpd. telnet works in one direction (i can read the data from netcat, but anything i send back is not printed). bozohttpd uses dup2() which i haven't bothered to address yet, etcetc. (not hooking this up the build for now) 2011-01-07 22:52:43 +03:00
			`.include <bsd.lib.mk>`