This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] mingw-w64

On 05/07/2010 18:38, Charles Wilson wrote:

> 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.

  Should be handled by passing -bindir=$bindir to libtool rather than mv'ing
them after "make install".

> But how the heck did libobjc-2.dll get into the "regular" bin/ dir? And
> why is there only one version of it?

  I forgot about libobjc when adding -bindir support to GCC(*, didn't make it
in time for 4.5 branch.  Guess I should see about backporting that for 4.5.1.


(*) -

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]