Re: cygport patch: suppress libtool fixup step

[Dave Korn <dave dot korn dot cygwin at gmail dot com>]

On 06/07/2010 19:56, Charles Wilson wrote:

> To deal with the duplicated DLLs from two different multilib mingw64
> toolchains (one that supports -m32 and -m64, but *defaults* to -m64, and
> one that also supports -m32 and -m64, but *defaults* to -m32), the DLLs
> are actually installed into a completely different directory outside the
> $triple area.
> 
> The 64bit dlls are moved manually to $special_prefix/bin64/ and
> $special_prefix/bin32 -- because these DLLs are "shared" by both
> toolchains in the specificed -mXX mode, so the "deep" directory inside
> one toolchain's private area or the other, are both inappropriate.

  In what way are these DLLs "shared"?  They are target libraries, they aren't
linked into the cross-compiler itself, and applications built by the
cross-compiler don't link directly against the DLLs anyway, they have import libs.

> But...this is all handled manually, after 'make install'.

  I think it would be cleaner if the right -bindir settings were sent to
libtool during the build/install process.  This is PR40125(*), btw.  Which I'm
down to fix, I guess I'd better get on with it.

    cheers,
      DaveK
-- 
(*) - http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40125

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple