From: "Thomas 'Dent' Mirlacher" <dent@cosy.sbg.ac.at>
To: bonganilinux@mweb.co.za
Cc: Hossein Mobahi <hmobahi@yahoo.com>,
linux-kernel@vger.kernel.org,
linux-c-programming@vger.kernel.org
Subject: Re: problem with <asm/semaphore.h>
Date: Tue, 4 Jun 2002 13:44:44 +0200 (MET DST) [thread overview]
Message-ID: <adi9k5$c50$2@main.gmane.org> (raw)
In-Reply-To: <E17FCaW-0002V9-00@rammstein.mweb.co.za>
On Tue, 4 Jun 2002 bonganilinux@mweb.co.za wrote:
> I think you a trying to include a file from the linux source
> which will not work for use-space apps. Try using
> #include <semaphore.h> instead
yes, sounds right, since struct semaphore in asm/semaphore will be
defined only if __KERNEL__ is defined.
tm
--
in some way i do, and in some way i don't.
next prev parent reply other threads:[~2002-06-04 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 11:41 problem with <asm/semaphore.h> bonganilinux
2002-06-04 11:44 ` Thomas 'Dent' Mirlacher [this message]
2002-06-04 11:44 ` Thomas 'Dent' Mirlacher
[not found] <1176885218.597268.304370@l77g2000hsb.googlegroups.com>
2007-04-19 0:50 ` Robert Hancock
[not found] ` <fa.fBTtgscoj66JCf4bIm8v290vCRo@ifi.uio.no>
[not found] ` <fa.w5cKcLCYzl2eiKiQW21MMlLALWM@ifi.uio.no>
[not found] ` <1176961482.904618.250700@e65g2000hsc.googlegroups.com>
2007-04-19 14:26 ` Robert Hancock
[not found] ` <fa.AvTW9UjANJ733AbQtnQmG3hvo7U@ifi.uio.no>
[not found] ` <fa.BgzkXXMJTw3V0hCHG6tJNpgDbkw@ifi.uio.no>
[not found] ` <fa.aUMayTTuQ16UFy6Q+LWR4hiTB1Q@ifi.uio.no>
[not found] ` <fa.633EuMGTHsDpCL9UutDSzsItJUQ@ifi.uio.no>
[not found] ` <1177003071.879067.80590@n76g2000hsh.googlegroups.com>
2007-04-21 22:57 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 11:19 Hossein Mobahi
2002-06-04 11:44 ` Shanks
2002-06-04 11:44 ` Shanks
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='adi9k5$c50$2@main.gmane.org' \
--to=dent@cosy.sbg.ac.at \
--cc=bonganilinux@mweb.co.za \
--cc=hmobahi@yahoo.com \
--cc=linux-c-programming@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.