unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Cc: Eli Zaretskii <eliz@elta.co.il>, emacs-devel@gnu.org
Subject: Re: NTEmacs build fails
Date: Thu, 02 Oct 2003 08:25:06 -0400	[thread overview]
Message-ID: <uzngjrfml.fsf@boost-consulting.com> (raw)
In-Reply-To: <jells454lc.fsf@sykes.suse.de> (Andreas Schwab's message of "Thu, 02 Oct 2003 12:14:23 +0200")

Andreas Schwab <schwab@suse.de> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>> "Eli Zaretskii" <eliz@elta.co.il> writes:
>>
>>>> From: David Abrahams <dave@boost-consulting.com>
>>>> Date: Wed, 01 Oct 2003 07:03:56 -0400
>>>> 
>>>> Thank you!  There seem to be lots of "secret" build repairs in the
>>>> lisp/ directory (autoloads, recompile, ...).  Maybe there is a way to
>>>> hint at what to do when the main build fails?
>>>
>>> "make recompile", "make autoloads", and (in the top-level directory)
>>> "make bootstrap" are the top sellers.
>>
>> Thanks, but I meant automatically, as part of the build process.
>
> That should already work, if you do a fresh build.

What do you mean by "fresh?"  I did "nmake clean" from the nt/ directory...

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

  reply	other threads:[~2003-10-02 12:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 21:40 NTEmacs build fails David Abrahams
2003-10-01  5:55 ` Eli Zaretskii
2003-10-01 11:03   ` David Abrahams
2003-10-01 21:11     ` Eli Zaretskii
2003-10-01 22:33       ` David Abrahams
2003-10-02 10:14         ` Andreas Schwab
2003-10-02 12:25           ` David Abrahams [this message]
2003-10-02 13:49             ` Andreas Schwab
2003-10-02 15:01               ` David Abrahams
2003-10-02 15:43                 ` Andreas Schwab
2003-10-02 17:11                   ` David Abrahams
2003-10-03 16:06                     ` Andreas Schwab

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