On Jul 11 09:52, Corinna Vinschen wrote: > On Jul 9 23:02, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > > > This was fixed in Cygwin 3.3.0, as the announcement of the latter stated: > > > > Thanks! So maybe it is time to upgrade... after all LOL > > > > > But you can still run a parallel Cygwin installation > > > > I tried that before... And it did not work out well. Unless it's a VM, > > there's a small but real chance that at some point they are to get > > intertwined, > > This must have been very long ago. For a long time, Cygwin's path > handling and shared memory interaction between Cygwin processes is > based on the installation path of the Cygwin DLL a process is running > under. A Cygwin process running under a Cygwin DLL from path A uses > different default Windows PATH and different shared memory names than a
make that "different names for all shared objects" > process running under Cygwin DLL from path B. Keeping Cygwin > installations separate just requires never to run processes from > installation A under Cygwin DLL B. > > > > and then ... it's quite a mess (learned that the hard way, unfortunately). > > It really isn't. Only if you start to mix paths from two parallel > Cygwin installations inside the same shell session, which should be > easy to avoid. > > > Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
