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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=fZ7yqjjc2Pu3Dey0ZBZRANDWycL2lIWvidOt7VxJO+u
	8zjN56UBrcq+BCR4ZCqIdLe2xZjrptn3Vs/YKEEH7855LTB7NvbbJeZWlWVq68d2
	kpKjnahowPS8BFvmZyDolHiFTFpDv7wKR86W5+6HFRB701ulNp03XYHbole13bJQ
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=P+n3GJBLEPXwHGPSn9GLWat06hU=; b=Hyl0FjIoA34e0O75O
	s26yt1l8xCP6hoYODeF4VawdkZoBsgu/Tx56HC0EsSBvmZF7UctaYXfV9XpQXwxf
	LMvnt9jPZ7ELT9kFvyisa1uGhTr1IFsMV5AutZa8F8l4vIcnJ0RbGHgtn9to8AIU
	D0e6VBmefm4kcOIMJc4P91yfRU=
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.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,SPF_NEUTRAL autolearn=no version=3.3.2
X-HELO:	out3-smtp.messagingengine.com
Message-ID:	<5239EC4C.7060904@cwilson.fastmail.fm>
Date:	Wed, 18 Sep 2013 14:09:16 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version:	1.0
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: cannot run setup64.exe without admin privileges (even if renamed foo.exe)
References:	<CAPw2spinsbSZaduOMJtgR6rkaoJA9s7rTm6LCwvWBCK9-kiN8A AT mail DOT gmail DOT com> <5231EEF4 DOT 6010407 AT users DOT sourceforge DOT net> <CAPw2sphgi3r6U=ZvUj7ywS1JYOgPY2f4spuDW8Frff5gUCsrtQ AT mail DOT gmail DOT com> <20130918174034 DOT GB2351 AT ednor DOT casa DOT cgf DOT cx> <CAPw2spi2cQMRid83Zg53d3QvaA9J=2=kBXet_0SHnZtOxmwjDg AT mail DOT gmail DOT com>
In-Reply-To:	<CAPw2spi2cQMRid83Zg53d3QvaA9J=2=kBXet_0SHnZtOxmwjDg@mail.gmail.com>

On 9/18/2013 1:53 PM, Frédéric Bron wrote:
>>> Is it possible to build setup64.exe from a 32bit cygwin?
>>
>> As previously mentioned, despite the subject, there is no such thing as
>> setup64.exe.  The makefile creates setup.exe.  The filename gets changed
>> when it gets uploaded to cygwin.com to either setup-x86.exe or
>> setup-x86_64.exe.
>
> do you mean I can only build the 32bit version on i686 bits and the
> 64bit version on x86_64 and in both case the binary is called
> setup.exe after running make?
> This means I cannot build the x86_64 version from a i686 cygwin. Is
> that correct?

No. setup.exe (either 32bit or 64bit) is a native windows application, 
and if you're trying to build it within cygwin, then you MUST use a 
cross compiler -- either i686-w64-mingw32 or x86_64-w64-mingw32. when 
configuring the build, just do:

configure --host=i686-w64-mingw32 --build=i686-pc-cygwin ....
to build 32bit setup.exe from 32bit cygwin

configure --host=x86_64-w64-mingw32 --build=x86_64-pc-cygwin ....
to build 64bit setup.exe from 64bit cygwin

...but you can always mix and match the --build and --host settings; 
32setup from 64cygwin, or 64setup from 32cygwin.

--
Chuck



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