From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: building bash-2.03?
Date: Tue, 13 Jul 1999 08:58:00 -0000 [thread overview]
Message-ID: <19990713115954.A825@cygnus.com> (raw)
In-Reply-To: <19990712143203.C21559@cygnus.com>
On Mon, Jul 12, 1999 at 02:32:03PM -0700, Geoffrey Noer wrote:
>> Has anyone else built bash-2.03 successfuly for cygwin? Is there
>> something special I need to do, or should I start looking for problems
>> in my cygwin setup? (I've built other gnu software in the past
>> without difficulty.)
>
>As an FYI, I imported bash 2.03 into our development sources here at
>Cygnus which was pretty painless. This (or possibly a newer version)
>will be in the next Cygwin release, whenever that happens.
Cool. Does anyone know when the new release is going to come out?
(preemptively)
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: building bash-2.03?
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <19990713115954.A825@cygnus.com> (raw)
Message-ID: <19990731183400.dvsJXHJsl9stUCXSvTtew4yMc7lYvdavCUvnUTOaed0@z> (raw)
In-Reply-To: <19990712143203.C21559@cygnus.com>
On Mon, Jul 12, 1999 at 02:32:03PM -0700, Geoffrey Noer wrote:
>> Has anyone else built bash-2.03 successfuly for cygwin? Is there
>> something special I need to do, or should I start looking for problems
>> in my cygwin setup? (I've built other gnu software in the past
>> without difficulty.)
>
>As an FYI, I imported bash 2.03 into our development sources here at
>Cygnus which was pretty painless. This (or possibly a newer version)
>will be in the next Cygwin release, whenever that happens.
Cool. Does anyone know when the new release is going to come out?
(preemptively)
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-13 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-12 9:43 David Starks-Browning
1999-07-12 14:32 ` Geoffrey Noer
1999-07-13 8:58 ` Chris Faylor [this message]
1999-07-31 18:34 ` Chris Faylor
1999-07-31 18:34 ` Geoffrey Noer
1999-07-31 18:34 ` David Starks-Browning
1999-07-12 10:23 Earnie Boyd
1999-07-31 18:34 ` Earnie Boyd
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=19990713115954.A825@cygnus.com \
--to=cygwin@sourceware.cygnus.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).