public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Phil Frisbie, Jr." <phil@hawksoft.com>
To: Max TenEyck Woodbury <mtew@cds.duke.edu>
Cc: pthreads-win32@sourceware.cygnus.com
Subject: Re: _POSIX_SOURCE?
Date: Thu, 02 Aug 2001 14:41:00 -0000	[thread overview]
Message-ID: <3B69C76D.8DDAA6B9@hawksoft.com> (raw)
In-Reply-To: <3B699D81.69208419@cds.duke.edu>

Unfortunately, it is not that simple...

First, pthread.h includes windows.h and winsock.h for some defines.

Second, the Windows headers do not recognize _POSIX_SOURCE, but they do
recognize _POSIX_ , but that just fixes some things like file IO and it does not
block non POSIX functions.

You can either closely look at the source code line by line looking for non
POSIX functions, or take your source code over to a Linux, Solaris, or other
POSIX system and 'try' to compile it :) That is how I am porting the GLTrace DLL
from Windows to Linux/Solaris.

Max TenEyck Woodbury wrote:
> 
> I have (a part of) an application that I have working under
> WinXX that I want to move to several other environments. I figured
> that making it POSIX compliant would be the first step in moving
> it, so I stripped the windows headers, inserted the corresponding
> POSIX headers and defined _POSIX_SOURCE and included the PT32 include
> directory in the header search path. I expected the compiler
> to point out all the function calls and definitions that I needed
> to change.
> 
> NADA!
> 
> No errors. And there should be loads of 'em!
> 
> Help?
> 
> mtew@cds.duke.edu


Phil Frisbie, Jr.
Lead Developer, Hawk Software
http://www.hawksoft.com

  reply	other threads:[~2001-08-02 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 11:29 _POSIX_SOURCE? Max TenEyck Woodbury
2001-08-02 14:41 ` Phil Frisbie, Jr. [this message]
2001-08-02 14:59   ` _POSIX_SOURCE? Max TenEyck Woodbury

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=3B69C76D.8DDAA6B9@hawksoft.com \
    --to=phil@hawksoft.com \
    --cc=mtew@cds.duke.edu \
    --cc=pthreads-win32@sourceware.cygnus.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).