From: Mumit Khan <khan@xraylith.wisc.edu>
To: law@cygnus.com
Cc: "Philippe PRADOS" <pprados@club-internet.fr>, egcs@cygnus.com
Subject: Re: Installation in Windows
Date: Thu, 04 Dec 1997 20:26:00 -0000 [thread overview]
Message-ID: <9712050424.AA23569@modi.xraylith.wisc.edu> (raw)
In-Reply-To: <6361.881275431@hurl.cygnus.com>
Jeffrey A Law <law@cygnus.com> writes:
>
> In message < 01bd0092$3f5915b0$6d068609@magauto1 >you write:
> > We can't start 'configure' with Windows. How can we generate version ? or
> > where can we find compiled version for windows ?
> I don't think we support windows. You might be able to get something running
> using cygwin, but I don't think bare windows will work.
> jeff
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ for more info
on running egcs natively under win32 (aka mingw32). I've been distributing
a reasonably complete development toolchain based on egcs-971023, and now
it's time for egcs-1.0 hopefully sometime this weekend.
My local changes are derived from Jan-Jaap's changes (see my web page for
more info -- follow the ftp pointer), and then quite a few other misc
fixes to account for win32 braindeadness. Most of Jan-Jaap's changes are
now approved by Kenner (thanks to Jan-Jaap's great work and persistence),
and will be in FSF gcc-2.8.0. The other changes, eg., the ones to libU77
are completely unofficial until they're approved by the respective
authors/maintainers.
Good news is that my local tree based on egcs-971201 snapshot passed all
but gcov and profile dejagnu tests. The failures are "expected" on this
platform, at least for now.
Mumit
prev parent reply other threads:[~1997-12-04 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-04 2:52 Philippe PRADOS
1997-12-04 14:19 ` Mumit Khan
1997-12-04 14:41 ` Jeffrey A Law
1997-12-04 20:26 ` Mumit Khan [this message]
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=9712050424.AA23569@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=pprados@club-internet.fr \
/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).