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=tdU1oJHzldH80tb/jXMG+pMAVQqID3XWE7RHxKQbP5M
	IGpjILH3rHcJO4FDiVwZGogXx+bKQ9hHfgZUdkYug0vVBD4dQt61BPbuj3Ety8/2
	tlarI1G+Tdw11J2U8z0j7Om9luy3Ezk7/L/vbp4hriGZAefO2mVDxpxBddW99sWU
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5168957C.70809@lysator.liu.se>
Date: Sat, 13 Apr 2013 01:15:08 +0200
From: Peter Rosin <peda AT lysator DOT liu DOT se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
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>
In-Reply-To: <51681B8C.1070701@shaddybaddah.name>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 2013-04-12 16:34, Shaddy Baddah wrote:
> Hi,
> 
> I am having trouble building Cygwin setup.exe (regular 32bit on
> 32bit). I am finding that the build is hanging at the linking stage of
> libgetopt++:
> 
> make[2]: Entering directory `/cygdrive/c/Users/shaddy/cygwin-home/workarea/cygwin-setup-build/libgetopt++'
>   CXXLD    libgetopt++.la
> 
> Building with options I have deduced give me some debug:
> 
> $ make AM_DEFAULT_VERBOSITY=1 am__v_lt_1=--debug 2>&1 | tee -a build.log
> 
> I find (with confirmation from pstree), the build is hung in libtool:
> 
> make[2]: Entering directory `/cygdrive/c/Users/shaddy/cygwin-home/workarea/cygwin-setup-build/libgetopt++'
> /bin/sh ./libtool --debug --tag=CXX    --mode=link g++  -Wall -Werror -Wno-uninitialized -g -O2 -version-info 1:1:0   -o libgetopt++.la -rpath /cygdrive/c/Users/shaddy/cygwin-home/workarea/cygwin-setup-build/inst/lib src/GetOption.lo src/Option.lo  src/BoolOption.lo src/OptionSet.lo src/StringArrayOption.lo  src/StringOption.lo
> libtool: enabling shell trace mode
> ...
> + func_convert_core_msys_to_w32 .libs/
> + set -x
> ++ /usr/bin/sed -e 's/[ ]*$//' -e 's|\\\\*|\\|g;s|/|\\|g;s|\\|\\\\|g'
> 
> 
> The code that it is stuck on is:
> 
>   func_convert_core_msys_to_w32_result=`( cmd //c echo "$1" ) 2>/dev/null |
>     $SED -e 's/[ ]*$//' -e "$lt_sed_naive_backslashify"`
> 
> And I found the double-slash on the cmd to be problematic. If I
> manually edit it out, the build continues (but only to a real build
> failure, which I'll leave out for the moment).
> 
> I've attached the cygcheck.out from that build host, a Windows 8
> computer. However, I also encountered exactly the same problem on a
> Windows 7 computer.
> 
> 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?

Cheers,
Peter (who will be away for the weekend)


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