unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Build issue GNU Emacs 21.3 on MinGW32 GCC - W2K
Date: Tue, 25 Feb 2003 20:51:09 +0200	[thread overview]
Message-ID: <3405-Tue25Feb2003205108+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20030224162531.041934E166@server2.fastmail.fm> (seagull@fastmail.fm)

> From: "Dhruva Krishnamurthy" <seagull@fastmail.fm>
> Date: Mon, 24 Feb 2003 21:55:30 +0530
> 
>  When I do a "gmake bootstrap" (MinGW32 - GCC 3.3/GCC 3.2.1/GCC 3.2.2 on
>  W2K)
> Build fails at the following locations:
> - calendar/lunar.el (EMACS Abort)
> - calendar/solar.el (EMACS Abort)
> - gnus/gnus-cite.el (SEGV crash)
> - gnus/gnus-draft.el (SEGV crash)
> - gnus/gnus-dup.el (SEGV crash)
> - gnus/gnus-mh.el (SEGV crash)
> - gnus/gnus-uu.el (SEGV crash)
> - gnus/gnus-vm.el (SEGV crash)
> - gnus/nnsoup.el (SEGV crash)
> - gnus/nnvirtual.el (SEGV crash)
> 
> I am sorry if I have bored some of you with my persistent mails. I fear
> that we may end up loosing MinGW support for compiling GNU Emacs and will
> end up depending on MSVC.

I, for one, appreciate your persistence very much.  However, given
that the resources for working on the Windows port are very scarce at
the moment, how about if you try to debug this yourself?  I'm sure
people here, including myself, will be more than willing to offer help
if you report some findings and ask for further guidance, even though
those same people cannot themselves work on the problem.

> For me a true FSF GNU Emacs is when there is no forced dependency on
> commercial compilers or build tools.

Very true, IMHO.

TIA

  reply	other threads:[~2003-02-25 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 16:25 Build issue GNU Emacs 21.3 on MinGW32 GCC - W2K Dhruva Krishnamurthy
2003-02-25 18:51 ` Eli Zaretskii [this message]
2003-02-26  5:05 ` Le Wang
2003-02-26 18:04   ` Eli Zaretskii

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=3405-Tue25Feb2003205108+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --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).