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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=udxGpTqdr+XUIFn9eCrnOa8vY1iZ7iNLbJCVLciigY+btmG8oaY9h
	VUrMGTjkZTpg0/zX4oNl8rmyxFtL0ujFZoLWBqQ8VRQ7jGIdqkAXpeMed1pgB5B4
	qQ541ALhmqpPbUhdGRpuHhsqgTs2DWSeE+IIVzVW30NXxgj7SQ8boQ=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=GkYdzpkILIB488iyVNyxALCGNjM=; b=M9ENnTspzfvV84ahfwXrhQm3H/A4
	6H4CktBHYOaDRxpBUSjeDSSqV0u0D5OkEGNF9ApxtFfs5QZzZm7hzcMyyRygLVAi
	bVS94h8YPIRDa2l5/PIR5bVFXZ44me9LRQ1be5Wmw3Nluk71rB4p4rR0YqM/MEpL
	ihssxIJuDl8TQRg=
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=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+So+eFEnzg7WSZLc2tM9r6
Date: Wed, 25 Jun 2014 10:12:47 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: developing 32-bit and 64-bit in a shared environment
Message-ID: <20140625141247.GC5212@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <0D835E9B9CD07F40A48423F80D3B5A702E7D8188 AT USA7109MB022 DOT na DOT xerox DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7D8188@USA7109MB022.na.xerox.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, Jun 25, 2014 at 01:04:24PM +0000, Nellis, Kenneth wrote:
>I have happily been using 32-bit Cygwin for years, developing 
>shell/perl scripts and C/C++ software. Some of the users that 
>I support have upgraded to 64-bit Cygwin, and so my 32-bit C/C++ 
>binaries no longer work for them. That has forced me to adopt 
>64-bit Cygwin, which I've installed on the same machine as my 
>32-bit Cygwin. I need to maintain both environments in parallel.
>
>Now, I want to share my Cygwin $HOME directory between the two 
>environments.  I already keep my binaries in $HOME/bin/$(arch) 
>and $HOME/lib/$(arch), so they are covered. And, of course 
>/usr/bin has to continue to point to the separate Cygwin 
>environments. 
>
>I didn't see what I was looking for in the FAQ or User Guide, 
>so am looking for advice from the list.

I think you're looking for this:

https://cygwin.com/cygwin-ug-net/using.html#using-pathnames

i.e., use /etc/fstab to mount your home directory to the same
place in both environments.

cgf

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