From: Pinte_Stanislas@emc.com
To: pthreads-win32@sources.redhat.com
Subject: RE: compilation problem under windows 2000, using metrowerks mwcc Ver sion 2.4.5 build 199 ()
Date: Wed, 26 Jun 2002 06:36:00 -0000 [thread overview]
Message-ID: <8D3680004D2FD5118B510002B32C0FBE6EBE72@bebr3mx1.corp.emc.com> (raw)
I figured out the reason:
I compiled using the -gccincludes option.
withing the gcc includes, there is a mode_t type already defined...
So for the best, the variable name could be renamed to something unique to
the pthreads_win32...
Stan.
-----Original Message-----
From: Pinte_Stanislas@emc.com [mailto:Pinte_Stanislas@emc.com]
Sent: woensdag 26 juni 2002 14:44
To: pthreads-win32@sources.redhat.com
Subject: compilation problem under windows 2000, using metrowerks mwcc
Ver sion 2.4.5 build 199 ()
hello,
I am compiling a cpp file which is #include ing the semaphore.h header, and
it gives me:
[apply] ..\..\PTHREADS\Pre-built\include\semaphore.h:93: declaration
syntax error
[apply] ..\..\PTHREADS\Pre-built\include\semaphore.h:94: declaration
syntax error
errors.
There are two quick fixes for that stuff:
the first one is to replace
#ifdef HAVE_MODE_T
typedef unsigned int mode_t;
#endif
by
#ifdef WIN32
typedef unsigned int mode_t;
#endif
the second one is to
#define HAVE_MODE_T in the files #include'ing semaphore.h
any ideas why this happens?
thanks,
Stan.
Stanislas Pinte - Associate Software Engineer.
Phone: +32-(0)15-401.371
Fax: +32-(0)15-401.400
Address: Schaliënhoevedreef 20i, B-2800 Mechelen, Belgium
next reply other threads:[~2002-06-26 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 6:36 Pinte_Stanislas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-26 5:46 Pinte_Stanislas
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=8D3680004D2FD5118B510002B32C0FBE6EBE72@bebr3mx1.corp.emc.com \
--to=pinte_stanislas@emc.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).