From: Ildar Mulyukov <ildar@users.sourceforge.net>
To: cygwin <cygwin@cygwin.com>
Subject: status gcc-3
Date: Fri, 01 Mar 2002 02:57:00 -0000 [thread overview]
Message-ID: <3C7F5E8A.8050507@users.sourceforge.net> (raw)
Hello, cygwin hackers!
Would you please inform me about gcc-3.x status regarding to Cygwin
project? I mean
* status of gcc-3 ability at cygwin platform
(I suggest 99%; when I tried it out 2month ago everything seemed to be
allright except spec - it was ugly)
* plans of using it as the default/alternative compiler available via
setup.exe
Thanks!
--
Ildar Mulyukov,
free SW programmer/designer
================================================
email: ildar@users.sourceforge.net
projects: http://os-development.sourceforge.net/
home: http://www.faki.mipt.ru/~ildar
================================================
--
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/
next reply other threads:[~2002-03-01 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 2:57 Ildar Mulyukov [this message]
2002-03-01 5:36 ` Christopher Faylor
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=3C7F5E8A.8050507@users.sourceforge.net \
--to=ildar@users.sourceforge.net \
--cc=cygwin@cygwin.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).