public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bob McGowan <rmcgowan@veritas.com>
To: Tim Prince <tprince@computer.org>
Cc: Cygwin <cygwin@sources.redhat.com>
Subject: Re: Cygwin for Itanitium (Whistler)
Date: Mon, 12 Feb 2001 11:24:00 -0000	[thread overview]
Message-ID: <3A883208.474BAEE0@veritas.com> (raw)
In-Reply-To: <007701c094fb$a1116db0$9865fea9@timayum4srqln4>

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.

Tim Prince wrote:
> 
> I thought the problem was in Whistler-64 not supporting enough Windows
> functions, and that had something to do with MKS revoking their
> commitment to port to it.  MKS ksh runs sufficiently to be useful, so
> you can't say the 32-bit mode is totally broken.
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: <cygwin@cygwin.com>
> Sent: Monday, February 12, 2001 1:44 AM
> Subject: Re: Cygwin for Itanitium (Whistler)
> 
> > On Fri, Feb 09, 2001 at 03:28:27PM -0800, Wes Isberg wrote:
> > > Hi all -
> > >
> > > I'm having the same problem as the person who emailed in October
> > > (child-died errors on any Cygwin command) when running on
> > > Itanium/Whistler Beta (64-bit Windows 2000).
> > >
> > > Has anyone built cygwin for Itanium?
> > > (since its 32-bit compatibility mode is not working...)
> >
> > You are a pioneer. Why don't you try to compile (and port?) Cygwin on
> > the Itanium/Whistler platform? Your efforts would be highly
> appreciated.
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin
> to
> > Cygwin Developer
> mailto:cygwin@cygwin.com
> > Red Hat, Inc.
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
rmcgowan@veritas.com

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-02-12 11:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 15:27 Wes Isberg
2001-02-12  1:44 ` Corinna Vinschen
2001-02-12  5:53   ` Tim Prince
2001-02-12 11:24     ` Bob McGowan [this message]
2001-02-12 11:32       ` Christopher Faylor
2001-02-12 14:57   ` Wes Isberg
2001-02-12 15:04     ` Larry Hall (RFK Partners, Inc)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A883208.474BAEE0@veritas.com \
    --to=rmcgowan@veritas.com \
    --cc=cygwin@sources.redhat.com \
    --cc=tprince@computer.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).