From: rustom <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: emacs build broken?
Date: Wed, 27 Jan 2010 23:44:51 -0800 (PST) [thread overview]
Message-ID: <363d22a1-d98d-4d05-9a5c-c90fdb590ec4@p13g2000pre.googlegroups.com> (raw)
I did (for a emacs 23 build)
$cvs update -dP
$make distclean
make bootstrap
After a lot of grinding it stops at (last few lines)
Generating autoloads for mail/rmailmm.el...
Generating autoloads for mail/rmailmsc.el...
Generating autoloads for mail/rmailout.el...
Generating autoloads for mail/rmailout.el...done
Generating autoloads for mail/rmailsort.el...
Generating autoloads for mail/rmailsum.el...
End of file during parsing
make[3]: *** [autoloads] Error 255
make[3]: Leaving directory `/home/siva/pdsw/emacs/lisp'
make[2]: *** [/home/siva/pdsw/emacs/src/../lisp/loaddefs.el] Error 2
make[2]: Leaving directory `/home/siva/pdsw/emacs/src'
make[1]: *** [src] Error 2
make[1]: Leaving directory `/home/siva/pdsw/emacs'
make: *** [bootstrap] Error 2
When I did downloaded a fresh tar.bz2 of 23.1 it has compiled ok.
So I guess this is a broken build.
So ok... during development builds can break.
My question is how do I do a cvs update (rather than a full download)
and yet stay with relatively stable emacs versions?
next reply other threads:[~2010-01-28 7:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:44 rustom [this message]
2010-01-28 7:57 ` emacs build broken? rustom
2010-01-28 8:50 ` José A. Romero L.
2010-01-29 4:50 ` rustom
2010-01-29 5:44 ` rustom
2010-01-29 6:00 ` Tim X
2010-01-29 9:43 ` José A. Romero L.
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=363d22a1-d98d-4d05-9a5c-c90fdb590ec4@p13g2000pre.googlegroups.com \
--to=rustompmody@gmail.com \
--cc=help-gnu-emacs@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).