Jason Tishler wrote: >>Is that a deficiency of cygwin as a whole, or just related to the way >>my DLL was built?) >> > >Cygwin's fork() attempts to load DLLs in the child in the same location >as in the parent. If it fails, then the child aborts. > Other than the lack of someone writing the code, is there any reason why fork() can't automagically try another location? Is this even possible? Or does it go against the way Cygwin/Windows works?
Cheers, Nicholas
