Brian Dessent wrote:
"Aaron W. LaFramboise" wrote:
I don't really see any compelling reason that win32 threads shouldn't
work on Cygwin. As far as I know, nothing about this choice is
ultimately exposed to the user. In fact, Win32 threads are quite likely
to yield superior performance anywher
"Aaron W. LaFramboise" wrote:
> I don't really see any compelling reason that win32 threads shouldn't
> work on Cygwin. As far as I know, nothing about this choice is
> ultimately exposed to the user. In fact, Win32 threads are quite likely
> to yield superior performance anywhere where it matte
Brian Dessent wrote:
Jesper de Jong wrote:
/home/jesper/gcc-4.1.2/configure --enable-threads=win32
Where do people keep getting this idea that Cygwin uses win32 threads?
It doesn't, and you've most likely built a compiler that is subtly
broken in some way. Cygwin uses pthreads, this sh
Hello Brian,
Maybe because the configuration instructions:
http://gcc.gnu.org/install/configure.html
suggest that there is a choice and if you don't know better you will
think "I'm using Windows so I can use win32 threads".
Jesper
2007/4/5, Brian Dessent <[EMAIL PROTECTED]>:
Jesper de Jong wro
On 05 April 2007 13:52, Brian Dessent wrote:
> Jesper de Jong wrote:
>
>> /home/jesper/gcc-4.1.2/configure --enable-threads=win32
>
> Where do people keep getting this idea that Cygwin uses win32 threads?
> It doesn't, and you've most likely built a compiler that is subtly
> broken in some w
Jesper de Jong wrote:
> /home/jesper/gcc-4.1.2/configure --enable-threads=win32
Where do people keep getting this idea that Cygwin uses win32 threads?
It doesn't, and you've most likely built a compiler that is subtly
broken in some way. Cygwin uses pthreads, this should be
--enable-threads
I successfully build gcc-4.1.2 on Cygwin running on Windows XP
Professional with SP2.
Output from running /home/jesper/gcc-4.1.2/config.guess:
i686-pc-cygwin
Output of 'gcc -v':
Using built-in specs.
Target: i686-pc-cygwin
Configured with: /home/jesper/gcc-4.1.2/configure
--enable-th
