From: Nick Dokos <nicholas.dokos@hp.com>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Cleaning up my org setup, using version from git
Date: Fri, 22 Mar 2013 18:27:33 -0400 [thread overview]
Message-ID: <7644.1363991253@alphaville> (raw)
In-Reply-To: Message from Marcelo de Moraes Serpa <celoserpa@gmail.com> of "Fri\, 22 Mar 2013 15\:54\:45 MDT." <CACHMzOHVXwb-BEafpWzsQKam5vSsDPOoFNXBH6nn2_FCgvUHvA@mail.gmail.com>
Marcelo de Moraes Serpa <celoserpa@gmail.com> wrote:
> On Fri, Mar 22, 2013 at 3:35 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>
> Did you `make autoloads'?
> Yes,
>
> org git:(master): make autoloads
> ======================================================
> = Invoke "make help" for a synopsis of make targets. =
> = Created a default local.mk template. =
> = Setting "oldorg" as the default target. =
> = Please adapt local.mk to your local setup! =
> ======================================================
> End of file during parsing
> make: [local.mk] Error 255 (ignored)
> make -C lisp autoloads
> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
> org-version: 8.0-pre (release_8.0-pre-150-g412d98)
> End of file during parsing
> make[1]: *** [org-version.el] Error 255
> make: *** [autoloads] Error 2
>
Well, you issued the command but the make failed. So you need to
investigate why it is failing. `make autoloads' removes some existing
files and then tries to rebuild them. One of those is org-loaddefs.el -
the fact that you don't have it shows that the rebuild failed.
The rebuild is done by this rule in lisp/Makefile:
,----
| autoloads: cleanauto addcontrib $(LISPI) $(LISPV)
|
| $(LISPV): $(LISPF)
| @echo "org-version: $(ORGVERSION) ($(GITVERSION))"
| @$(RM) $(@)
| @$(MAKE_ORG_VERSION)
`----
and MAKE_ORG_VERSION is defined in mk/default.mk:
,----
| # Using emacs in batch mode.
| # BATCH = $(EMACS) -batch -vanilla # XEmacs
| BATCH = $(EMACS) -batch -Q
|
| # Emacs must be started in lisp directory
| BATCHL = $(BATCH) \
| --eval '(add-to-list '"'"'load-path ".")'
|
| # How to generate org-version.el
| MAKE_ORG_VERSION = $(BATCHL) \
| --eval '(load "org-compat.el")' \
| --eval '(load "../mk/org-fixup.el")' \
| --eval '(org-make-org-version "$(ORGVERSION)" "$(GITVERSION)" "$(datadir)")'
`----
But you have a syntax error in some file (End of file during parsing - as I said,
probably a missing paren or some such) that causes emacs to exit abnormally.
Nick
prev parent reply other threads:[~2013-03-22 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 20:04 Cleaning up my org setup, using version from git Marcelo de Moraes Serpa
2013-03-22 21:02 ` Nick Dokos
2013-03-22 21:27 ` Marcelo de Moraes Serpa
2013-03-22 21:35 ` Thomas S. Dye
2013-03-22 21:54 ` Marcelo de Moraes Serpa
2013-03-22 22:19 ` Thomas S. Dye
2013-03-22 22:24 ` Marcelo de Moraes Serpa
2013-03-22 22:35 ` Nick Dokos
2013-03-22 22:27 ` Nick Dokos [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7644.1363991253@alphaville \
--to=nicholas.dokos@hp.com \
--cc=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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/org-mode.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).