From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Cc: rusty@rustcorp.com.au
Subject: compiling futex-2.2
Date: Thu, 02 Oct 2003 23:29:12 -0400 [thread overview]
Message-ID: <3F7CED08.9080200@nortelnetworks.com> (raw)
I tried downloading and compiling the futex-2.2 package, and ran into
some snags.
The linux/futex.h file uses a number of nonstandard data types but does
not itself include any other headers. IN addition, the "u32" data type
is problematic, since it is only defined in the kernel headers if
__KERNEL__ is defined. Perhaps it should be defined as "__u32"?
Also, there is a definition of sys_futex in the package headers that
does not match the definition in the latest kernel headers. Any plans
to update the package?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2003-10-03 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 3:29 Chris Friesen [this message]
2003-10-03 4:28 ` compiling futex-2.2 Chris Friesen
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=3F7CED08.9080200@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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