X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 6 Aug 2008 21:35:23 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: ABI unification Message-ID: <20080807013523.GA25033@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1218043716.30536.ezmlm@cygwin.com> <005501c8f81b$575346e0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Aug 06, 2008 at 08:48:18PM -0400, Francis Litterio wrote: >Dave Korn wrote: >>>Perhaps this can be "fixed" for any non-x86 Cygwin port? >>The very concept of a non-x86 Cygwin port is meaningless nonsense. You >>need to do a bit more homework. I suggest you start by reading the >>first sentence on the first page at http://cygwin.com/. > >Doesn't Windows Server 2003 run on Intel's Itanium processor? >Technically, that's a non-x86 Windows platform. Would it help if I vowed not to port Cygwin to the Itanium? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/