From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Arne Henrichsen <ahenric@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys_sem* undefined
Date: Wed, 25 Aug 2004 09:14:13 -0700 [thread overview]
Message-ID: <20040825091413.0c43c78d.rddunlap@osdl.org> (raw)
In-Reply-To: <20040825115020.58522.qmail@web41501.mail.yahoo.com>
On Wed, 25 Aug 2004 12:50:20 +0100 (BST) Arne Henrichsen wrote:
| Hi,
|
| I am running kernel 2.6.8 and have noticed that in
| linux/sem.h the function declarations for sys_semop,
| sys_semop etc have been removed (as far as I can see
| from 2.6.4 onwards). Now when I compile my code I get
| the sys_sem* undefined warning messages. Which header
| file do I need to include now to get this support?
grep(1) finds sys_semop here:
./linux/syscalls.h:446:asmlinkage long sys_semop(int semid, struct sembuf __user
*sops,
Yes, include/linux/syscalls.h contains syscall prototypes.
| Also when I want to load my module with insmod it
| cannot find these symbols.
syscalls aren't called by name, so that's no surprise.
--
~Randy
next prev parent reply other threads:[~2004-08-25 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 11:50 Arne Henrichsen
2004-08-25 16:14 ` Randy.Dunlap [this message]
2004-08-26 9:05 ` Arne Henrichsen
2004-08-26 14:08 ` Paulo Marques
2004-08-26 13:44 ` Arne Henrichsen
2004-08-26 16:28 ` Randy.Dunlap
2004-08-27 9:26 ` Arne Henrichsen
2004-09-05 3:51 ` Pete
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=20040825091413.0c43c78d.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=ahenric@yahoo.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®