From: "Smith, David A2" <david.a2.smith@lmco.com>
To: pthreads-win32@sourceware.org
Subject: Newbie: Include file issues?
Date: Fri, 23 Jun 2006 18:28:00 -0000 [thread overview]
Message-ID: <DCC1EEDFB1AB0040BF64751002EA665E1040934B@emss03m09.us.lmco.com> (raw)
Hey guys and gals,
I'm trying to port some linux code to win32. I downloaded and built pthreads-w32 with no problems. When I try to use (include and link) it however, I get a lot of compilation errors.
error C2065: 'pthread_attr_t' : undeclared identifier
error C2146: syntax error : missing ';' before identifier 'attr'
error C3861: 'pthread_attr_init': identifier not found, even with argument-dependent lookup
Etc...
The problem seems to be that pthread_attr_t is a typedef of pthread_attr_t_*, which is never defined.
I noticed some people including implements.h in what appears to be an incomplete thread in the archive. When I include implements.h after pthread.h, it doesn't do any good. This doesn't appear to be a common problem... does anyone know why it is happening?
Thanks!
Dave
reply other threads:[~2006-06-23 18:28 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=DCC1EEDFB1AB0040BF64751002EA665E1040934B@emss03m09.us.lmco.com \
--to=david.a2.smith@lmco.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).