From: "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: still failing to "make" almost-cvs 21.3
Date: Sat, 17 Jul 2004 13:40:31 +0200 [thread overview]
Message-ID: <3791-Sat17Jul2004134031+0300-eliz@gnu.org> (raw)
In-Reply-To: <cd9u5n$hjv$1@panix2.panix.com> (dkcombs@panix.com)
> From: dkcombs@panix.com (David Combs)
> Newsgroups: gnu.emacs.help
> Date: 16 Jul 2004 21:08:07 -0400
>
> STILL trying to compile "almost-cvs" 21.3
This is the wrong place to discuss problems with building the CVS
code. Please in the future write to emacs-pretest-bug@gnu.org.
> ------- Repeating that code that caught me:
>
> maybe_bootstrap:
> @bar="`echo $(srcdir)/lisp/*.elc`"; \
> if [ \( "$$bar" = '$(srcdir)/lisp/*.elc' \) -o \( "$$bar" = '' \) ]; then \
> echo "Your tree does not include the compiled Lisp files."; \
> echo "You need to do \`make bootstrap' to build Emacs."; \
> echo "Emacs now requires Texinfo version 4.2."; \
> exit 1;\
> fi
That's right: the first time you build the CVS code after checking it
out, you need to say "make bootstrap".
> I've now gone and installed texinfo 4.2, and it's on $PATH.
>
> No, no .elc-files. Why didn't they get built? Beats me!
They are not in the CVS tree, and since your previous bootstrap
failed, they were not built.
> And, as instructed, I tried to do the "make bootstrap"; got this:
>
> 275 ==/big7.1/sources-stuff-2/emacs-21.3==>
> 275 ==/big7.1/sources-stuff-2/emacs-21.3==> make bootstrap
> (cd src; make mostlyclean)
> [Please ignore a syntax error on the next line - it is intentional]
Where did that message come from? The only place I can find it in the
CVS is in the nt/gmake.defs file, which should be only used on
Windows. Are you building this on Windows? If so, you need to follow
the Windows installation instructions in nt/INSTALL, except that you
should say "make bootstrap" instead of just "make".
> Huh?: "make[1]: *** No rule to make target `mostlyclean'. Stop."
Probably because you didn't run nt/configure.bat, and so there's no
Makefile in the `src' directory.
> Hey, cvs-maintainers, do I *really* have to hack this Makefile,
No, you don't.
> fix bugs in it?
What bugs? ;-)
next prev parent reply other threads:[~2004-07-17 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 1:08 still failing to "make" almost-cvs 21.3 David Combs
2004-07-17 11:40 ` Eli Zaretskii [this message]
2004-07-24 4:02 ` Harry Putnam
2004-07-24 8:46 ` Eli Zaretskii
2004-07-24 21:47 ` Harry Putnam
[not found] ` <mailman.1323.1090655484.1960.help-gnu-emacs@gnu.org>
2004-07-24 11:59 ` Miles Bader
2004-07-24 21:51 ` Harry Putnam
[not found] ` <mailman.218.1090061068.1960.help-gnu-emacs@gnu.org>
2004-07-24 0:38 ` David Combs
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=3791-Sat17Jul2004134031+0300-eliz@gnu.org \
--to=eliz@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.
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).