From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: jmorris@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: selinux build failure
Date: Mon, 25 Aug 2003 09:50:55 -0700 [thread overview]
Message-ID: <20030825095055.7d73b93b.rddunlap@osdl.org> (raw)
In-Reply-To: <200308250006.h7P06Ax0022635@post.webmailer.de>
On Sun, 24 Aug 2003 02:21:08 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
| James Morris wrote:
|
| > On Sun, 24 Aug 2003, Christoph Hellwig wrote:
| >
| >> Argg, this is b0rked. {asm,linux}/compat.h are for the 32bit compatiblity
| >> code. 64bit arches don't have fcntl64 - see the #if BITS_PER_LONG == 32
| >> around sys_fcntl64 in fcntl.c..
| >
| > Indeed. How about this?
Yes, the second patch fixes for me also. [2.6.0-test4 now]
I also see the warnings below.
| security/selinux/hooks.c: In function `selinux_bprm_set_security':
| security/selinux/hooks.c:1384: warning: cast to pointer from integer of different size
| security/selinux/hooks.c:1430: warning: cast to pointer from integer of different size
| security/selinux/hooks.c: In function `selinux_bprm_compute_creds':
| security/selinux/hooks.c:1520: warning: cast from pointer to integer of different size
| security/selinux/hooks.c: In function `selinux_getprocattr':
| security/selinux/hooks.c:3147: warning: passing arg 3 of `security_sid_to_context' from incompatible pointer type
Thanks.
--
~Randy [mantra: Always include kernel version.]
"Everything is relative."
next prev parent reply other threads:[~2003-08-25 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <o4Fj.1rw.9@gated-at.bofh.it>
[not found] ` <o4YO.1Fl.21@gated-at.bofh.it>
2003-08-24 0:21 ` Arnd Bergmann
2003-08-25 16:50 ` Randy.Dunlap [this message]
2003-08-26 0:12 ` James Morris
2003-08-23 4:27 Randy.Dunlap
2003-08-24 14:49 ` James Morris
2003-08-24 15:02 ` Christoph Hellwig
2003-08-24 15:25 ` James Morris
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=20030825095055.7d73b93b.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=arnd@arndb.de \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®