</wild stab in the dark> Uhmmm....could this actually be due to the *known* memory leak in ld.exe? (When I see 'make', I think 'compile and link' === 'gcc and ld') Search the archives for information on this problem in binutils (I think Ralf Habacker posted the bug report). He's currently trying to track it down and squish it with help from the binutils mailing list. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
- vfork problems on Win98 -- is there a fix? Andrew Kalman
- Re: vfork problems on Win98 -- is there a fix? Andrew Kalman
- Re: vfork problems on Win98 -- is there a fix? Christopher Faylor
- Re: vfork problems on Win98 -- is there a fix? Charles Wilson
- Re: vfork problems on Win98 -- is there a fix? Andrew Kalman
- Re: vfork problems on Win98 -- is there a fix? Charles Wilson
- Re: vfork problems on Win98 -- is there a fix? Andrew Kalman
- Re: vfork problems on Win98 -- is there a fix? Christopher Faylor
- Re: vfork problems on Win98 -- is there a fix? Andrew Kalman
- Re: vfork problems on Win98 -- is there a fix? Christopher Faylor
- Re: vfork problems on Win98 -- is there a fix? Ashok Vadekar
- Re: vfork problems on Win98 -- is there a fix? Christopher Faylor
- Re: vfork problems on Win98 -- is there a fix? Christopher Faylor
- Re: vfork problems on Win98 -- is there a fix? Andrew Kalman