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
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51632E49.5070500@malth.us>
Date: Mon, 08 Apr 2013 13:53:29 -0700
From: "Gregory M. Turner" <gmt@malth.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@cygwin.com
Subject: cygwin64 build recipe (was: Re: cygwin64 process substitution: known bug?)
References: <5161DCD1.7040002@malth.us> <20130408081044.GB10199@calimero.vinschen.de> <20130408093850.GA12628@calimero.vinschen.de>
In-Reply-To: <20130408093850.GA12628@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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