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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=uG/FoQv37MRwkHQN
	acYisnXx926E6RG49A7oTiywepta2f8U3PbJgtBFt9R5iNybcGeu7Fe9U8rKJ2u/
	br8NatfHlae2kD5V0XkQHdfXtsLVV6PXpQM8yshgaUTWE8sn5CdYlH6Hc87O8HqH
	lHiZ0+dM/fBHNACupgy9BAfhYzE=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=dKx065XlHs5djdiYWGJbwz
	1hKTk=; b=aX2oQLitKa2tjKpcTq5NUu0O2YCxZa+GxoXYpIwFWe9LyBANuCb8AH
	1Y6tGspKzeBvsBNYq8kCe7mWuxaoE/k6ZQ7VCL1GDe5jSvUhjOCC1PhfhdRUWTLe
	WeZh5XqNTurjV9Tzibq6XerNFrMeNlXKqtvBxAdHWQ31yvFvHIhhk=
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=-2.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1369, H*i:sk:a620774, H*MI:sk:a620774, H*f:sk:a620774
X-HELO:	filter02.dlls.pa.frontiernet.net
X-Previous-IP:	96.247.120.186
Subject:	Re: Attempting to build cygwin1.dll
To:	Cygwin mailing list <cygwin AT cygwin DOT com>
References:	<bc4cc28f-6ddb-d60a-1c5c-faa623bc6a9b AT frontier DOT com> <a6207748-79bc-36ad-1885-2b6b04340b35 AT cygwin DOT com>
From:	Nirgendsdorf <nirgendsdorf AT frontier DOT com>
Message-ID:	<a6eb430a-950d-41bc-6360-3a346dd3069e@frontier.com>
Date:	Tue, 30 Aug 2016 00:34:21 -0700
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version:	1.0
In-Reply-To:	<a6207748-79bc-36ad-1885-2b6b04340b35@cygwin.com>
X-IsSubscribed:	yes

On Tue, 30 Aug 2016 01:04:23 -0500, Yaakov Selkowitz wrote:
> On 2016-08-29 21:21, Nirgendsdorf wrote:
>> I am sure I have all the support libraries for the 32-bit mingw
>> gcc installed and working (I've built software with it). Does this
>> mean a 64-bit machine is required to build the Cygwin DLL?
>
> No; the mingw64 cross-compiler is required for building
> cyglsa64.dll.

Thank you, Yaakov. The nomenclature that has developed for the 32-bit 
and 64-bit builds of the mingw toolchain can be confusing to say the 
least, so I have to ask which "mingw64" cross-compiler you are talking 
about? mingw64-i686 (which I suppose is the 32-bit version), or 
mingw64-x86_64?

In any case, there seems to be no configure options allowing the user to 
choose which newlib-cygwin components to build. lsaauth becomes an issue 
only because it stops the scripts before cygwin1.dll is built. I may be 
wrong, but I think that libm and the Cygwin dll are the only two 
components of the package that will give me a significant performance 
gain if I can build them architecturally specific with `gcc 
-march=native -mfpmath=sse.' I am not sophisticated enough to rewrite 
the scripts, nor to build cygwin1.dll manually as described in the 
article I mentioned. I would sure appreciate it if there were some means 
within my abilities to build it.

Jeff

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