Date: Mon, 05 Feb 2001 18:32:36 -0700 From: Drew Eckhardt <drew@PoohSticks.ORG> To: Jochen Kaiser <Jochen.Kaiser@rrze.uni-erlangen.de> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: why isn't /usr/include/sys/syscall.h generated by makesyscalls? Message-ID: <200102060132.f161Wai06570@chopper.Poohsticks.ORG> In-Reply-To: Your message of "Tue, 06 Feb 2001 02:30:03 %2B0100." <20010206023002.A26837@devil.rrze.uni-erlangen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010206023002.A26837@devil.rrze.uni-erlangen.de>, Jochen.Kaiser@rr ze.uni-erlangen.de writes: >hi , > >i am trying to play with some statistics on ip protocols. I'd like >to implement a syscall for some funcions and I wonder why > >sh sr/src/sys/kern/makesyscalls.sh syscalls.master > >updates files in /usr/src/sys/kern/ but not the ones in >/usr/include/sys/ Because the kernel source tree you're playing with may be inappropriate for the machine you're building your kernel on. For example, my current employer sells black (metaphorically - in reality, they're more of a dark blue or purple) boxes which run older versions of FreeBSD than developers have on their desktop. >Any help, including stuff I should read is very appreciated. make install under /usr/src/sys/include will put the headers in the right place. make followed by make install under /usr/src/lib/libc will get you a library with the trivial wrapper functions that make the actual system calls. -- <a href="http://www.poohsticks.org/drew/">Home Page</a> For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102060132.f161Wai06570>