Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Igor Pechtchanski
Well, either that or keeling over. I think I'd better change it to a more truthful "April", though... Igor On Fri, 28 Feb 2003, Randall R Schulz wrote: > Igor, > So tell the truth. Are you really undergoing a thesis defense next month? > Randall > > At 13:16 2003-02-28, Igor Pechtchanski

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Randall R Schulz
Igor, So tell the truth. Are you really undergoing a thesis defense next month? Randall At 13:16 2003-02-28, Igor Pechtchanski wrote: On Fri, 28 Feb 2003, Christopher Faylor wrote: > On Fri, Feb 28, [EMAIL PROTECTED]:15:08PM -0500, Igor Pechtchanski wrote: > >On Fri, 28 Feb 2003, Corinna Vinsch

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Christopher Faylor
On Fri, Feb 28, 2003 at 04:16:32PM -0500, Igor Pechtchanski wrote: >TY [Thank you], CGF! THISU [This honor is surely undeserved], IMHO, but >IWTTLUTI [I will try to live up to it]. AAFS [As a first step], IWLTP [I >would like to propose] establishing the OLOCA [Official List of Cygwin >Acronyms].

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Igor Pechtchanski
On Fri, 28 Feb 2003, Christopher Faylor wrote: > On Fri, Feb 28, [EMAIL PROTECTED]:15:08PM -0500, Igor Pechtchanski wrote: > >On Fri, 28 Feb 2003, Corinna Vinschen wrote: > > > >> On Fri, Feb 28, [EMAIL PROTECTED]:34:04PM +, Steven O'Brien wrote: > >> > By the way, the current CVS has a proble

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Christopher Faylor
On Fri, Feb 28, 2003 at 01:34:04PM +, Steven O'Brien wrote: >Hi >I think I've found the problem with dlopen()/fork() on Win ME as >reported in >http://cygwin.com/ml/cygwin/2003-02/msg02221.html >If I'm right, it also applies to win 95/98. > >in dll_init.cc: (dll_list::load_after_fork) a call is

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Christopher Faylor
On Fri, Feb 28, 2003 at 01:15:08PM -0500, Igor Pechtchanski wrote: >On Fri, 28 Feb 2003, Corinna Vinschen wrote: > >> On Fri, Feb 28, [EMAIL PROTECTED]:34:04PM +, Steven O'Brien wrote: >> > By the way, the current CVS has a problem with unix sockets - they are >> > vey slow - like several m

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Igor Pechtchanski
On Fri, 28 Feb 2003, Corinna Vinschen wrote: > On Fri, Feb 28, [EMAIL PROTECTED]:34:04PM +, Steven O'Brien wrote: > > By the way, the current CVS has a problem with unix sockets - they are > > vey slow - like several minutes to get a simple message through in > > some cases. > > Simple tes

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Corinna Vinschen
On Fri, Feb 28, 2003 at 01:34:04PM +, Steven O'Brien wrote: > By the way, the current CVS has a problem with unix sockets - they are > vey slow - like several minutes to get a simple message through in > some cases. Simple testcase[tm]? Corinna -- Corinna Vinschen Plea

Re: bug report - DLL failure on win ME with gcc-3

2003-02-28 Thread Steven O'Brien
Hi I think I've found the problem with dlopen()/fork() on Win ME as reported in http://cygwin.com/ml/cygwin/2003-02/msg02221.html If I'm right, it also applies to win 95/98. in dll_init.cc: (dll_list::load_after_fork) a call is made to LoadLibraryEx (d.name, NULL, DONT_RESOLVE_DLL_REFERENCES); A