public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Starks-Browning <starksb@ebi.ac.uk>
To: Steven Whatley <swhatley@blkbox.com>
Cc: cygwin@cygwin.com
Subject: Cygwin 20.1b & 1.3.2 on same system
Date: Tue, 17 Jul 2001 08:45:00 -0000	[thread overview]
Message-ID: <2456-Tue17Jul2001164501+0100-starksb@ebi.ac.uk> (raw)
In-Reply-To: <Pine.GSO.3.95.1010717080429.24475C-100000@blkbox.com>

On Tuesday 17 Jul 01, Steven Whatley writes:
> Hi all,
> 
> I'd like to get started writing programs for my Palm IIIx.  The PRC-Tools
> package requites the Cygwin 20.1b version but I have Cygwin v1.3.2
> installed.  Can the two live on the same system?  What is the best way to
> set it up?  

You might have luck with the latest development version of prc-tools,
which is intended to work with the Latest Net Release of Cygwin.  It's
at < http://prc-tools.sourceforge.net/ >.

Regards,
David


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2001-07-17  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 18:36 source Alison Winters
2001-07-16 20:28 ` source Tim Prince
2001-07-16 20:32   ` source Christopher Faylor
2001-07-20  5:13     ` setup.exe Request Max Bowsher
2001-07-20  5:15       ` Robert Collins
2001-07-20 11:31         ` Max Bowsher
2001-07-20 15:05           ` Christopher Faylor
2001-07-17  6:24 ` Cygwin 20.1b & 1.3.2 on same system Steven Whatley
2001-07-17  8:05   ` Larry Hall (RFK Partners, Inc)
2001-07-17  8:45   ` David Starks-Browning [this message]
2001-07-17  9:06     ` Steven Whatley
2001-07-18  5:12   ` Mark Aberdeen
     [not found] <50A89B19AEAAD411B9D200A0C9FB5699010C8DD2@craius.cportcorp.com>
2001-07-17  8:26 ` 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=2456-Tue17Jul2001164501+0100-starksb@ebi.ac.uk \
    --to=starksb@ebi.ac.uk \
    --cc=cygwin@cygwin.com \
    --cc=swhatley@blkbox.com \
    /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).