From: Tim Cross <theophilusx@gmail.com>
To: glyn@millingtons.org
Cc: Emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-plus-contrib fails to compile
Date: Wed, 02 May 2018 04:00:08 +1000 [thread overview]
Message-ID: <877eonxnmf.fsf@gmail.com> (raw)
In-Reply-To: <87lgd3vjag.fsf@nowhere.org>
Glyn Millington <glyn.millington@gmail.com> writes:
> Good morning list!
>
> Emacs 25.3.1 on Linux
>
> For many upgrades now (over the last year or so) when I have tried
> to upgrade org-plus-contrib with the package management system
> pointed at the Org repository, the package is installed but
> compilation fails with a massive (23.6MB!) backtrace which begins
> like this:
>
>
> Debugger entered--Lisp error: (void-variable This)
> eval-buffer(#<buffer *load*> nil
> "/home/glyn/.emacs.d/elpa/org-plus-contrib-20180430/org" nil t)
> ; Reading at buffer position 5
> load-with-code-conversion("/home/glyn/.emacs.d/elpa/org-plus-contrib-20180430/org"
> "/home/glyn/.emacs.d/elpa/org-plus-contrib-20180430/org" nil t)
>
> None of the lisp files in the package are compiled.
>
> Can anyone point me to likely sources of the problem (my own
> cluelessness goes without saying! ) ?
>
I found this will most often occur because you have org loaded before
you try to do the upgrade. Basically, org gets confused because of
having an already loaded version while trying to install a new version.
I was seeing this quite often. Once I re-arranged by init file to ensure
that I can do a package upgrade before org is loaded, all works fairly
reliably.
An easy way to 'fix' the problem is to just delete the org-plus-contrib
directory from your ELPA directory, then restart emacs. Your emacs will
probably downlload and install the package during startup. Just make
sure your org setup comes after your package setup.
--
Tim Cross
next prev parent reply other threads:[~2018-05-01 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 9:04 org-plus-contrib fails to compile Glyn Millington
2018-05-01 10:37 ` Bastien
2018-05-01 18:00 ` Tim Cross [this message]
2018-05-01 18:23 ` Glyn Millington
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=877eonxnmf.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=glyn@millingtons.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/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).