From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>
To: emacs-devel@gnu.org
Subject: Re: Build failure on Cygwin
Date: Fri, 13 Apr 2007 13:47:32 +0200 (MET DST) [thread overview]
Message-ID: <Pine.OSF.4.21.0704131338180.27730-100000@ax0rm1.roma1.infn.it> (raw)
In-Reply-To: <ulkho3vk4.fsf@gnu.org>
Eric Hanchrow wrote:
> I simply did "cvs co ...", "./configure", "make bootstrap".
>
> ...
> Fatal error (6)/bin/sh: line 2: 220 Aborted....
>
This often happens in bootstrapping under Cygwin.
Solution: build in a separate directory and/or build from an
"xterm" console (NOT the dos-like console)...
...or use prebuild (22.0.97-pretest) Cygwin binaries from
http://www.webalice.it/angelo.graziosi/Emacs.html.
To build use GCC-4.0.3 or 4.0.4 which seem to give very stable binaries.
Cheers,
Angelo.
next prev parent reply other threads:[~2007-04-13 11:47 UTC|newest]
Thread overview: 24+ 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 ` Angelo Graziosi [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-04-13 3:12 Build failure on Cygwin Eric Hanchrow
2007-04-13 9:35 ` Eli Zaretskii
2007-04-13 15:01 ` Eric Hanchrow
2007-04-13 19:01 ` Eli Zaretskii
2007-04-14 1:04 ` Eric Hanchrow
2007-04-14 11:30 ` Eli Zaretskii
2007-04-15 12:11 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=Pine.OSF.4.21.0704131338180.27730-100000@ax0rm1.roma1.infn.it \
--to=angelo.graziosi@roma1.infn.it \
--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).