public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Jack Atkinson <jgatkinsn@doxalogos.com>
To: pthreads-win32@sourceware.org
Subject: Need Help!
Date: Wed, 07 Apr 2010 15:09:00 -0000	[thread overview]
Message-ID: <4BBCA00B.100@doxalogos.com> (raw)

Hello,

I've downloaded the latest pthreads-win32.  I've put the 
pthreadsVCE2.dll file in my windows\system32 directory on Windows 7, 
64-bit.  I'm using Microsoft Visual Studio Express 2008.  My project is 
configured to include the header file.  However, I get these errors when 
I compile:

1>k:\adtran\managedcomponents\adbasewin32\signal.h(31) : error C2143: 
syntax error : missing ';' before '*'
1>k:\adtran\managedcomponents\adbasewin32\signal.h(31) : error C4430: 
missing type specifier - int assumed. Note: C++ does not support default-int
1>k:\adtran\managedcomponents\adbasewin32\signal.h(31) : error C4430: 
missing type specifier - int assumed. Note: C++ does not support default-int

When I look in the signal.h file (my own signal implementation) where 
the error is, I have this:

pthread_attr_t* sigev_notify_attributes;

I look up in the pthread.h file (pthreads-win32 file).  I see that 
pthread_attr_t is a typedef of "struct pthread_attr_t_".  However, I 
cannot find "struct pthread_attr_t_" anywhere inside the pthread.h 
file.  I did see an alternate define for "_UWIN", but there are no 
instructions on why "_UWIN" could be needed.

Could someone help me figure out what I've overlooked to get this 
compile?  Somehow other people have got this working, but I'm clueless 
with these incomplete defines found in the pthreads.h file.

Thanks,
J. Atkinson

                 reply	other threads:[~2010-04-07 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BBCA00B.100@doxalogos.com \
    --to=jgatkinsn@doxalogos.com \
    --cc=pthreads-win32@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).