Aye i also have been getting that problem, i got around it by hand
setting paths in my build script so that the mingw32 directories came
first before the windows system directories. In most cases this works
but i have seen a few edge cases that prove that it is not allways
enough. In those
Based on what you have said, is this right thinking:
In other words, ldd in particular and run-time loading of libs in
general inside mingw is not "hermetically sealed off" from any influence
by Windows. Its behavior is affected not only by what the msys/mingw
environment wants to do with DLLs,
On Tue, Mar 22, 2016 at 11:58 AM, Alexpux wrote:
>
> 22 марта 2016 г., в 13:45, Matthew A. Postiff
> написал(а):
>
> Thanks all for the ideas.
>
> I was not as clear as I could be when I showed the very short PATH. Indeed
> that may be overdoing it, but
> 22 марта 2016 г., в 13:45, Matthew A. Postiff
> написал(а):
>
> Thanks all for the ideas.
>
> I was not as clear as I could be when I showed the very short PATH. Indeed
> that may be overdoing it, but zlib1.dll was loaded from the wrong place even
> though my path
Thanks all for the ideas.
I was not as clear as I could be when I showed the very short PATH.
Indeed that may be overdoing it, but zlib1.dll was loaded from the
wrong place even though my path was that short. Apparently,
something in Windows is choosing to find