From: Eric Hanchrow <offby1@blarg.net>
To: emacs-devel@gnu.org
Subject: Re: Build failure on Cygwin
Date: Fri, 13 Apr 2007 18:04:29 -0700 [thread overview]
Message-ID: <87ps674vhe.fsf@offby1.atm01.sea.blarg.net> (raw)
In-Reply-To: ubqhsjdzg.fsf@gnu.org
For what it's worth, I just built gcc 4 from source, which went
perfectly smoothly, and then built emacs from that, which also went
perfectly smoothly.
--
next prev parent reply other threads:[~2007-04-14 1:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2007-04-14 11:30 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2007-04-15 12:11 Angelo Graziosi
2007-03-23 14:04 emacs snapshot tarball test build Eli Zaretskii
2007-04-13 11:47 ` Build failure on Cygwin 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=87ps674vhe.fsf@offby1.atm01.sea.blarg.net \
--to=offby1@blarg.net \
--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).