running cygwin apps(gcc etc.) under wine

[Chris Morgan]

Ahh, very cool.  Is there anything we can do to keep cygwin from replacing 
wines/libc's fork with its own and presumably fix this problem?

Chris


On Tuesday 17 December 2002 10:34 pm, Dmitry Timoshkov wrote:
> <chrismorgan at rcn.com> wrote:
> > Trying to run my work related code build process under wine results in
> > some failures with cygwin's gcc.  Even with a simple hello
>
> world.c file and 'gcc -o test test.c' I get:
> >       0 [main] gcc -134958416 sync_with_child: child 134963016(0xB0) died
> > before initialization with status code 0x1 2599 [main] gcc -134958416
> > sync_with_child: *** child state waiting for longjmp 1335488 [main] gcc
> > -134958416 sync_with_child: child 134968376(0xC0) died before
> > initialization with status code 0x1 1337536 [main] gcc -134958416
> > sync_with_child: *** child state waiting for longjmp 3711485 [main] gcc
> > -134958416 sync_with_child: child 134969736(0xD0) died before
> > initialization with status code 0x1 3713593 [main] gcc -134958416
> > sync_with_child: *** child state waiting for longjmp 8125556 [main] gcc
> > -134958416 sync_with_child: child 134970152(0xE0) died before
> > initialization with status code 0x1 8127752 [main] gcc -134958416
> > sync_with_child: *** child state waiting for longjmp gcc: vfork: Resource
> > temporarily unavailable
> >
> > Any ideas why this is occuring?  Is this due to issues with pthreads?
>
> Very likely this is due to the implementation of 'fork' in cygwin.