From: h.piat@faiveley.com
To: pthreads-win32@sources.redhat.com
Subject: Réf. : Re: PThread-win32 : Message Queue
Date: Mon, 13 Oct 2003 14:42:00 -0000 [thread overview]
Message-ID: <C1256DBE.0050D0A2.00@smtp.faiveley.fr> (raw)
Yes you are in the right. I only want to add this contrib file inside my
project.
My project add directly Pthread lib "libpthreadGC.a", and it works fine.
But I'm unable to compile "mqueue.c". Do you have an idea ?
Ross Johnson <rpj@callisto.canberra.edu.au> le 13/10/2003 16:35:50
Veuillez répondre à rpj@callisto.canberra.edu.au
Pour Herve PIAT/Faiveley
:
cc : pthreads-win32@sources.redhat.com
Objet Re: PThread-win32 : Message Queue
:
Hi,
The mqueue.zip stuff is provided as a separate contributed item and
isn't necessarily kept in sync with the library.
Also please note that the message queue implimentation is limited by the
fact that pthreads-win32 doesn't support process-shared mutexes or CVs,
which the code relies on. So it only works (assuming no other problems)
within a single process.
Ross
h.piat@faiveley.com wrote:
>
>Hi all
>
>I just donwload mqueue.zip and want to test it.
>But I have this result :
>
>In file included from tester.c:2:
>mqueue.h:24: warning: redefinition of `pid_t'
>
>e:/Dev-Cpp/include/sys/types.h:90: warning: `pid_t' previously declared here
>
>mqueue.h:62: parse error before "HANDLE"
>
>mqueue.h:62: warning: no semicolon at end of struct or union
>
>mqueue.h:67: parse error before '}' token
>
>make.exe: *** [tester.o] Error 1
>
>I'm under Win2K, with DevC++ and use the gcc compiler.
>I sucessful used PThread with my own program, and I dont know what's wrong with
>this mqueue distribution.
>Perhaps I forgot a define variable somewere !
>
>
>Thanks for your help
>
>Hervé PIAT
>Faiveley Transport
>Electronics engineering department
>
>
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>Faiveley is pleased to announce that its new website is on line at
>http://www.faiveley.com.
>Faiveley est heureux de vous annoncer la mise en ligne de son nouveau site
>http://www.faiveley.fr
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>NOTE : Ce courrier électronique est destiné exclusivement au(x) destinataire(s)
>mentionné(s) ci-dessus et peut contenir des informations privilégiées,
>confidentielles et/ou non soumises à divulgation aux termes des lois
>applicables. Si vous avez reçu ce message par erreur, ou s'il ne vous est pas
>destiné, veuillez le signaler immédiatement à l'expéditeur et effacer ce
>courrier électronique.
>
>NOTE: This e-mail message is intended only for the named recipient(s) above and
>may contain information that is privileged, confidential and/or exempt from
>disclosure under applicable law. If you have received this message in error,
or
>are not the named recipient(s), please immediately notify the sender and delete
>this e-mail message.
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>
>
next reply other threads:[~2003-10-13 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 14:42 h.piat [this message]
2003-10-15 21:50 Medina Sr, Aurelio
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=C1256DBE.0050D0A2.00@smtp.faiveley.fr \
--to=h.piat@faiveley.com \
--cc=pthreads-win32@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).