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=hgoWTtgQG+6Y5iJrvbnD0Zota/NS/vffwp+yYyrJpoi
	pjF8Pl5Q1mPGl3JngyQ6ThYt0anrsdzAZST4O0PtnnIkM6yek4x6OCD1dAue+E4E
	QqSwtqSPN0wJ8j3jLdDun3VjJBJLOD2EF0Ycpl3888i+wohcgyxqJ4GGCDNM24Xk
	=
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=8NJHm32vt42wvBHaBKAkM2iLNuY=; b=TAvuAD6bu8wUKE5I8
	Omsd3p9oWZK/3HZXs8pkiOlMNdAWzIYsJFKq1AQPSNBq3Gl87lsFJ6Ot8JSwp6Aa
	e5DU3bzN4AYsBZXwjts2RHoJBmKcrxm/lwal9vVGb9sOHWRTMAt0rKUM50OyLHVX
	6A5ZNswmPjR/7y859UYNto37Pc=
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
X-Spam-SWARE-Status:	No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,RCVD_VIA_APNIC autolearn=ham version=3.3.1
Message-ID:	<516BBCA6.5030107@shaddybaddah.name>
Date:	Mon, 15 Apr 2013 18:39:02 +1000
From:	Shaddy Baddah <lithium-cygwin AT shaddybaddah DOT name>
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: possible libtool bug blocking builds of Cygwin setup.exe
References:	<51681B8C DOT 1070701 AT shaddybaddah DOT name> <5168957C DOT 70809 AT lysator DOT liu DOT se> <5168A77E DOT 9090907 AT shaddybaddah DOT name> <5168F04B DOT 2010105 AT lysator DOT liu DOT se>
In-Reply-To:	<5168F04B.2010105@lysator.liu.se>
X-Optus-CM-Score:	0
X-Optus-CM-Analysis:	v=2.0 cv=HfxM1V48 c=1 sm=1 a=VuQqkWwBfaAA:10 a=yOqpaCKOgisA:10 a=8nJEP1OIZ-IA:10 a=8I0BVzSG5d0A:10 a=ERfkQRCpBwv-tYYGskwA:9 a=wPNLvfGTeEIA:10 a=RkPObcNqpdaXDoCDBSw5Xw==:117

Hi Peter,

On Apr 13, Peter Rosin wrote:
> On 2013-04-13 02:31, Shaddy Baddah wrote:
>> Hi Peter,
>>
>> On 13/04/13 09:15, Peter Rosin wrote:
>> </snip>
>>>> Have I stumbled on a real problem?
>>>
>>> This all sounds suspiciously like libtool bug 14022, where the reporter
>>> had confused --build and --host. How did you run configure?
>>>
>>
>>
>> I'm emulating what is in setup/bootstrap.sh:
>>
>> $ ../cygwin-setup/configure --build="i686-pc-mingw32" --host="i686-pc-mingw32" -C
>
> Since you had POSIX paths with a distinct Cygwin touch, I guess we can
> stop blaming Libtool. You are apparently cross-compiling from Cygwin to
> MinGW and should drop your --build argument and thus let config.guess
> do its thing. I.e. stop lying to configure.
>
> Or build with MSYS where the above --build and --host are true.
>
> I guess the bootstrap script also needs some love if you have read it
> right. I haven't read it at all.

You are correct, dropping the --build argument was the correct action. I
apologise for blaming libtool. I was confused and therefore only
suggested it was a possibility. Thankfully it was not.

-- 
Thanks,
Shaddy

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