From: Maks Romih <maks.romih@t-2.net>
Subject: Re: Building Emacs-cvs on Cygwin (GCC summary)
Date: Mon, 30 Oct 2006 02:22:39 +0100 (CET) [thread overview]
Message-ID: <20061030022239.AEY02066@m1.t-2.net> (raw)
> GCC-3.4.4-(1/2) Segment fault
>
> GCC-4.0.3 OK
> GCC-4.1.1 OK
>
> GCC-4.2-20061024(prerelease) M-x undefined
> GCC-4.3-20061022(experim.) M-x undefined
>
>
> In conclusion on Cygwin only the build with GCC-4.0.3 and > 4.1.1 seem to
> work fine.
>
> Are there people that can confirm these results?
I can confirm the 3.4.4.1., because I've also had stackdumps when I built the emacs-22.0.50 with GCC 3.4.4.1.
Then I compiled with CFLAGS=-g to see where it breaks but it doesn't break any more, so now I happily use the debug version.
Maks.
next reply other threads:[~2006-10-30 1:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 1:22 Maks Romih [this message]
2006-10-30 19:16 ` Building Emacs-cvs on Cygwin (GCC summary) Richard Stallman
2006-10-30 20:31 ` Eric Hanchrow
2006-10-30 21:05 ` Eli Zaretskii
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=20061030022239.AEY02066@m1.t-2.net \
--to=maks.romih@t-2.net \
/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).