public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: seagull@fastmail.fm To: gcc-gnats@gcc.gnu.org Cc: rms@gnu.org Subject: other/9816: GCC 3.2.2 (Mingw Release candidate version) - Regression in building GNU Emacs 21.3 (CVS) Date: Sun, 23 Feb 2003 09:26:00 -0000 [thread overview] Message-ID: <20030223092326.9193.qmail@sources.redhat.com> (raw) >Number: 9816 >Category: other >Synopsis: GCC 3.2.2 (Mingw Release candidate version) - Regression in building GNU Emacs 21.3 (CVS) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sun Feb 23 09:26:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: seagull@fastmail.fm >Release: GCC-3.2.2 (MinGW32 version) on W2K >Organization: >Environment: GCC 3.2.2 MingW GCC release candidate Windows 2000 >Description: - Compiling GNU Emacs 21.2.95 (Beta release) and 21.3 (CVS) is possible using GCC 3.2.1 Mingw on W2K - The same fails using GCC 3.2.2 Mingw on W2K It is a GCC regression (maybe a Mingw port regression) >How-To-Repeat: - Install MinGW 2.0 and add GCC 3.2.2 from (www.mingw.org) - Download GNU Emacs 21.2.95 or 21.3 (from CVS) - From emacs/nt, "configure --with-gcc" to use GCC - "gmake bootstrap" for building GNU Emacs - The executable gets built but while the built emacs.exe is used for compiling lisp files, it crashes on some. >Fix: - No fix - I had to build using MSVC. - Then rebuild with GCC - Recompile all lisp files using the emacs.exe generated by MSVC (to avoid compilation of lisp files from GCC generated emacs.exe) >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-02-23 9:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-23 9:26 seagull [this message] 2003-02-24 15:10 bangerth
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=20030223092326.9193.qmail@sources.redhat.com \ --to=seagull@fastmail.fm \ --cc=gcc-gnats@gcc.gnu.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).