From: Andreas Schwab <schwab@suse.de>
Cc: Eli Zaretskii <eliz@elta.co.il>, emacs-devel@gnu.org
Subject: Re: NTEmacs build fails
Date: Thu, 02 Oct 2003 15:49:40 +0200 [thread overview]
Message-ID: <jen0cj4umj.fsf@sykes.suse.de> (raw)
In-Reply-To: <uzngjrfml.fsf@boost-consulting.com> (David Abrahams's message of "Thu, 02 Oct 2003 08:25:06 -0400")
David Abrahams <dave@boost-consulting.com> writes:
> 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?"
Restarting the build from scatch.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-10-02 13:49 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
2003-10-02 13:49 ` Andreas Schwab [this message]
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=jen0cj4umj.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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).