From: Andries Brouwer <aebr@win.tue.nl>
To: Sinelnikov Evgeny <linux4sin@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.6.0-test5: ioctl.h: _IOC_TYPECHECK: Is it a bug?
Date: Sun, 19 Oct 2003 23:13:40 +0200 [thread overview]
Message-ID: <20031019211340.GA7524@win.tue.nl> (raw)
In-Reply-To: <200310090253.01449.sin@info.sgu.ru>
On Thu, Oct 09, 2003 at 11:39:04PM +0400, Sinelnikov Evgeny wrote:
> I have problem with linux-utils.2.12 compile on 2.6.0-test5 headers. From this
> version instead 2.6.0-test4 was changed next file where added next string:
>
> include/asm-i386/ioctl.h:
> #define _IOC_TYPECHECK(t) \
> ((sizeof(t) == sizeof(t[1]) && \
> sizeof(t) < (1 << _IOC_SIZEBITS)) ? \
> sizeof(t) : __invalid_size_argument_for_IOC)
>
> This string have problems with compiling files using _IOR macros from ioctl.h
> Here is example from util-linux-2.12:
> #define BLKBSZGET _IOR(0x12,112,sizeof(int))
Normally, user space includes <sys/ioctl.h>, which again includes
<asm/ioctl.h> which defines _IOR etc.
It sounds like you use a symlink /usr/include/asm into a kernel source tree.
Doing such things is discouraged. For people that follow kernel development
the kernel source tree changes from day to day. When some utility shows
obscure errors it would be necessary to recall when, and with what kernel
headers it was last compiled in order to debug the problem. That is not good
for stability and reproducibility.
Moreover, there are no guarantees that kernel headers work in user space.
Often they do for some kernel versions and don't for other kernel versions.
It is the task of the distributor of include files to pick a suitable set.
Finally, when something is wrong with util-linux, please tell aeb@cwi.nl.
(There used to be a mailing list but I think it has been killed since
the recent spam floods.)
Andries
prev parent reply other threads:[~2003-10-19 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 19:39 Sinelnikov Evgeny
2003-10-19 21:13 ` Andries Brouwer [this message]
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=20031019211340.GA7524@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux4sin@mail.ru \
/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
Powered by JetHome