On Wed, Aug 22, 2012 at 12:46 AM, Simon Josefsson wrote:
> FYI, this may be of interest:
>
> http://sources.redhat.com/pthreads-win32/
see more fix here also:
https://github.com/GerHobbelt/pthread-win32/commits/master/
> Maybe it would make sense to offer something like that i
FYI, this may be of interest:
http://sources.redhat.com/pthreads-win32/
Maybe it would make sense to offer something like that in gnulib, so
that you can write against pthread API and have it work with native
Windows threads. I haven't looked at the implementation though.
/Simon
The shipped with pthreads-win32 is horribly broken; it
pollutes the global namespace with more than just bad macros (such as
the incorrect macros for asctime_r that we are already working around in
time.in.h), but also by including a specific to how
pthreads-win32 was configured, which may clash
Eric Blake wrote:
> Yes, looks reasonable
Thanks for the review. Pushed it.
Bruno
of where we
would be including , so we can be reasonably sure that it is
the likely-broken pthread.h from pthreads-win32.
> +/* The pthread-win32 also defines a couple of broken macros. */
s/pthread-win32/pthreads-win32/
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt virtu
Hi Eric,
> # if ! @TIME_H_DEFINES_STRUCT_TIMESPEC@
> # if @SYS_TIME_H_DEFINES_STRUCT_TIMESPEC@
> # include
> +# elif @PTHREAD_H_DEFINES_STRUCT_TIMESPEC@
> +# include
> # else
Now, gnulib - not the user's code - is including this , of
which you just determined that it contains a broke
When using the pthreads-win32 library with mingw, struct timespec
is available in . Meanwhile, that header has some
rather buggy macros for localtime_r and gmtime_r that interfere
with proper gnulib replacement header actions.
Tested in a cross-compilation environment: Fedora 13 with mingw32-gcc
We have an application on MinGW that uses pthreads-win32, and I haven't
had any problems.
I did need to pick up a Posix timer package as well for our application,
since MinGW doesn't have one. I used the now obsolete LinuxThreads
timers, which make use of pthreads, and it works withou
referrable
to use the POSIX API rather than some other API; this is another reason
why your library is interesting for gnulib.
How well tested is pthreads-win32? Is there a list of packages that uses it?
Can it be built on mingw with pretty clean, standard Makefile infrastructure?
Does building
Bruno Haible <[EMAIL PROTECTED]> writes:
> Just stumbled across this: http://sourceware.org/pthreads-win32/
It's a bit weird that you'd stumble across this only after so much time.
Are there some other issues with it that we don't know about? (Yes, I
know, sorry, a dum
Hi,
Just stumbled across this: http://sourceware.org/pthreads-win32/
It's a package that implements the POSIX multithread API on top of the
Win32 API. Looks quite mature. License is LGPL, but copyright holder is not
the FSF.
Compared to the 'lock' and 'tls' modules tha
11 matches
Mail list logo