X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
X-Mail-Handler:	MailHop Outbound by DynDNS
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18zMUYUW29CA0zahoCONJXG
Date:	Sat, 26 May 2012 17:16:51 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 64-bit Cygwin packages (was RE: Is the Latest Release of Cygwin supported on Windows Server 8/2012)
Message-ID:	<20120526211651.GE9878@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<70952A932255A2489522275A628B97C31348C73D AT xmb-sjc-233 DOT amer DOT cisco DOT com>
MIME-Version:	1.0
In-Reply-To:	<70952A932255A2489522275A628B97C31348C73D@xmb-sjc-233.amer.cisco.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Tue, May 22, 2012 at 01:15:24PM -0700, Matt Seitz (matseitz) wrote:
>> From: Cygwin-L: On Behalf
>> Of marco atzeri
>> 
>> Until we work and deploy a 64bit cygwin1.dll the idea to build any 64 bit
>> cygwin program is pure academic and not very useful.
>> 
>> If you want to propose patches for 64 bit cygwin cygwin-developers is the
>> right mailing list.
>
>Sorry if I wasn't clear.  That's exactly what I was trying to suggest:
>if someone wants a 64-bit Cygwin package, they should start by building
>such a package themselves, including any necessary changes to
>cygwin1.dll.  Once you've got a working example, bring your results and
>patches to the maintainers.

No, sorry.  Please don't do this.  Something this major requires serious
coordination, not a 10,000 line patch.

So, if someone seriously wants to do this then join the cygwin-developers
list to discuss it.  Don't start a discussion unless you want to actually
do some work though.  We're not keenly interested in your ideas unless you
are thoroughly versed in how Cygwin works now and are willing to work to
getting things working with a 64-bit compiler.

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

- Raw text -