UWIN not supported

UWIN not supported

[Paul Thomas]

Hi,

I read in the announcement (POSIX Threads (pthreads) for Win32) that  
UWIN is not supported. What does that mean exactly? Does it mean that  
the two won't work together or just that nobody wants to look into any  
problems?

If they don't work together, can anyone explain why? I mean is it just  
a question of routing signals or something more serious.

thanks,
Paul.

Re: UWIN not supported

[Ross Johnson]

Paul Thomas wrote:
> Hi,
>
> I read in the announcement (POSIX Threads (pthreads) for Win32) that 
> UWIN is not supported. What does that mean exactly? Does it mean that 
> the two won't work together or just that nobody wants to look into any 
> problems?
Hi Paul,

In the most general sense it means that I don't run the test suite 
against any UWIN build of the library before releasing revisions. 
Several years ago now, I wasn't able to get the UWIN environment up and 
running and haven't had the interest to spend more time on it. I'd be 
happy to change the ANNOUNCE file if someone is willing to confirm that 
the [pthreads-win32] test suite passes - or passes with known exceptions.

As you've indicated, signals don't work, nor does shared memory etc. and 
AFAIK UWIN would need to be made threads-aware for these to work as well.

I assume they have worked together at least superficially in the past, 
hence the UWIN sections in the source (contributed by David Korn at 
AT&T). But to what extent they worked together back then I don't know. 
With minimal effort, someone who knows UWIN internals could probably get 
it working well enough to get through the pthreads-win32 test suite, but 
real applications that also need what UWIN provides, e.g. signals, still 
may not work.

Not sure if this helps at all but, ultimately, IMO UWIN needs it's own 
pthreads routines as Cygwin has done.

Ross

>
> thanks,
> Paul.