X-Recipient:	archive-cygwin AT delorie DOT 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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=DEKs6LgolpRuvi29iosKOvEPaspjsnxSluIfOWoSsN0
	PJ/2sfKeAL5BHP4EM7VU+4bj5Hxo3k0eOvICzjAvX41CtS+EU50rwLxSaGI6FZan
	fmIkL7vHXaEi9clQ2ClkY4gzKRE/Ci1xapdFOUe5IHoUThNRVIYeUoYAvM8J9txE
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=1PVh6PxrXZl52NtsrXmWlrGiTrk=; b=Qyxek/0eFv3VmQktS
	2ixt+iSPScuXFMZb9OeMAy9SjTFz5W6kAF4pGbAUiLYJQ0VymddqXqOCYlwwqeys
	FyjBJfTvpxoWzuahYRbyjpA/t5s/1wxuXvWh7+1WLlOz/3KLA28+y2XAmEDEAkxG
	kf89lg7oUPNnGMM8zoWoRbdwcI=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ig0-f175.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=F7Oxcv2gP22vHcGoONz58FnvIXBB+/5kpejHPx8SB7c=; b=lrT9HNSy5WCc88miV/HYrc46e62y7yPrUyIM4nmLGRpD7mi29AGtaLAXbpn7gJDq6D WKlYL3w1K4SkliyHIn27Ngoi/Yf60Zqn85SefL/qmmBtXJx/wj0dI4WBlpNJffpF5AOu IgX7vdlRk/HMSMhIr9aB2ZsL6ZpkSEPEq4ne2eYXIMXLTqxMJSy6V4X7EbdJb5q++r0B YBKpXVzOkL9CCgMw4nTW8D6rcn3IuM6KSGgKuM3vnacus5/LXz8azFhqVk/yCO/1BWTD VuiZSplpLn+LFxALK497EnnW2nVWRX1uaiNaq8qeWfULm0nLwzt1CZ1x2iTxTN/IcEIA z0hQ==
X-Gm-Message-State:	ALoCoQkIS3QAUNSKIbYO9kxL4G0uyTuXV07g1ZC9NFdkY3ElINyoyFkOxnz31zSpfDqbk50mXzHx
X-Received:	by 10.43.180.133 with SMTP id pe5mr3878746icc.71.1398464949534; Fri, 25 Apr 2014 15:29:09 -0700 (PDT)
Message-ID:	<535AE1AE.7060205@breisch.org>
Date:	Fri, 25 Apr 2014 18:29:02 -0400
From:	"Chris J. Breisch" <chris DOT ml AT breisch DOT org>
User-Agent:	Postbox 3.0.9 (Windows/20140128)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 64-bit vs. 32-bit
References:	<CABn7SNaxsvGXsEjkQM6csfpbnBRRhds6g6ajQSy=MwErSLkx1A AT mail DOT gmail DOT com> <535AD731 DOT 8040809 AT etr-usa DOT com>
In-Reply-To:	<535AD731.8040809@etr-usa.com>
X-IsSubscribed:	yes

Warren Young wrote:
> On 4/25/2014 11:26, Tom Szczesny wrote:
>>
>> CYGWIN_NT-6.1-WOW64
>
> "WOW64" means 32-bit Windows emulated on top of 64-bit Windows.[1] This
> tells you that Cygwin is running inside that 32-bit environment.
>
[snip]
> You don't have to guess and hope, though. From 32-bit Cygwin:
>
> $ file /bin/ls
> /bin/ls: PE32 executable (console) Intel 80386 (stripped to external
> PDB), for MS Windows
>
> $ file /cygdrive/c/cygwin64/bin/ls
> /cygdrive/c/cygwin64/bin/ls: PE32+ executable (console) x86-64, for MS
> Windows
>
> file(1) saith sooth what what form of executable thou hast wrought.
>
> You might also find this piece enlightening: http://goo.gl/qv5ki7
>
>

That is enlightening. I have a rather different, and very non-standard 
setup, making use of $PROCESSOR_ARCHITECTURE. This environment variable 
is set in both 32-bit and 64-bit Cygwin. In the former, it's set to 
"x86" and in the latter, it's set to "AMD64".

So, I have my 64-bit Cygwin root set to C:/cygwin/AMD64, and my 32-bit 
Cygwin root set to C:/cygwin/x86. My package root for both is 
C:\cygwin\packages, and I have /home in both environments mounted on 
C:/cygwin/home.

I script all my builds, and the script I use sets the build directory 
always to build_${PROCESSOR_ARCHITECTURE}. In a similar way, my output 
files are named things like configure_${PROCESSOR_ARCHITECTURE}.out, 
make_${PROCESSOR_ARCHITECTURE}.out, etc.

But, as you mention in your SO response, I'd never dream of sharing 
/usr/local this way.

Oh, finally, I set the title of my mintty or xterm to contain 
${PROCESSOR_ARCHITECTURE} as well, so I don't forget where I am.

-- 
Chris J. Breisch

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