From: Christian Marie <pingu@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: _syscallX isn't in linux-headers-2.6.20 ??
Date: Thu, 8 Feb 2007 16:10:45 +1100 [thread overview]
Message-ID: <20070208051045.GA8845@tiny.chatswood.mooter.com> (raw)
In-Reply-To: <1170895989.14243.49.camel@orpheus>
On Thu, Feb 08, 2007 at 10:23:09AM +0930, Iain Buchanan wrote:
> Hi all,
>
> I'm trying to use:
>
> _syscall3(int, ioprio_set, int, which, int, who, int, ioprio);
> _syscall2(int, ioprio_get, int, which, int, who);
>
> and supposedly I just
>
> #include <linux/unistd.h>
>
> but I'm getting these error from gcc:
>
> error: syntax error before "ioprio_set"
> warning: data definition has no type or storage class
> error: syntax error before "ioprio_get"
> warning: data definition has no type or storage class
Hi,
It would be helpful to provide us with the failing code as we have no
clue what you could be doing wrong.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-02-08 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 0:53 [gentoo-user] _syscallX isn't in linux-headers-2.6.20 ?? Iain Buchanan
2007-02-08 5:10 ` Christian Marie [this message]
2007-02-08 7:01 ` [gentoo-user] " Iain Buchanan
2007-02-08 10:40 ` [gentoo-user] " Boyd Stephen Smith Jr.
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=20070208051045.GA8845@tiny.chatswood.mooter.com \
--to=pingu@gentoo.org \
--cc=gentoo-user@lists.gentoo.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