From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: Angelo.Graziosi@roma1.infn.it, henman@it.to-be.co.jp,
emacs-devel@gnu.org
Subject: Re: emacs snapshot tarball test build
Date: Fri, 23 Mar 2007 15:58:41 +0200 [thread overview]
Message-ID: <umz243vu6.fsf@gnu.org> (raw)
In-Reply-To: <E1HUbWZ-0002A2-7o@fencepost.gnu.org> (message from Richard Stallman on Fri, 23 Mar 2007 00:37:11 -0400)
> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 23 Mar 2007 00:37:11 -0400
> Cc: henman@it.to-be.co.jp, emacs-devel@gnu.org
>
> This often happens boostraping Emacs on Cygwin.
>
> Workaround: try to build in another nested directory.
>
> Is this documented in the installation instructions?
> In etc/PROBLEMS?
>
> If not, would someone like to add that info?
These are not workarounds that I'd recommend adding to PROBLEMS.
In general, if the problem only happens during bootstrap, and doesn't
have a good workarounds, I'd say let's ignore it. Most Emacs users
will never bootstrap.
next prev parent reply other threads:[~2007-03-23 13:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 11:27 Help: build emacs in cygwin (fwd) Angelo Graziosi
2007-03-09 15:24 ` Eli Zaretskii
2007-03-13 13:10 ` Help: build emacs in cygwin Angelo Graziosi
2007-03-13 18:23 ` Harald Maier
2007-03-14 0:52 ` Angelo Graziosi
2007-03-14 1:31 ` djh
2007-03-14 7:41 ` Jason Rumney
2007-03-22 21:41 ` emacs snapshot tarball test build Angelo Graziosi
2007-03-23 1:34 ` djh
2007-03-23 9:09 ` Angelo Graziosi
2007-03-23 14:04 ` Eli Zaretskii
2007-04-04 11:32 ` Pretest 22.0.97 Angelo Graziosi
2007-04-13 11:47 ` Build failure on Cygwin Angelo Graziosi
2007-05-14 20:56 ` merging Unicode branch and availability of Windows binaries Angelo Graziosi
2007-05-14 21:13 ` Drew Adams
2007-03-23 4:37 ` emacs snapshot tarball test build Richard Stallman
2007-03-23 13:58 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 6:10 djh
2007-03-23 12:43 ` Eli Zaretskii
2007-03-28 7:32 ` djh
2007-03-28 20:45 ` Eli Zaretskii
2007-03-29 1:54 ` djh
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=umz243vu6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Angelo.Graziosi@roma1.infn.it \
--cc=emacs-devel@gnu.org \
--cc=henman@it.to-be.co.jp \
--cc=rms@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).