From: Sharon Kimble <boudiccas@skimble09.plus.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Failing to load, showing this 'Symbol's function definition is void: defvar-1'
Date: Sun, 18 Dec 2022 13:58:59 +0000 [thread overview]
Message-ID: <87h6xsn78c.fsf@skimble09.plus.com> (raw)
In-Reply-To: <86v8m9ts30.fsf@gmail.com> (Tim Cross's message of "Sun, 18 Dec 2022 12:24:49 +1100")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Tim Cross <theophilusx@gmail.com> writes:
> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> I unfortunately upgraded this morning to emacs-30.0.50, and since then I can't get into my usual emacs of 29.0.50.
>>
>> When I'm loading emacs-29.0.50 from /usr/local/bin/ it is consistently failing to load
>> saying "Symbol's function definition is void: defvar-1".
>>
>> My init.el is this -
>> ====
>> ;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
>> ;; Make sure that Git version of Org mode is being loaded instead of the built-in version.
>> (add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa/org-9.5.5"))
>> ;;;(add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa/org-9.6"))
>> (add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-contrib/lisp"))
>>
>> (require 'package)
>> (setq package-enable-at-startup nil)
>> (package-initialize)
>>
>>
>> (require 'ob-tangle)
>> (org-babel-load-file "/home/boudiccas/.emacs.d/config22-2.org")
>> ====
>>
>> It seems to be baulking at the last 2 lines, can somebody help please?
>>
>> Thanks
>> Sharon.
>
> Emacs 30.0.50 is the bleeding edge of the development tree. It will be
> unstable by definition. The error you are getting looks like an internal
> Emacs error unrelated to org mode.
>
> I would wait a day or so and pull new sources and re-build to see if the
> issue is fixed. If not, log a bug report.
>
> If a working Emacs is critical to your activities, I would revert back
> to 28.2 or maybe 29, which is in pre-release state, so a little more
> stable than the bleeding edge dev code. Note that there is an Emacs 29
> branch, so you can checkout emacs-29 to get the most recent release
> candidate for Emacs 29.
>
> In general, org mode won't attempt to fix issues introduced in the HEAD
> soruces of Emacs as these sources tend to be in flux and issues will
> often be resolved by other non-org specific changes. Issues at this
> level tend to be a 'wait and see'.
Thanks for replying Tim, and as you can see I'm back in emacs.
I know that building emacs isn't part of org-modes mailing list setup, but it looked like '(require 'ob-tangle)' was causing the problem, hence I asked the org-mode mailing list.
For the benefit of the archives these are the steps I took -
====
make clean
make distclean
sudo make clean
sudo make distclean
delete /home/foo/git/emacs
git clone -b master git://git.sv.gnu.org/emacs.git
cd git/emacs
git checkout origin
git checkout emacs-29
/autogen.sh
configure
make
src/emacs -Q ;;; if this works, then try loading emacs, and if that works, then bobs your uncle!
sudo make install
====
This is because I'd got a failed build and install, so it all needed clearing out before I could delete the failed emacs git download, so it needed a fresh download.
Anyway, I've learnt from my mistake and have documented it all just in case I do it again.
Thanks
Sharon.
- --
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 11.5, fluxbox 1.3.7, emacs 29.0.60, org 9.5.5
-----BEGIN PGP SIGNATURE-----
iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmOfHKMdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1ttMg//YqH3l+FBRjrZySmW
OEE4YPEqCh4vDCoRhXd9iiybpvMHCDlqk1lWlR6cEqL9Fd0487N9VCFqRNHSvbtt
2La7rsVhholHVCYGuu9EIl20ogpty8O1IQgMMySm+v7pKu1Wch1djAzLcT1bxdAX
v2BC8M6aNRimA67/cGO+xav8m7fhrtRXPXCjMTXzCp5Bb9qzvrMnt6sIU+r88+QW
W1znPB2NOHxexHoXDxJZXWXqVVlXIUOlYAFmK0hQ079z2w7tveuDlBVcLFXOYbbR
2J9a0dRbE/bSJVFDUDs7BLRZdEXOLyjy9ijdK2KBH5RfbDoO3zfqpZfbLXZlcy5R
ONhqRQvxQzV6Chkc5cYq3HLQlrmzbIU2SGZeZ4lQxPCBlCuWagtr94QTVScFNudj
ufyqtmm4zcOuFBKrQ5MSiqXfNv3XGAnNj2cgQ8M1XaPiVUl6oMQtWNWtkJ0kurZD
5UDAliqWMoefjl0T+p23VIKvwwiPdc4YCAxCi0PgvoTQGx/FxBSgecDh9a/6fZjm
XCzn7TQr90GGYA7VkNy0tUiW/8shqQBQaRmhNLQ03/ZIBxBB10IgX63xc9HK32ev
CBfRZubfjUWKJ4vRxvha149bCcg9FQy9rsCSN4OCYxXh95nUhJJlr6PD30jnnHY1
E4zflSI+cLcpB9p6l3d7Z86uvOk=
=5Wpq
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2022-12-18 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 15:58 Failing to load, showing this 'Symbol's function definition is void: defvar-1' Sharon Kimble
2022-12-18 1:24 ` Tim Cross
2022-12-18 13:58 ` Sharon Kimble [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=87h6xsn78c.fsf@skimble09.plus.com \
--to=boudiccas@skimble09.plus.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.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).