delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/07/08/13:02:54

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,TW_YG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4C36098F.8030109@gmail.com>
Date: Thu, 08 Jul 2010 18:23:27 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT gmail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygport patch: suppress libtool fixup step
References: <4C3215FC DOT 3010309 AT cwilson DOT fastmail DOT fm> <1278402537 DOT 5784 DOT 8 DOT camel AT YAAKOV04> <4C337C6E DOT 2080003 AT cwilson DOT fastmail DOT fm>
In-Reply-To: <4C337C6E.2080003@cwilson.fastmail.fm>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin 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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019