On Tue, 27 Nov 2001, Russell Coker wrote:

> What is probably of more interest to you is the locations that I've put
> header files in, here's what I'm currently installing:
> /usr/include

Well, this will naturally break the build of all of the userland components of SELinux. Why do you need to change the installation directories from what we use?

> /usr/include/linux/flask

This change is probably harmless for building the userland components, since the same #include directives will still work (#include <linux/flask/foo.h>). But what about the <linux/asm-i386/unistd.h> and the <linux/asm-i386/flask/unistd.h> files? These are also needed for building the userland components.

> /usr/include/selinux

This change will require changes to the userland components of SELinux, and I'm not planning on making these changes to our distribution unless there is a real justification. What's wrong with /usr/local/selinux/include?

--
Stephen D. Smalley, NAI Labs
ssmalley@nai.com




--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.