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=XC3R/VDXwMlfirQoDMBse09mrDqQllN6WE2z4Gqjgr8
	IvxGSCO4UYcoLMRxyvzKbj6NQqoU6jK5fjqyECLcaFRFJ/S8OBkoMVZMNZKLNE3L
	9hUKxhMnQVxvbOtUpmIk+YTC+1i5AzcPQqGvzEgG2Ea/PmI4wk3Z8wUJF2U4Vl9E
	=
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=a/S99BQhXkCSD73ZwGDrfZUlNnQ=; b=QRFhV1smmRwUuw7tJ
	sRiMAR3FzwTw/fNoDthcfrbULL3tzkYCb3ahIvK0Sef8SzSQvSB9oUweJR49Yech
	WTXl5qHkejBF02v12WjFIN8fy3hAxJeldWvq6l7v/6m1kzmmxrL11G2g0Ysztkas
	/mVfsbB7PAVdflwwDqJjjPeSlY=
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.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_LR,TW_RW,TW_WX,TW_XR,TW_YG autolearn=ham version=3.3.1
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=LugLmlygW3p/D6VvVtVWBbWJdVdYSZ86ad+dgL4Z7y4=; b=mRzfMZM7Qn5sX8pdCeEI1SAUM/jWlsWIP070XdwvX4vMksI6SSP6qtEgvOkCEQYks9 Pxhq2O7MawWBO1iCmiOis2KtMMeXzHmxxnIupNerceKNZiw5erOFPwwdIWombJ2TWZaF sBo36q1evf9JXErg1jMXEmlUrLIiQkH8ai4atEzxjFyZq+O5GjUZxEJ+enNaoIz/2szL O2cSbm0+9QjdZ6yDHmGsJJG/5CYSRpn2aXeOVN7KV/Hy1A5kaNMTFjPJ7RQki1Tsr4v0 0s0gy+MabXGbqIfgljXulSyyy0Fe68tRBCGpo0zmii3nKgOZ6jFXScLkpfd7e4y094AY qMRA==
X-Received:	by 10.60.26.137 with SMTP id l9mr16786484oeg.17.1365454450779; Mon, 08 Apr 2013 13:54:10 -0700 (PDT)
Message-ID:	<51632E49.5070500@malth.us>
Date:	Mon, 08 Apr 2013 13:53:29 -0700
From:	"Gregory M. Turner" <gmt AT malth DOT us>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	cygwin64 build recipe (was: Re: cygwin64 process substitution: known bug?)
References:	<5161DCD1 DOT 7040002 AT malth DOT us> <20130408081044 DOT GB10199 AT calimero DOT vinschen DOT de> <20130408093850 DOT GA12628 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20130408093850.GA12628@calimero.vinschen.de>
X-Gm-Message-State:	ALoCoQn4BEtYxawE/Rc/BVHLCQazlA/xOCwlLRtBONMrWLw6/sqPVTcQ6eqS1eK8qq6jI2geI4J/

On 4/8/2013 2:38 AM, Corinna Vinschen wrote:
> On Apr  8 10:10, Corinna Vinschen wrote:
>> On Apr  7 13:53, Gregory M. Turner wrote:
>>> On my cygwin64, all bash process substitutions fail:
>>>
>>> $ ls -l <(echo foo)
>>> lrwxrwxrwx 1 greg None 0 Apr  7 13:20 /dev/fd/63 -> pipe:[656]
>>>
>>> $ cat <(echo foo)
>>> cat: /dev/fd/63: No such file or directory
>>>
>>> Here's an strace: http://pastebin.com/KS9766Vv
>>>
>>> Anyone know what's going on?  I don't have a cygwin64 kernel/libc
>>> build tree, yet, but, if this merits further investigation, I
>>> suppose it's as good an excuse as any to build one, as this is
>>> messing up my play-time.
>> Confirmed.  Looks like a bug in bash or (more likely) 64 bit Cygwin.
>> I'm going to fix a problem reported on the cygwin-apps list first, but
>> I'll have a look into this later this week.
>>
>> Of course I'd appreciate if you look into this, too.  Many problems
>> found in the 64 bit version during the last couple of weeks are based
>> on sloppy datatype handling, so I guess this is another one of them.
> I looked into this first, accidentally.  This should be fixed in CVS
> I'll upload a new 64 bit Cygwin DLL later today.
>
>
> Thanks again for the report,

No, thank you for the fix!

If I may hijack my own thread a bit: I tried a cygwin64 core build but 
things didn't go great.

Is bootstrap.sh on *-*-linux-gnu still the best way to roll your own 
cygwin64?  My attempts to cross the cygwin64 cygport on cygwin32 
resulted in tons of fussy problems centered around dlmalloc.c (I also 
had to kludge around some Makefile problems).

Any chance, yet, that the right thing would happen if I just checked out 
the cygwin-64bit-branch of winsup in my cygwin64 environment and "did 
what README says"?

-gmt


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