all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Cc: emacs-devel@gnu.org
Subject: Re: building NTEmacs
Date: Wed, 05 Mar 2003 13:33:53 -0500	[thread overview]
Message-ID: <uptp5ll2m.fsf@boost-consulting.com> (raw)
In-Reply-To: <20030305184149.8AA9.LEKTU@terra.es> (Juanma Barranquero's message of "Wed, 05 Mar 2003 18:49:54 +0100")

Juanma Barranquero <lektu@terra.es> writes:

> On Wed, 05 Mar 2003 12:17:49 -0500, David Abrahams <dave@boost-consulting.com> wrote:
>
>> Ah, but the nt installation instructions don't say I should "make
>> bootstrap", do they? ;-)
>
> On HEAD there's a INSTALL-CVS on the root directory, though you're right
> there is none on EMACS_21_1_RC. :(
>
>> Once I do that and the -kb dance with my .tit files (oh, and I had to
>> make lisp/loaddefs.el writable because I checkout with CVSREAD set),
>> it seems to be working.
>
> Glad to hear.
>
>> What kind?  The "emacs crashed; do you want to send a report to
>> Microsoft?" window comes up.  I click "no" instead of dropping into
>> the debugger because I figure the build is surely optimized.
>
> Uh? AFAIK, there's no prebuilt binary for HEAD (we don't do nightly
> tarballs, etc.), so *you* should know if the executable you're building
> is optimized or not, shouldn't you?

Only if I know what the build/install process does by default.  It's
not as though I went crawling into the nmake file to figure out what
was happening.

>> I don't think anything I was doing was causing images to be
>> displayed, so there must be crashes elsewhere.
>
> As I said, I've been a few on my system, but nothing as serious as
> "daily crashes", so it'd be *really* helpful to try entering the
> debugger to see where's Emacs crashing.

It would only help if there were debug symbols, and I don't know
whether there are. Also, since I now have the release candidate I'm
unlikely to have an opportunity to do that unless this one crashes
too.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

  reply	other threads:[~2003-03-05 18:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-21 14:59 building NTEmacs David Abrahams
2003-02-21 15:06 ` David Abrahams
2003-02-21 15:19 ` Juanma Barranquero
2003-02-21 15:57   ` David Abrahams
2003-02-21 16:24     ` Juanma Barranquero
2003-03-05 16:22       ` David Abrahams
2003-03-05 16:54         ` Juanma Barranquero
2003-03-05 17:17           ` David Abrahams
2003-03-05 17:49             ` Juanma Barranquero
2003-03-05 18:33               ` David Abrahams [this message]
2003-03-06  7:27                 ` Juanma Barranquero
2003-03-08  1:35                   ` David Abrahams
2003-03-08 12:51                     ` David Abrahams
     [not found]             ` <1046896317.3e665ebdb7657@webmail.freedom2surf.net>
2003-03-05 20:47               ` David Abrahams
2003-02-21 20:25     ` Jason Rumney
2003-02-23  9:47   ` Frank Schmitt
2003-02-23 13:03     ` Juanma Barranquero

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=uptp5ll2m.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    --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 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.