On Mon, Mar 21, 2016 at 6:41 PM, Matthew A. Postiff <[email protected]>
wrote:
> Do you mean more clean than
>
> $ printenv | grep PATH
> PATH=/mingw32/bin:/usr/local/bin:/usr/bin:/bin
That may be overdoing it, you might find yourself running some windows
utilities
that will need /c/windows. In /etc/profile I use the following
>
C=`/usr/bin/cygpath $SYSTEMDRIVE`
wpath="$C/Windows:$C/Windows/system32:$C/Windows/system32/Wbem"
MSYS2_PATH="/usr/local/bin:/usr/bin:/bin"
and then have variations built with these, depending on MSYSTEM. Because
of perl,
more gets added at the end so for MINGW32
PATH=/mingw32/bin:/opt32/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows:/c/Windows/system32:/c/Windows/system32/Wbem:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
>
>
> For the record...I had a zlib1.dll in C:\Windows\SysWOW64\ on two
different
> computers. On the one, it caused a libxml check in configure to fail. The
> check returned 127--library missing--but it wasn't libxml2-2 that was
> missing! On the other, it caused gcc to be unable to write output. It
> returned 1 and did not give any output. When I deleted zlib1.dll, these
odd
> problems disappeared.
>
I have 0 zlib* files anywhere beneath c:/windows, 67 of them beneath
c:/msys64,
including C:/msys64/mingw32/bin/zlib1.dll
C:/msys64/mingw32/lib/pkgconfig/zlib.pc
C:/msys64/mingw32/include/zlib.h
C:/msys64/mingw64/bin/zlib1.dll C:/msys64/mingw64/include/zlib.h
..
>> >
>> > Digging around I found another problem with conftest.exe:
>> >
>> > $ ldd conftest.exe | grep zlib
>> > zlib1.dll => /c/Windows/system32/zlib1.dll (0x10000000)
>> >
>> > There are two problems with zlib1.dll:
>> >
>> > 1. /c/Windows/system32/zlib1.dll DOES NOT EXIST on my system. I found
>> > the DLL instead at /c/Windows/SysWOW64/zlib1.dll
>> > 2. That library shouldn't have been linked. It should have linked to
>> > /mingw32/bin/zlib1.dll
>> >
>> > Any ideas on what is wrong, or what I'm doing wrong?
>> >
Somebody at sometime has decided that zlib1.dll needed to be linked via
the WOW system.
That seems really sick to me, maybe its a virus. If zlib1 is needed then
it should be included in the
directory containing the .exe; if you have installed a program that doesn't
want its own directory (i.e. a virus)
and yet remain as small and insignificant as possible (i.e. a virus) then
it might install such support
files in obscure locations such as that.
You asked for ideas, that's all it is.
------------------------------------------------------------------------------
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
