running cygwin apps(gcc etc.) under wine

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?

Thanks,
Chris

[Sylvain Petreolle]

strange... did you try running cygwin precompiled binaries ?
some commands seems to work.

maybe im not seeing something but all shells I try to execute with wcmd
just logout immediately when you run it. otherwise other commands seem
to be fine.

if gcc is creating subprocesses, I have the same issue with shells.
they try to execute some external commands and fail.

maybe the whole cygwin procedure to run cygwin binaries doesnt work
with our code.
 --- [e-mail] a écrit : > 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?
>
> Thanks,
> Chris

=====
Sylvain Petreolle
[e-mail] 
Fight against Spam ! http://www.euro.cauce.org/en/index.html
ICQ #170597259

"Don't think you are. Know you are." Morpheus in Matrix, chapter 15.

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Dmitry Timoshkov]

 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.

--
Dmitry.

[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:
>  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.

[Dimitrie O. Paun]

On December 18, 2002 12:22 am, Chris Morgan wrote:
> 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?

I would say: why doesn't cygwin's fork work on top of wine? I'd say
that needs to be fixed, if possible. Using the native fork should
be fairly simple, but it does defeat the purpose a bit...

[Dmitry Timoshkov]

"Chris Morgan"  wrote:
> 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?

I'm afraid it's impossible to replace cygwin's fork by an one from libc.
Cygwin makes some assumptions about "environment" where it runs and
accordingly patches virtual memory of a newly created process to mimic
fork behaviour.