X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-50.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_YG X-Spam-Check-By: sourceware.org Subject: Re: cygport patch: suppress libtool fixup step From: "Yaakov (Cygwin/X)" To: cygwin In-Reply-To: <4C3215FC.3010309@cwilson.fastmail.fm> References: <4C3215FC DOT 3010309 AT cwilson DOT fastmail DOT fm> Content-Type: text/plain; charset="UTF-8" Date: Tue, 06 Jul 2010 02:48:57 -0500 Message-ID: <1278402537.5784.8.camel@YAAKOV04> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Mon, 2010-07-05 at 13:27 -0400, Charles Wilson wrote: > JonY needs to suppress the "libtool fixup" postinstall step when > packaging the mingw64 gcc. He may or may not need to fixup his .la > files, BUT -- given that we're talking about gcc here, AND his cross > compiler goes somewhere other than /usr...it's likely that whatever > "fixing up" he needs to do, will be specific to that package and likely > unable to re-use the more generic fixup code. I am working on proper cross-compiler support within cygport now: * cygconf handling of build/host/target; * modifying the libtool fixup for different targets; * handling conflicting files between native and cross-compiler/ed packages (to allow prefix=/usr). Regarding libtool fixups: am I correct that on mingw32/64 platforms, deep non-module libs still need to be relocated to remove the ../bin (IOW put the DLL alongside the .la)? Yaakov -- 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