Ray Donnelly <[email protected]> writes: > This has nothing to do with LIB. It's the DLL loader on Windows, not build > time stuff. > > Use process hacker 2. Search for DLL handles straight after boot up. See > which processes loaded the zlib DLL. Find alternatives to that software, > maybe MSYS2 has some? Uninstall the offending software. Delete the DLL if > uninstalling didn't do that for you. Install the alternatives. Be happy. > This is entirely at your own risk. If it goes wrong, you won't be happy I'm > afraid.
You seem to imply that if a process loads a dll (let's call it foo.dll), then other processes will load that same foo.dll even if there is a different one on the directory where their executables are. Just in case, I will remark that this is not correct. There can be multiple copies of foo.dll on the system and the correct one will be picked if the programs are correctly installed. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
