The problem is resolved in the snapshot as well. Thanks again.
LC
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Corinna Vinschen cygwin.com> writes:
>
> On Mar 8 11:33, Corinna Vinschen wrote:
> > You're trying this on a 64 bit machine, right? Call `peflags -l0' on
> > your executable and try again. It should work.
>
>
> Well, I think I have a solution now. I applied a patch to CVS and
> I'm just ge
On Mar 8 11:33, Corinna Vinschen wrote:
> On Mar 8 01:35, Lee Collier wrote:
> > Jon Clugston gmail.com> writes:
> > >
> > > Don't know if it will fix your problem, but you cannot just create a
> > > mutex on the stack and call "lock" on it. You must initialize it with
> > > "pthread_mutex_ini
On Mar 8 01:35, Lee Collier wrote:
> Jon Clugston gmail.com> writes:
> >
> > Don't know if it will fix your problem, but you cannot just create a
> > mutex on the stack and call "lock" on it. You must initialize it with
> > "pthread_mutex_init()".
> >
> > Jon
> >
> >
> Good catch. I missed t
Jon Clugston gmail.com> writes:
>
> Don't know if it will fix your problem, but you cannot just create a
> mutex on the stack and call "lock" on it. You must initialize it with
> "pthread_mutex_init()".
>
> Jon
>
>
Good catch. I missed that in my haste to scrounge a sample pgm together. With
On Wed, Mar 7, 2012 at 1:51 PM, Lee Collier wrote:
> Hello,
>
> I'm new to cygwin and ran into an anamoly with calling ioctl() that
> I've not experienced on Linux. It appears that ioctl() behaves as
> expected when it is called from the main thread; however, it does not
> when called from a thread
6 matches
Mail list logo
