From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building Emacs-cvs on Cygwin (GCC summary)
Date: Mon, 30 Oct 2006 23:05:42 +0200 [thread overview]
Message-ID: <uodrt7bvd.fsf@gnu.org> (raw)
In-Reply-To: <87wt6hfsue.fsf@offby1.atm01.sea.blarg.net> (message from Eric Hanchrow on Mon, 30 Oct 2006 12:31:53 -0800)
> From: Eric Hanchrow <offby1@blarg.net>
> Date: Mon, 30 Oct 2006 12:31:53 -0800
>
> >>>>> "Richard" == Richard Stallman <rms@gnu.org> writes:
>
> Richard> Let's document that people should not use GCC 3.4 on
> Richard> Cygwin. Where is the best place to document this?
>
> I vote for nt/INSTALL
No, that's the wrong file: the problem is in the Cygwin build, which
doesn't use any of the stuff in nt/.
The right place is etc/PROBLEMS.
next prev parent reply other threads:[~2006-10-30 21:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 1:22 Building Emacs-cvs on Cygwin (GCC summary) Maks Romih
2006-10-30 19:16 ` Richard Stallman
2006-10-30 20:31 ` Eric Hanchrow
2006-10-30 21:05 ` Eli Zaretskii [this message]
2006-10-30 21:26 ` Eric Hanchrow
2006-10-30 21:44 ` Jason Rumney
2006-11-05 10:52 ` Jari Aalto
2006-11-05 11:55 ` Eli Zaretskii
2006-10-30 21:06 ` Eli Zaretskii
2006-11-04 12:12 ` Eli Zaretskii
2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi
2006-11-21 1:46 ` Angelo Graziosi
2006-11-21 9:35 ` Angelo Graziosi
2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi
2006-11-22 22:23 ` Eli Zaretskii
2006-11-23 0:07 ` Angelo Graziosi
2006-11-23 4:15 ` Eli Zaretskii
2006-11-23 14:04 ` Angelo Graziosi
2006-11-23 23:55 ` Angelo Graziosi
2006-11-24 21:17 ` Eli Zaretskii
2006-11-24 23:32 ` Angelo Graziosi
2006-11-25 11:07 ` Eli Zaretskii
2006-11-25 9:52 ` Angelo Graziosi
2006-11-25 11:06 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-10-28 12:16 Building Emacs-cvs " Eli Zaretskii
2006-10-29 11:13 ` Building Emacs-cvs on Cygwin (GCC summary) Angelo Graziosi
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uodrt7bvd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).