From: N8TM@aol.com
To: michael@weiser.saale-net.de, cygwin@sourceware.cygnus.com
Subject: Re: [FAQ autopost] gnuwin32 resource pointer
Date: Sun, 14 Nov 1999 19:51:00 -0000 [thread overview]
Message-ID: <0.4b04558b.2560dd10@aol.com> (raw)
As I do not know of any other "installation-specific" instructions for
building the gnu compilers and running the test suites under cygwin, I have
collected procedures at http://www.members.aol.com/n8tm/cygwingccg77.htm
including work-arounds for W95, NT4, and W2K.
Tim
tprince@computer.org
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: N8TM@aol.com
To: michael@weiser.saale-net.de, cygwin@sourceware.cygnus.com
Subject: Re: [FAQ autopost] gnuwin32 resource pointer
Date: Tue, 30 Nov 1999 23:39:00 -0000 [thread overview]
Message-ID: <0.4b04558b.2560dd10@aol.com> (raw)
Message-ID: <19991130233900.qD0XuOWSBwwD8HN4DyFB6gKXIKX2QesK-oV-SVL5cz8@z> (raw)
As I do not know of any other "installation-specific" instructions for
building the gnu compilers and running the test suites under cygwin, I have
collected procedures at http://www.members.aol.com/n8tm/cygwingccg77.htm
including work-arounds for W95, NT4, and W2K.
Tim
tprince@computer.org
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-11-14 19:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-14 19:51 N8TM [this message]
1999-11-15 18:32 ` Michael Weiser
1999-11-30 23:39 ` Michael Weiser
1999-11-30 23:39 ` N8TM
-- strict thread matches above, loose matches on Subject: below --
1999-11-30 18:58 Michael Weiser
1999-11-30 23:39 ` Michael Weiser
1999-12-01 9:48 ` Michael Weiser
1999-12-31 13:28 ` Michael Weiser
1999-11-14 18:31 Michael Weiser
1999-11-30 23:39 ` Michael Weiser
1999-10-31 17:13 Michael Weiser
1999-10-31 19:54 ` Michael Weiser
1999-10-14 17:24 Michael Weiser
1999-10-31 19:54 ` Michael Weiser
1999-09-30 17:10 Michael Weiser
1999-09-30 23:42 ` Michael Weiser
1999-09-30 7:11 Michael Weiser
1999-09-30 23:42 ` Michael Weiser
1999-10-01 5:11 ` Michael Weiser
1999-10-31 19:54 ` Michael Weiser
1999-09-14 19:53 Michael Weiser
1999-09-30 23:42 ` Michael Weiser
1999-08-31 18:33 Michael Weiser
1999-08-31 23:49 ` Michael Weiser
1999-08-14 18:37 Michael Weiser
1999-08-31 23:49 ` Michael Weiser
1999-07-31 18:34 Michael Weiser
1999-07-14 18:32 Michael Weiser
1999-07-31 18:34 ` Michael Weiser
1999-06-30 18:32 Michael Weiser
1999-06-30 22:10 ` Michael Weiser
1999-06-14 18:33 Michael Weiser
1999-06-30 22:10 ` Michael Weiser
1999-05-31 18:32 Michael Weiser
1999-05-31 21:10 ` Michael Weiser
1999-05-14 18:44 Michael Weiser
1999-05-31 21:10 ` Michael Weiser
1999-04-30 18:32 Michael Weiser
1999-04-14 18:32 Michael Weiser
1999-04-30 18:32 ` Michael Weiser
1999-03-31 17:33 Michael Weiser
1999-03-31 19:45 ` Michael Weiser
1999-03-14 19:18 Michael Weiser
1999-03-31 19:45 ` Michael Weiser
1999-02-28 18:33 Michael Weiser
1999-02-28 23:02 ` Michael Weiser
1999-02-14 18:32 Michael Weiser
1999-02-28 23:02 ` Michael Weiser
1999-01-31 23:52 Michael Weiser
1999-02-01 5:50 ` Michael Weiser
[not found] ` < 199902010000.BAA29320@khazad-dum.weiser.saale-net.de >
1999-02-01 18:37 ` Michael Weiser
1999-02-28 23:02 ` Michael Weiser
1999-02-28 23:02 ` Michael Weiser
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=0.4b04558b.2560dd10@aol.com \
--to=n8tm@aol.com \
--cc=cygwin@sourceware.cygnus.com \
--cc=michael@weiser.saale-net.de \
/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).