From: Eric Hanchrow <offby1@blarg.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eric Hanchrow <eric.hanchrow@gmail.com>, emacs-devel@gnu.org
Subject: Re: Build failure on Cygwin
Date: Fri, 13 Apr 2007 08:01:50 -0700 [thread overview]
Message-ID: <87odls5ndt.fsf@offby1.atm01.sea.blarg.net> (raw)
In-Reply-To: <uk5wgk45n.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 13 Apr 2007 12\:35\:48 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Thu, 12 Apr 2007 20:12:06 -0700 From: "Eric Hanchrow"
>> <eric.hanchrow@gmail.com>
>>
>> I simply did "cvs co ...", "./configure", "make bootstrap".
Eli> Thanks for reporting.
Eli> Is this the first time you try to bootstrap the Cygwin build?
Yes, or at least, the first time in years.
Eli> If so, please look for relevant entries in PROBLEMS, and make
Eli> sure you don't trip on any of the Cygwin-related gotchas
Eli> mentioned there. In particular, the one with GCC versions.
I did indeed have gcc 3.4.4, which that file mentions doesn't work.
Thanks, that explains the failure. But it leaves me with two
questions:
* Couldn't "configure" detect the gcc version, and fail if it finds
that we're using any of those bad gcc versions on Cygwin? That
would have saved me and you time.
* Do I need to build gcc 4 myself from source? It doesn't appear to
be available from Cygwin's setup program.
--
next prev parent reply other threads:[~2007-04-13 15:01 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 [this message]
2007-04-13 19:01 ` Eli Zaretskii
2007-04-14 1:04 ` Eric Hanchrow
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87odls5ndt.fsf@offby1.atm01.sea.blarg.net \
--to=offby1@blarg.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric.hanchrow@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.