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:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=OSB
	o2ywRUhFIP6kuurGQqZUB/94mDo5xPcTUhDbodMr7XaahvdsrxOavsYwHc3GAvST
	aVUT8qiFnlyTGz9A0p+UyOxCf077DfloNtdwkf8d9ZvMgsaqYrTLIoyQRkielhc/
	EGvOwvOcdR9bo+8jwCZ+J+x64oQOQPQcBPcee9cs=
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:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; s=default; bh=r2196rfkh
	90t7mnz1O49zc/Fwro=; b=ntapYsR2OIwQdyP9slnSbBVJWLstNZFhhJbMSEP76
	YUtnIm2NgUVMm06z//bFy7+G9szbt9/HKT/FN6KWfFbKWV9/sgV68bs2IsVL4Otc
	0Ju5h4iV0siJ+0P0bXnsOWdjrDd1usHt7mkn1lZtdf0smmvsLkKoZUaxx1ccTJ+B
	tg=
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=-1.0 required=5.0 tests=AWL,BAYES_05,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	Mark Geisert <mark AT maxrnd DOT com>
Subject:	32/64 issue building native 32-bit Cygwin from CVS
Date:	Tue, 3 Dec 2013 17:03:56 +0000 (UTC)
Lines:	25
Message-ID:	<loom.20131203T175052-753@post.gmane.org>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

I'm running into this issue when building winsup/lsaauth.  My autoconf foo
is weak but it appears the configure.ac wants to use 64-bit mingw tools even
on this 32-bit build.  There was a similar issue in winsup/utils but
recently that was fixed elsewhere and picked up by my very recent 'cvs update'.

checking for i686-w64-mingw32-gcc... i686-pc-mingw32-gcc
checking for x86_64-w64-mingw32-gcc... no
configure: error: no acceptable mingw64 cc found in $PATH
configure: error: /oss/src/winsup/lsaauth/configure failed for lsaauth
make[1]: *** [configure-target-winsup] Error 1
Makefile:8338: recipe for target 'configure-target-winsup' failed
make[1]: Leaving directory '/oss/build'
Makefile:833: recipe for target 'all' failed
make: *** [all] Error 2

Related question: Are the necessary
    MINGW_CXX=i686-pc-mingw32-g++
    MINGW32_CC=i686-pc-mingw32-gcc
supposed to be exported by the global configure/build process or do I have
to define and export them manually?  I've done the latter because the former
doesn't seem to be happening automatically.

Thanks for any leads,

..mark


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