Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 12 Feb 2001 14:32:52 -0500 From: Christopher Faylor To: Cygwin Subject: Re: Cygwin for Itanitium (Whistler) Message-ID: <20010212143252.A4738@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin References: <3A847D1B.FAD08C7C@lutris.com> <20010212104407.F2107@cygbert.vinschen.de> <007701c094fb$a1116db0$9865fea9@timayum4srqln4> <3A883208.474BAEE0@veritas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3A883208.474BAEE0@veritas.com>; from rmcgowan@veritas.com on Mon, Feb 12, 2001 at 10:57:12AM -0800 On Mon, Feb 12, 2001 at 10:57:12AM -0800, Bob McGowan wrote: >I've seen a problem with running cygwin in the 64 bit environment, too, >and I agree, the problem is not in the 32 bit emulation. The initial >bash shell starts and runs fine, internal commands work as expected. >The problem I'm seeing is when an external command is tried. The error >generated is: > >$ ls >97304241 [main] bash 1640 sync_with_child: child 476(0x700) died before initialization with status code 0x80 >97305532 [main] bash 1640 sync_with_child: *** child state waiting for longjmp >bash: fork: Resource temporarily unavailable >$ > >I'm not able to pursue trying to fix this and its not a high priority >for me. But I could spare a cycle or two to help test, if needed. It is not likely that we will be pursuing a 64 bit port unless Red Hat is paid to do so. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple