X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 26 May 2010 13:25:57 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Native 64 bit. Message-ID: <20100526172557.GA3908@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 Wed, May 26, 2010 at 01:13:52PM -0400, Jason Pyeron wrote: >First off, I do not know if we will ever finish this attempt, but we will start >and try. > >We would like to compile cygwin for 64 bit native operation. Our office is >switching to all 64 bit systems. > >Reading: >http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin > >Could someone confirm that the gcc, make, perl, and cocom should be be cygwin >(32 bit) versions or should they be "windows" versions? > >Also should I move this to the cygwin-developers list? > >The fun will start 7-June-2010, wish us luck. Wow, if you're asking questions like this, you have a long road ahead of you. It doesn't matter what you use. Just use whatever works. 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