From: Adrian Bunk <bunk@fs.tum.de>
To: Stephen Smalley <sds@epoch.ncsc.mil>, jmorris@redhat.com
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: 2.6.0-test9: selinux compile error with "make O=..."
Date: Sun, 26 Oct 2003 02:22:09 +0200 [thread overview]
Message-ID: <20031026002209.GD23291@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0310251152410.5764-100000@home.osdl.org>
I got the following compile error in 2.6.0-test9 (using "make O=..."):
<-- snip -->
...
CC security/selinux/ss/ebitmap.o
cpp0: security/selinux/ss/global.h: No such file or directory
make[4]: *** [security/selinux/ss/ebitmap.o] Error 1
<-- snip -->
The problem comes from the following line in
security/selinux/ss/Makefile:
EXTRA_CFLAGS += -Isecurity/selinux/include -include security/selinux/ss/global.h
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-10-26 0:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 19:09 Linux 2.6.0-test9 Linus Torvalds
2003-10-25 19:52 ` Marcelo Tosatti
2003-10-25 20:14 ` viro
2003-10-25 22:35 ` Linus Torvalds
2003-10-25 23:45 ` Jose Luis Domingo Lopez
2003-10-26 0:22 ` Adrian Bunk [this message]
2003-10-26 9:49 ` 2.6.0-test9: selinux compile error with "make O=..." Sam Ravnborg
2003-10-27 13:40 ` Stephen Smalley
2003-10-27 18:42 ` Sam Ravnborg
2003-10-28 15:10 ` Stephen Smalley
2003-10-26 12:05 ` Linux 2.6.0-test9 Patrik Wallstrom
2003-10-27 18:21 ` Patrik Wallstrom
2003-10-27 22:51 ` bill davidsen
2003-10-28 2:12 ` Jeff Garzik
2003-10-28 4:52 ` Bill Davidsen
2003-10-26 15:05 ` Linux 2.4 <-> 2.6 compatibility (was: Linux 2.6.0-test9) Matthias Andree
2003-10-26 15:18 ` Linux 2.4 <-> 2.6 compatibility Måns Rullgård
2003-10-27 2:51 ` Matthias Andree
2003-10-26 16:06 ` Jochen Hein
2003-10-26 17:47 ` Fabio Massimo Di Nitto
2003-10-26 18:18 ` Jochen Hein
2003-10-27 16:02 ` Linux 2.6.0-test9 (compile stats) John Cherry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031026002209.GD23291@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sds@epoch.ncsc.mil \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.