-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Tim Cross <theophil...@gmail.com> writes:
> Sharon Kimble <boudic...@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-----