Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Jan 1997 00:16:18 +1100
From:      Bruce Evans <bde@zeta.org.au>
To:        phk@critter.dk.tfs.com, wollman@lcs.mit.edu
Cc:        current@freebsd.org
Subject:   Re: <sys/kernel.h> and MAKE_SET
Message-ID:  <199701021316.AAA05486@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>>>>> Isn't it wrong to have MAKE_SET() in <sys/kernel.h> ?  What if you want
>>>>> to use it from userland ?

Probably.  It not very conveniently placed for use in the kernel.  In
userland, you declare the magic parts of MAKE_SET() in a user header.

>>I would just as soon see linker sets not used in user-land code, so as
>>to not diminish its value to other people who are attempting to do
>>things with it that don't involve using our linker/build environment.

I agree.

>>One of the nice things about most of the user-land code as it stands
>>is that I can take most of the utilities together with some useful
>>glue from the C library and have things work on other platforms.

Except for cruft like __P.

>I don't care much about this, but it prevents me from testing my
>kernel code in a userland harness :-(
>
>I'm going to stick in this patch:
>
>Index: kernel.h
> ...
>+#ifdef KERNEL

kernel.h was supposed to be kernel-only.  In the CSRG version it has
only the kernel variables that you ifdefed (less a few).

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701021316.AAA05486>