X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 26 May 2010 13:56:15 -0400 Message-ID: Subject: Re: Native 64 bit. From: NightStrike To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 1:13 PM, 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. You know about http://mingw-w64.sf.net/ right? I sure hope so. If not, please ask me :) What is your end goal? Porting cygwin to win64 is a huge task, and it might not be necessary. We can already cross compile from cygwin32 to native win64 on a win64 system. Is that all you need? If you really are going to port cygwin, you should start by porting all the dependencies. -- 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