All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alain Birtz <abz@videotron.ca>
To: linuxppc-dev@lists.linuxppc.org
Subject: Shared memory between module and application: is it possible ?
Date: Fri, 26 May 2000 19:01:59 -0400	[thread overview]
Message-ID: <392F0267.C7933983@videotron.ca> (raw)


How application can do to exchange data with module ?

I know how to share memory between two application,
but when I try to make the samething with module and application
I get header confict:

----------------
In file included from /usr/include/sys/shm.h:24,
                 from mod_l1.c:9:
/usr/include/unistd.h:193: conflicting types for `ssize_t'
/usr/include/linux/types.h:37: previous declaration of `ssize_t'
In file included from /usr/include/sys/shm.h:25,
                 from mod_l1.c:9:
/usr/include/sys/types.h:46: conflicting types for `ino_t'
/usr/include/linux/types.h:11: previous declaration of `ino_t'
/usr/include/sys/types.h:57: conflicting types for `dev_t'
/usr/include/linux/types.h:10: previous declaration of `dev_t'
/usr/include/sys/types.h:72: conflicting types for `nlink_t'
/usr/include/linux/types.h:13: previous declaration of `nlink_t'
In file included from /usr/include/sys/types.h:193,
                 from /usr/include/sys/shm.h:25,
                 from mod_l1.c:9:
/usr/include/sys/select.h:51: conflicting types for `fd_set'
/usr/include/linux/types.h:9: previous declaration of `fd_set'
----------------

What can I do to fix it ?


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-05-26 23:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-26 23:01 Alain Birtz [this message]
2000-05-27 12:36 ` Shared memory between module and application: is it possible ? Michael Schmitz

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=392F0267.C7933983@videotron.ca \
    --to=abz@videotron.ca \
    --cc=linuxppc-dev@lists.linuxppc.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.