[ITP] mingw-w64

[JonY]

On 7/6/2010 01:38, Charles Wilson wrote:
> OK, a bit further along.  With the recently posted patch to cygport:
> http://cygwin.com/ml/cygwin/2010-07/msg00117.html
>
> AND the attached patch to your .cygport script, I get a bit further with
> the install step. It completes without error (but I still have the
> warning about the missing cygwin-specific README file, of course).
>
> However, the DLLs don't appear to be in the correct locations.
>
> opt/mingw64/bin/libobjc-2.dll
> opt/mingw64/bin32/libgcc_s_sjlj-1.dll
> opt/mingw64/bin64/libgcc_s_sjlj-1.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libgfortran-3.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libgomp-1.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libssp-0.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/32/libstdc++-6.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/libgfortran-3.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/libgomp-1.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/libssp-0.dll
> opt/mingw64/lib/gcc/x86_64-w64-mingw32/4.6.0/libstdc++-6.dll
>
> Now, the DLLs buried down in the 4.6.0/ directory I can see (it appears
> to be a mistake, but that IS where they "normally" go...even if we
> choose to put them in toplevel bin32 and bin64 dirs instead.)  It looks
> like the cygport is missing some 'mv' commands.
>
> But how the heck did libobjc-2.dll get into the "regular" bin/ dir? And
> why is there only one version of it?

Hi,

I had a thinko, thanks for the patch. Yeah, cygport moves the libtool 
dlls around.

I will recheck on the README file and libobjc-2, I thought I patched up 
the configure file.