X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=b1sx3SYPnvg94Vn0/qd/++AdBlk0
	pSkJtc/89HJxUyIhvt2JEc7CR0S61RhuojZhm0Oeg4Mkd6WFhKgi8HLuCkiQqfft
	R5Y8YuUDlLhR/h7Ld9Vl38PkRK3BEkLsMBUkDTftoNbK/kd3c75QJggoHJSg6QTS
	P4o0o4+Nw4YGFqY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=L32B7kQauI9PB8haPSXiflWNQQY=; b=rC
	+wMgmLegFC8iO8mpwp5VLUZPTbyHuUR8f2uffLFSyujq8RuiQwYppbWI349Inulo
	yhu6X5SRoPQ7XZBnG8Em3PXZIVpUp0aqsr+8YNhsa7zZ+7V78tkDrczmHvKAuQBy
	Jc/7MRiQhNL7leVAQoB0+juTVP9PgiJeOw+rfRM34=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_05,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=D*us, H*r:qmail-ldap-1.03, installations, products
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 32 bit lib dirs on cygwin64, advice sought
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <942E9B22984F4DA8BBC52814E9069B43@black7>
Date: Tue, 31 May 2016 15:08:10 -0600
Message-Id: <4FBD4813-C8B2-4CD1-8EB3-BEC76C6BA8D7@etr-usa.com>
References: <942E9B22984F4DA8BBC52814E9069B43@black7>
To: The Cygwin Mailing List <cygwin@cygwin.com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u4VL8ZJ6009667

On May 29, 2016, at 6:30 PM, Jason Pyeron <jpyeron@pdinc.us> wrote:
> 
> I feel I am making things way too complicated.

Yes. :)

> I have a Makefile, which is building a static library [1] in both 32 and 64
> bit.

Don’t do that.  The 32-bit and 64-bit Cygwins are fundamentally incompatible:

  http://stackoverflow.com/a/18333049

If you must do 32- and 64-bit Cygwin development on a single machine, it’s best to have separate 32- and 64-bit Cygwin installations which do not share any files.

I’ll add one exception to that, which is that it is fine to share a tree for building packages with cygport between two Cygwins since it knows how to segregate the build products for you.  It is possible to do this by hand, too, but it’s enough of a hassle that you could easily skip a step and end up commingling binaries of different word size, causing yourself problems.
--
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


