emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Something has happened such that I can't export to latex
@ 2022-07-26 15:32 Sharon Kimble
  2022-07-26 15:37 ` Ihor Radchenko
  0 siblings, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-26 15:32 UTC (permalink / raw)
  To: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

    
Just trying to export to latex this afternoon and this showed in the
mini-buffer -

- ----
| (void-variable org-latex-babel-language-alist) in org-latex-template
- ----

and this showed in the debugger -

- ----    
|Debugger entered--Lisp error: (void-variable org-latex-babel-language-alist)
|  org-latex--format-spec((:export-options nil :back-end #s(org-export-backend :name latex :parent nil :transcoders (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :options (... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...) :filters (... ... ... ...) :blocks nil :menu (108 "Export to LaTeX" ...)) :translate-alist ((bold . org-latex-bold) (center-block . org-latex-center-block) (clock . org-latex-clock) (code . org-latex-code) (drawer . org-latex-drawer) (dynamic-block . org-latex-dynamic-block) (entity . org-latex-entity) (example-block . org-latex-example-block) (export-block . org-latex-export-block) (export-snippet . org-latex-export-snippet) (fixed-width . org-latex-fixed-width) (footnote-definition . org-latex-footnote-definition) (footnote-reference . org-latex-footnote-reference) (headline . org-latex-headline) (horizontal-rule . org-latex-horizontal-rule) (inline-src-block . org-latex-inline-src-block) (inlinetask . org-latex-inlinetask) (italic . org-latex-italic) (item . org-latex-item) (keyword . org-latex-keyword) (latex-environment . org-latex-latex-environment) (latex-fragment . org-latex-latex-fragment) (line-break . org-latex-line-break) (link . org-latex-link) (node-property . org-latex-node-property) (paragraph . org-latex-paragraph) ...) :exported-data #<hash-table eq 15332/20251 0x1587aafeff57> :input-buffer "kpe.org" :input-file "/home/boudiccas/research/w..." :latex-class "my-report" :latex-class-options "[a4paper,11pt,twoside,open..." :latex-header "\\input{/home/boudiccas/res..." :latex-header-extra nil :description nil :keywords nil :subtitle nil ...))
|  org-latex-template(#("\n\n\\chapter{Boo..." 11 25 ... 90 94 ... 96 138 ... 249 253 ... ...) (:export-options nil :back-end ... :translate-alist ... :exported-data #<hash-table eq 15332/20251 0x1587aafeff57> :input-buffer "kpe.org" :input-file "/home/boudicca..." :latex-class "my-report" ...))
|  org-export-as(latex nil nil nil (:output-file "kpe.tex"))
|  org-export-to-file(latex "kpe.tex" nil nil nil nil nil)
|  org-latex-export-to-latex()
|  funcall-interactively(org-latex-export-to-latex)
|  call-interactively(org-latex-export-to-latex nil nil)
|  command-execute(org-latex-export-to-latex)
- ----

I just updated my emacs's packages, and also my org-mode installation,
but its still failing such that I cannot export to latex like I have
been able to.

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.2
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLgCP0dHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1tuwxAAnGf+OjubV45Bl9dq
ZJvm1YaSSq0N9XCtOF3eqF1kWpldXWuHxPlVa//4lsfU747m1UPorqj6a5mw7zPx
RmQf65uxAxPqAjrSekAc7MSOJ1+OqfvyFSeVwHjQzeDV18pMtayfl4FRF7fz1kwD
thHfZY+61h+y+ePuJhhlzAIX4++HpwYELq6SGHAhOHAN1CIQ9yaL11AK27SDE8Ey
H1wv3C7M2e8AeaZ4I4irXCOjDfCiSG1kQGOTs3g42FGBj5ykSkihC4tOgECdOCrP
RKebJQWtbSP4Mu8OmvrorD0Xf5Rt6ZSZXQT/x62nAcT3dbgA+RIqn0FB5zyX31vd
epsi1aYZoZlMzlcc+R4XZQNh3wfZB2/U7t9/mQfnQHiRFnItztzXe6DHo6EcfC7H
VfmADk3Gada8qI8nVWKfuImDiwvy/naQbNSzWSOCRDBRTJ6y0wJlxnvNbbr9puQP
CXflxGFWb5nlnRI+qVSALgeT4gLG1mdHUtuXEjavRUhFMg2DNxUs2cGStb0BijEN
KaXelNeFk//G34w0IM3OPtf2l16AWqBKv5BGiJg8TpNc0ck1+SryLJ4KflT/S/Iq
rfDOKDJdDR3r1EwVknAMseK3r0/6A5jLldpwjJWSuF3NmtGS9mfp60DNtJGBfp6D
wejP4v7PzB1s/OkqZeQiQWv6z1Y=
=HjWD
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-26 15:32 Something has happened such that I can't export to latex Sharon Kimble
@ 2022-07-26 15:37 ` Ihor Radchenko
  2022-07-26 16:33   ` Sharon Kimble
                     ` (2 more replies)
  0 siblings, 3 replies; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-26 15:37 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 289 bytes --]

>
> Just trying to export to latex this afternoon and this showed in the
> mini-buffer -
> - ----
> | (void-variable org-latex-babel-language-alist) in org-latex-template
> - ----

Please update again. The bug has been introduced recently, but should be
fixed on main already.

Best,
Ihor

[-- Attachment #2: Type: text/html, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-26 15:37 ` Ihor Radchenko
@ 2022-07-26 16:33   ` Sharon Kimble
  2022-07-26 16:39   ` Sharon Kimble
  2022-07-27  6:30   ` Sharon Kimble
  2 siblings, 0 replies; 23+ messages in thread
From: Sharon Kimble @ 2022-07-26 16:33 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

>  Just trying to export to latex this afternoon and this showed in the
>  mini-buffer -
>  - ----
>  | (void-variable org-latex-babel-language-alist) in org-latex-template
>  - ----
>
> Please update again. The bug has been introduced recently, but should be fixed on main already.
>
> Best,
> Ihor

Thanks Ihor.

How can I install my new org-mode setup from git please? The only way
that I know of is to close emacs down, and then start it again.

So can you advise please?            

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.2
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLgF0cdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1vZMhAAyPWGvoRn9TkxiDrs
GTa188ybcGuDQoRbRlcdncXeLdmFB7ijJT89QNiJdO52Ni2GPHRS76akwocmdUSJ
vriQX7wneOMqF29FYrkUwmt5V5TOEAHflIRD/YIfONqOCf9zi8TI+0AZOhFsZh3f
m+PkHlNmiwJftF/QnUMJDqf858CB0CYz6qO/ghRDQXrpQYCPNFF7iyqYp4enEiwY
V+VWtJXaP7RiKU6+E2cBzLlU4OkdzsAKBiVmqiosF52n3yNPNeUJgpzswedVitkU
Jwhc7KBI6NwEhYIx10EXhoZUi4h/OChDmfStbsmGXtjsieR846RjDb0MVifJx+7p
Yb5Ofio52V/B2qzJROrCPkJ0+OiH/Ty6sKDQnS3uCpdAUCy+5yQ2YoA9e3w5D9zc
nhN2fkRr/6buMGLadfgZ8tF7LBOyNgbIHmEIKmne+pP3kYv2wtuVYERSW/nyjk/D
3Hu2YyvGk8ixC2X3P75AAnJlhDx4RL4r5kbIyXB8ahdF7xktCJQPSW2DI18W0ozW
CjytZgescYst2v5FaV/G7tJjGw2Bc72KUhlzjTWCciwFXS9t1x5PY1XT/yULcWCH
8T0n9NzaPIn2KFboO0ZvdszdxfePHBXjLFjGOjm9cVi18T5lw2T/y20Qwz7y2FXI
99BPaoSKowyBvdmzzLqEI18uLyA=
=IYKy
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-26 15:37 ` Ihor Radchenko
  2022-07-26 16:33   ` Sharon Kimble
@ 2022-07-26 16:39   ` Sharon Kimble
  2022-07-27  3:41     ` Ihor Radchenko
  2022-07-27  6:30   ` Sharon Kimble
  2 siblings, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-26 16:39 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

>  Just trying to export to latex this afternoon and this showed in the
>  mini-buffer -
>  - ----
>  | (void-variable org-latex-babel-language-alist) in org-latex-template
>  - ----
>
> Please update again. The bug has been introduced recently, but should be fixed on main already.
>
> Best,
> Ihor
Sorry, I forgot that I can do it from the menu. Now I've updated I get this error message -

- ----    
|   Debugger entered--Lisp error: (void-variable org-link--description-folding-spec)
|      org-fold-initialize(" ▶▶▶")
|      org-mode()
|      #f(compiled-function () #<bytecode -0x2e9ea549cfbb7f8>)()
|      org-export-copy-buffer()
|      org-export-as(latex nil nil nil (:output-file "kpe.tex"))
|      org-export-to-file(latex "kpe.tex" nil nil nil nil nil)
|      org-latex-export-to-latex()
|      funcall-interactively(org-latex-export-to-latex)
|      call-interactively(org-latex-export-to-latex nil nil)
|      command-execute(org-latex-export-to-latex)   
- ----   

Any ideas please?

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLgGNUdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1vA2w//ZvrfqUW3C2BrlPDh
E1K4OZrC8TC4AsyqFpsVWs3P8ByVv21wi8Rhgo7iSpxx/+nE//oPjGm7kk6nXwna
DWDou8edxBIdHc6HXCRlCS3YbHtfzxr8D/k46JFN+JwrgbocMQtIM6a2AwYW7eV6
zccAPQ/TVyW5fRp9ew/N17Jg/yhqI2SrG5G0NpZMLCbIx/crtYxXGg5N80ouz7JD
pvgmQThz06tiU//Zoct8VGB7ubzBmta96ixV0gIOhQ6dplZ+FCyiBpbfG9wSUHTY
4dwa/ArZHDSFpAk2m5ylF8hyYdy2C+dKDyIjpV/nfTuHyXznJvka6Sc7TfN3Xw5b
5itrp4elz8iGrNr7ENehmplOwfPanqETibeOpC+GHkDGls1hgmCfn6cl35dcAJQ7
YobvHJhlnYwFNAALCp28KXZGdOY0m9J+y3txeTBEQPKGNIX/SRFfJCpOiEUP28Q+
Snw441U75tCcq1xvYvT7aopxOLBnUmSqEc01CAZYEMRx1fqdtRd9IS3ObgtbZaru
5L0raAFh3YRqnQvJY3a+T9tpvZYEm0GG/bOP4lOsSrZbVXy+OtTeKq7SFDETSK1n
KPD0a+uGsalIVjO3e/IotRDftgiS1oz6IfJ4GNs3et8pijZ+B9ViLcA6VTXFOAS6
bVcAXSlUDaLJ19WVVmD7ea7MQHE=
=YtLj
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-26 16:39   ` Sharon Kimble
@ 2022-07-27  3:41     ` Ihor Radchenko
  0 siblings, 0 replies; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-27  3:41 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> Sorry, I forgot that I can do it from the menu. Now I've updated I get this error message -
>
> - ----    
> |   Debugger entered--Lisp error: (void-variable org-link--description-folding-spec)
> |      org-fold-initialize(" ▶▶▶")

Please restart Emacs.

Best,
Ihor


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-26 15:37 ` Ihor Radchenko
  2022-07-26 16:33   ` Sharon Kimble
  2022-07-26 16:39   ` Sharon Kimble
@ 2022-07-27  6:30   ` Sharon Kimble
  2022-07-27 14:03     ` Fraga, Eric
  2022-07-27 14:16     ` Ihor Radchenko
  2 siblings, 2 replies; 23+ messages in thread
From: Sharon Kimble @ 2022-07-27  6:30 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

>  Just trying to export to latex this afternoon and this showed in the
>  mini-buffer -
>  - ----
>  | (void-variable org-latex-babel-language-alist) in org-latex-template
>  - ----
>
> Please update again. The bug has been introduced recently, but should be fixed on main already.
>
> Best,
> Ihor

Despite git pulling, etc, and restarting emacs, the problem still
remains.

This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
/home/boudiccas/git/org-mode/lisp/)'

Any ideas please?

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.2
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLg23AdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1th0A//cIMGlUf3XMc7CC/t
BuFtjfBODkom2n6fSnE5jPBIGCTd7mv3LJfviRWC6ZVW9K7OXuozoRV289yr7VBg
c0390rDglg6xyqjHcc6WEcnu0vWKus4H9LoW11jaVizXjugETM9rmtnVpmyf5dfx
U18YIkYxNngOMrYP3TDk1+39kPZEeRpXQOHfiUm8hNNbd/HG56+sq0H38RuHGcGU
sGX0ybduZb3QWmsUEnC6n4TteUK6mYk1jDeGWm6u+oau1u+d9NYwhFZsRWQugb3t
oWomBheUBIl+l8TzuStMfA59VV4so21hkNPrkQZvce5AabISCamI33IcrK4ZSBhE
Kk0GVXPjSgLQQVFMikjJBwBM9NdfGYkU6x/pGGxYrzTAcevWG5xrdjZsQv1dQXfX
Ijl+3QIUyJEDJtcZQjWApQ1E5f0CU7mC8KVzSdWVh3itmHX62hX6sZ7dOJFtZAgD
92eyIJ7sZDdwKjjZueq+E0CKbD4fxlq/unBF7dXNCOIFhPqONOPQRaIGTSKJ2kNz
z/ZHlxsS9gyNsI5KDt35+CbDuMDjac//o2AwXDKghoIm2ZsM1tq3Mm4OE5hufhHj
iHoJG4P44Symu7+/1Wdmdn4qOpdHzMykdlfJoPtVbLaJHcr60X/gcfflpg1Xx04E
sIRdd3ww1ShTEHCJtmMaRKhOlX4=
=1N2y
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27  6:30   ` Sharon Kimble
@ 2022-07-27 14:03     ` Fraga, Eric
  2022-07-27 14:16     ` Ihor Radchenko
  1 sibling, 0 replies; 23+ messages in thread
From: Fraga, Eric @ 2022-07-27 14:03 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: Ihor Radchenko, emacs-orgmode

> Despite git pulling, etc, and restarting emacs, the problem still
> remains.
>
> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
> /home/boudiccas/git/org-mode/lisp/)'

Sharon,

this looks like an old version (see my signature for a more recent version number).  Maybe you have a mixed installation?

-- 
: Eric S Fraga, with org release_9.5.4-648-gdf1814 in Emacs 29.0.50

^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27  6:30   ` Sharon Kimble
  2022-07-27 14:03     ` Fraga, Eric
@ 2022-07-27 14:16     ` Ihor Radchenko
  2022-07-27 15:20       ` Sharon Kimble
  2022-07-28  9:50       ` Sharon Kimble
  1 sibling, 2 replies; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-27 14:16 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> Despite git pulling, etc, and restarting emacs, the problem still
> remains.
>
> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
> /home/boudiccas/git/org-mode/lisp/)'
>
> Any ideas please?

Org 9.5.2 is a relatively old Org version. However, the error you are
getting was introduced in development version of Org (9.5.4+).
I suspect that you are loading some part of Org distribution from other
place. Not the Git folder you fetched.

Please make sure that you set the load-path for Org correctly early in
your config before you load Org or any package depending on Org.

Best,
Ihor


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27 14:16     ` Ihor Radchenko
@ 2022-07-27 15:20       ` Sharon Kimble
  2022-07-27 15:43         ` Fraga, Eric
  2022-07-27 23:02         ` Tim Cross
  2022-07-28  9:50       ` Sharon Kimble
  1 sibling, 2 replies; 23+ messages in thread
From: Sharon Kimble @ 2022-07-27 15:20 UTC (permalink / raw)
  To: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> Despite git pulling, etc, and restarting emacs, the problem still
>> remains.
>>
>> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
>> /home/boudiccas/git/org-mode/lisp/)'
>>
>> Any ideas please?
>
> Org 9.5.2 is a relatively old Org version. However, the error you are
> getting was introduced in development version of Org (9.5.4+).
> I suspect that you are loading some part of Org distribution from other
> place. Not the Git folder you fetched.
>
> Please make sure that you set the load-path for Org correctly early in
> your config before you load Org or any package depending on Org.
>
> Best,
> Ihor

Thanks Ihor.

I eventually tracked down that I was loading org-mode from '/usr/local/share/emacs/29.0.50/lisp/org/'.

So I've done a 'make clean', and then configured and built emacs to run from bootstrap, and now my org-version shows as 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @ /home/boudiccas/git/org-mode/lisp/)'.

However, if I build org-mode from git it shows as 'org-loaddefs: 9.5.4 (release_9.5.4-682-g5be0c7).

So I've rebooted and now emacs is showing my org-version as still 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @ /home/boudiccas/git/org-mode/lisp/)'.

So I've looked at my config file, and the first time that org is mentioned is -
=====
** installation
#+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results silent
;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
(require 'package)
(setq package-enable-at-startup nil)
(package-initialize)

(require 'ob-tangle)
(org-babel-load-file "~/.emacs.d/config22.org")
#+END_SRC
=====
and the first time that org-mode is mentioned is -                 
=====
** set pathways

#+begin_src emacs-lisp
;;(setq load-path (cons "~/.emacs.d/lisp" load-path))
;; This sets up the load path so that we can override it
(package-initialize nil)
;; Override the packages with the git version of Org and other packages
;;(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/"))
(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-contrib/lisp"))
;; Load the rest of the packages
(add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/lisp"))
;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/personal-elisp")
;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/test")
(add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa"))
;; (add-to-list 'load-path "/home/boudiccas/git")
(setq custom-file "/home/boudiccas/.emacs.d/lisp/custom.el")

(load custom-file)
#+end_src
=====

So how can I load the correct org-mode please?            

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.2
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLhV6kdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1se5g//bhQw5DnHJs4QxJtU
dnIXs9A33Q8561XvkUd9rmUf1fRhfitj+dIX9m7lYCr5CoeFzzBDHd/N+Me/nkAo
FbGGjVTEeQ1ypqoHe9w4w4U9Dv4vKKUVbmGFpA4svdrKnDgDXlAWckvNf7okjJin
qjbq7Y0gysrfW/hgtvWIq0AVdCoG9HzRXP1GV8aysRwqMhBCyGefNpj5noRAd6z/
0q4poqDMxozLZJvgkN20tbsrg/XVuHvEKkcyyMEyJNmyFUviY3iiUZ0X99Zp/S2F
MOUs/+h4RjqA3CLE6+RX2UUzYydD+ifosDWgO6uhWaHAqBxmcuK/Bo/Hlu4apVrC
s6lrNde7T3ub+s7Xxd8Goq+ARiuwtGU5df7Sb/8k+4PjU1mfUr61ySayGvHpaRVm
GLNURlG2RbNUijd0he7zXnXANcymHCKLkh4VXMOKETtLqP2vG7p2IKKX2iv9pztA
VomZscAL+stmEKSt6zr0jg3f1rCdkltG5VYKG0ZwJSdhwEuBjugOgYBXEKe6QXqy
GEi+FediBlbMiOAbOMvuLvWAdH16fYLegKoVLCbClhchRdeUztkCyAA2TeEZsaX7
sgVAb4ckFYST0lLBTLcl3i2x1rKTT4r0quf8pwMryeI+/UIhuHsvA4wpH9KEbD6X
+d/TwvxzbUt7pGTFjCwi7zfCW80=
=VvU8
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27 15:20       ` Sharon Kimble
@ 2022-07-27 15:43         ` Fraga, Eric
  2022-07-27 23:02         ` Tim Cross
  1 sibling, 0 replies; 23+ messages in thread
From: Fraga, Eric @ 2022-07-27 15:43 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

On Wednesday, 27 Jul 2022 at 16:20, Sharon Kimble wrote:
> So I've looked at my config file, and the first time that org is mentioned is -

So you use org-babel-load-file *before* you set the load-path.  Move the
two lines that set the load path for org to before you use
org-babel-load-path.  In my own init files, setting the path to org is
the first thing I do.

-- 
: Eric S Fraga, with org release_9.5.4-648-gdf1814 in Emacs 29.0.50

^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27 15:20       ` Sharon Kimble
  2022-07-27 15:43         ` Fraga, Eric
@ 2022-07-27 23:02         ` Tim Cross
  1 sibling, 0 replies; 23+ messages in thread
From: Tim Cross @ 2022-07-27 23:02 UTC (permalink / raw)
  To: emacs-orgmode


Note that identifying when org is loaded is not always
straight-forward. There are lots of packages which include org support
which can result in org being loaded as a side effect when you load
them. This is especially true of non-core packages which will use
explicit require statements rather than relying on autoloads etc.

For this reason, I always ensure that anything relating to org source
paths etc is loaded as early as possible. 

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

>
> So I've looked at my config file, and the first time that org is mentioned is -
> =====
> ** installation
> #+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results silent
> ;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
> (require 'package)
> (setq package-enable-at-startup nil)
> (package-initialize)
>
> (require 'ob-tangle)
> (org-babel-load-file "~/.emacs.d/config22.org")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is when org is being loaded as ob-tangle is part of org. This will
mean the built-in/bundled version of org is loaded.

> #+END_SRC
> =====
> and the first time that org-mode is mentioned is -                 
> =====
> ** set pathways
>
> #+begin_src emacs-lisp
> ;;(setq load-path (cons "~/.emacs.d/lisp" load-path))
> ;; This sets up the load path so that we can override it
> (package-initialize nil)
> ;; Override the packages with the git version of Org and other packages
> ;;(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/"))
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-contrib/lisp"))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This isn't going to work as you hope. You have already loaded org mode
when you called (require 'ob-tangle),

so what this is doing is adding an additional path to a latter version
of org which is going to result in a 'mixed' version. This will cause
lots of issues.

You either  need to move the above lines *above* the require 'ob-tangle
or move the earlier lines to after these ones. I think earlier is better
when it comes to org as there are many packages which include org
support and which will load org as a hidden side effect. 

> ;; Load the rest of the packages
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/lisp"))
> ;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/personal-elisp")
> ;; (add-to-list 'load-path "/home/boudiccas/.emacs.d/test")
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/.emacs.d/elpa"))
> ;; (add-to-list 'load-path "/home/boudiccas/git")
> (setq custom-file "/home/boudiccas/.emacs.d/lisp/custom.el")
>
> (load custom-file)
> #+end_src
> =====
>
> So how can I load the correct org-mode please?            
>

I note your appear to be running both the development version of Emacs
as well as the git version of org mode. While this will give you the
most recent versions of both, it will also mean your working with the
most unstable versions of both. If you rely on org for your daily
workflow, I would recommend

1. Just running with the version of org bundled with Emacs. Being the
development version, it will stay reasonably up-to-date as you really
need to update and re-build Emacs every week or so anyway.

or

2. Just use the org from ELPA and org-contrib from non-GNU ELPA. These
are usually the most stable versions with bug fixes applied. This would
be my recommendation. 

I think few people actually need to run from the head of the git
repository. Your messages indicated that having a broken org
installation was a significant issue for you and getting the issues
resolved are quite urgent. Using the ELPA/non-GNU packages will ensure
you get important bug fixes while keeping your org version current with
the most recent stable version and is probably the best choice for
anyone who needs a reliable org for production/daily use. 



^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-27 14:16     ` Ihor Radchenko
  2022-07-27 15:20       ` Sharon Kimble
@ 2022-07-28  9:50       ` Sharon Kimble
  2022-07-28 10:20         ` Ihor Radchenko
  1 sibling, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-28  9:50 UTC (permalink / raw)
  To: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> Despite git pulling, etc, and restarting emacs, the problem still
>> remains.
>>
>> This is on org-mode 'Org mode version 9.5.2 (release_9.5.2-25-gaf6f12 @
>> /home/boudiccas/git/org-mode/lisp/)'
>>
>> Any ideas please?
>
> Org 9.5.2 is a relatively old Org version. However, the error you are
> getting was introduced in development version of Org (9.5.4+).
> I suspect that you are loading some part of Org distribution from other
> place. Not the Git folder you fetched.
>
> Please make sure that you set the load-path for Org correctly early in
> your config before you load Org or any package depending on Org.
>
> Best,
> Ihor

After several rebuilds of emacs I'm now getting this line showing for
    org-version -

Org mode version 9.5.4 (release_9.5.4-17-g6e991f @ mixed installation!
    /home/boudiccas/git/emacs/lisp/org/ and
    /home/boudiccas/git/org-mode/lisp/)

I want to stay with the git version of org-mode if possible, so how do I
    stop the emacs org from operating please?         

Thanks everyone
    Sharon.    
- -- 
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 11, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLiW/kdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1sZpA/9EpnIpSiBGvytEZ7A
B+pSO29oQoVx/OoexFb3vQabZk1WTrH01Jjy+6xynxwIgy4DB044yg5CzW4P5yfC
Bp9RA32T+RFJjD2l4TLPs64cjzu2EC6wp9Jy8v0dVEIcl8KVopfRR5+j9HCSC16q
051qusl4VPrKmVX6h8/Yt3HmZ/dAVTh49p5aZeFeATdK8Fdtyj1HMfV/gv8hcvgi
WlyqBKToXGl57JLOhPhphkcH9j8TSeL5GwLFo4YKOcwGT6Y1Sb1EyZ23kiohuoth
uLKPoOlufkIiKSkPBion/pSk3OXzN6Gnc7hypdr/Y72nU2RntAA/tnft9kxHbc8R
byUFnPNDhP54b1LgjqxCBN1v6bzmb+5ZnPwu5UkyMu7uiNOGO8otM54Nv2XedJ8J
JklT0gLBvBK5X3CUr0oit+z+K1qEX/HpPfIFdmioxqKtZr7ivBfiGNQ5wegIbWIZ
lPJYLBDzHcvcBseQMDbfJ1SkDvESuAsIJVrfalOO2xjPfCKpALyxA8S7UHCCvLfm
SKOlxqjZm3rTaN0kIWZYXIhhNnURgVmSqRNcJ/8NXf/FF6aS7aeGYG3+51Dz514c
YovLXfAPQ2Ob6cadVX6hoMIHnm5LSUslMLvaTBvNkFBr3zPe2iiJZtj7t6tnzMwq
2mU8wlQXACey4+XmDJKqfpb2uZg=
=gwXa
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-28  9:50       ` Sharon Kimble
@ 2022-07-28 10:20         ` Ihor Radchenko
  2022-07-28 13:29           ` Sharon Kimble
  0 siblings, 1 reply; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-28 10:20 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> After several rebuilds of emacs I'm now getting this line showing for
>     org-version -
>
> Org mode version 9.5.4 (release_9.5.4-17-g6e991f @ mixed installation!
>     /home/boudiccas/git/emacs/lisp/org/ and
>     /home/boudiccas/git/org-mode/lisp/)
>
> I want to stay with the git version of org-mode if possible, so how do I
>     stop the emacs org from operating please?         

Try

#+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results silent
;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
(require 'package)
(setq package-enable-at-startup nil)

;; 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/git/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-contrib/lisp"))

(package-initialize)

(require 'ob-tangle)
(org-babel-load-file "~/.emacs.d/config22.org")
#+END_SRC

Hope it helps.

Best,
Ihor


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-28 10:20         ` Ihor Radchenko
@ 2022-07-28 13:29           ` Sharon Kimble
  2022-07-29  1:10             ` Ihor Radchenko
  0 siblings, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-28 13:29 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> After several rebuilds of emacs I'm now getting this line showing for
>>     org-version -
>>
>> Org mode version 9.5.4 (release_9.5.4-17-g6e991f @ mixed installation!
>>     /home/boudiccas/git/emacs/lisp/org/ and
>>     /home/boudiccas/git/org-mode/lisp/)
>>
>> I want to stay with the git version of org-mode if possible, so how do I
>>     stop the emacs org from operating please?         
>
> Try
>
> #+BEGIN_SRC emacs-lisp :tangle "~/.emacs.d/init.el" :exports code :results silent
> ;;; init.el --- sharon's config -*- eval: (read-only-mode 1) -*-
> (require 'package)
> (setq package-enable-at-startup nil)
>
> ;; 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/git/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name "/home/boudiccas/git/org-contrib/lisp"))
>
> (package-initialize)
>
> (require 'ob-tangle)
> (org-babel-load-file "~/.emacs.d/config22.org")
> #+END_SRC
>
> Hope it helps.
>

Thanks Ihor, its working well.

But, I'm unable to 'make autoloads' in the git version because its
    trying to connect to /usr/share/emacs and looking for something
    there which isn't there and just ends up deleting org-loaddefs, and the only way that
    I can get round it is by restoring git/org-mode from backup. 

Can you advise please as to how I can surmount that obstacle?

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLij0wdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1us7w/5AQntDTO/GQ0+VUH1
KQc/s5MHt7lq7FvIUpNpP9PyPPe19FHEeUJJgS+HV+MegcvEKQ6m5lhnSv1puy7Z
9iiT5RW4K/hf4fhbL8CDcDFxgJZNqJoIyOX/8VibEbLRw7DDrr4LypvjoYGhBM+k
ClQgTj8yOyrdzGwF7f0xkjrdYMEwaaxV41mmFI55VcUVIiT3S4GTea3bQGMNIE5h
LgX3WIPQqZnl72l4qW3xw0CmG+apkzLplLiXyXSaRweJI+uUba3qWZ1ADW7SJg97
/Xg/844VutYNTi/4xUgif6jShG2tEmfzNTqgjA677Gna/T33opdKT8uwxORmsIG+
SSQzLf3wsMVPHyxzeqOV8QzhGfhwIrhFTr03L6FXveLWlqEV1GOp40np8Lk3kSjX
NobJuglT1uf9qFg7OOpsu/Yh2qke5umTdMAoMEsUxzUNX24gfu18PrfC2ai9mpfe
VS6pJK2vW9PvNPm5drTX33uBJZ3ixS8sed0voxK4f5olwEYgxXSfi6CZzcno95SC
y4Bv/1v7kDP475B4ZmXrVer+41Pd07lS6Akq4r8DpXiw0maN37B1b/3YZfcJ7rZB
TLXFlNboBYhIPrb/s7URQNVtntcLbxDwZyjaef0YlyyjZ0TJjKpsoxK7NT/kmV4C
P3n5NKlwRAu52/dcri46mf8ih64=
=N9BT
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-28 13:29           ` Sharon Kimble
@ 2022-07-29  1:10             ` Ihor Radchenko
  2022-07-29  8:48               ` Sharon Kimble
  0 siblings, 1 reply; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-29  1:10 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> But, I'm unable to 'make autoloads' in the git version because its
>     trying to connect to /usr/share/emacs and looking for something
>     there which isn't there and just ends up deleting org-loaddefs, and the only way that
>     I can get round it is by restoring git/org-mode from backup. 
>
> Can you advise please as to how I can surmount that obstacle?

I am not sure. make autoloads should have nothing to do with
/usr/share/emacs

What exactly happens when you run make autoloads?

Best,
Ihor


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29  1:10             ` Ihor Radchenko
@ 2022-07-29  8:48               ` Sharon Kimble
  2022-07-29 12:00                 ` Robert Pluim
                                   ` (2 more replies)
  0 siblings, 3 replies; 23+ messages in thread
From: Sharon Kimble @ 2022-07-29  8:48 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> But, I'm unable to 'make autoloads' in the git version because its
>>     trying to connect to /usr/share/emacs and looking for something
>>     there which isn't there and just ends up deleting org-loaddefs, and the only way that
>>     I can get round it is by restoring git/org-mode from backup. 
>>
>> Can you advise please as to how I can surmount that obstacle?
>
> I am not sure. make autoloads should have nothing to do with
> /usr/share/emacs
>
> What exactly happens when you run make autoloads?
>
> Best,
> Ihor

Morning all.
    
=====
foo$ git pull
- From https://git.savannah.gnu.org/git/emacs/org-mode
   5be0c709b3..d37c0ee5fa  main       -> origin/main
Updating 5be0c709b3..d37c0ee5fa
Fast-forward
 lisp/org.el      | 2 +-
 lisp/ox-latex.el | 7 +++++--
 mk/org-fixup.el  | 2 +-
 3 files changed, 7 insertions(+), 4 deletions(-)
    
foo$ make autoloads
make -C lisp autoloads
make[1]: Entering directory '/home/boudiccas/git/org-mode/lisp'
rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
org-version: 9.5.4 (release_9.5.4-684-gd37c0e)
Warning: Lisp directory '/usr/local/share/emacs/29.0.50/lisp': No such file or directory
Cannot open load file: No such file or directory, loadup.el
make[1]: *** [Makefile:72: org-version.el] Error 255
make[1]: Leaving directory '/home/boudiccas/git/org-mode/lisp'
make: *** [mk/targets.mk:133: autoloads] Error 2
=====

Does this help please?

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLjnskdHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1u8LQ/6AyONH3DgnIBaCgHb
hX64gc4AmydhXDLCRHt5rAE3zBhgEUXtXOWaKmNIDaeLyiBcuqwPic5VEINrRVGF
Rb8VVEaShQTbF93w8N+m5QaGwbYabJ+3Iw7bcO8kmq1kxKIW+P812R1fHQyVdWeC
dq8EHbdZWoF2M2zROgVZxl6Vg8r+tBfk6vl9EZOjvUNrAeLKnMkZjJy9xgdCCJdE
Qt49rHnIVqSgfUMhOpDK6VFPx28ogC6627m+H2KMggXffKo/93W10EqxB2HEFPrd
UFrm0FW3U66AxwiZzpj1Zpe6KmRjl1FbgBsYoLIj+qG9QaQl07/0J8ltejN4V6m0
14r6VtGq+llafu+HMNBimyGmHlFKgh/cUwbjPns88aoxl/pZImTr8rlrfJKGuRSV
LNuQL0jiEbBvzO1G4lnOhYhbV3JzJaTZoigeZDffPgWRaRdsXE1/b9Vu3EMfYv7W
IMjrifgc5tD5r1GdhYSoQZg85bO+WjoauRv7+J3xzNVW4CWea5OrDQWAs3r1TfoW
vuikoGTIRkFVi2LujEFhmcl6ic97MYDth7DSIIZcjGplpeKDrJCYirpsNgjyrTJA
8B5MUWHfX9Jf5lgXZGOaNJ4tR0YA9O5OQXkk/xt2gUx7PaxlFA4GdcS6/cRecoAf
Lq/t3zewIk/oU4aPo83PorMoOMY=
=S0sG
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29  8:48               ` Sharon Kimble
@ 2022-07-29 12:00                 ` Robert Pluim
  2022-07-29 12:24                   ` Sharon Kimble
  2022-07-29 13:24                 ` Ihor Radchenko
  2022-07-30  3:18                 ` Tim Cross
  2 siblings, 1 reply; 23+ messages in thread
From: Robert Pluim @ 2022-07-29 12:00 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: Ihor Radchenko, emacs-orgmode

>>>>> On Fri, 29 Jul 2022 09:48:09 +0100, Sharon Kimble <boudiccas@skimble09.plus.com> said:

    Sharon> Morning all.
    
    Sharon> =====
    Sharon> foo$ git pull
    Sharon> From https://git.savannah.gnu.org/git/emacs/org-mode
    Sharon>    5be0c709b3..d37c0ee5fa  main       -> origin/main
    Sharon> Updating 5be0c709b3..d37c0ee5fa
    Sharon> Fast-forward
    Sharon>  lisp/org.el      | 2 +-
    Sharon>  lisp/ox-latex.el | 7 +++++--
    Sharon>  mk/org-fixup.el  | 2 +-
    Sharon>  3 files changed, 7 insertions(+), 4 deletions(-)
    
    Sharon> foo$ make autoloads
    Sharon> make -C lisp autoloads
    Sharon> make[1]: Entering directory '/home/boudiccas/git/org-mode/lisp'
    Sharon> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
    Sharon> org-version: 9.5.4 (release_9.5.4-684-gd37c0e)
    Sharon> Warning: Lisp directory '/usr/local/share/emacs/29.0.50/lisp': No such file or directory
    Sharon> Cannot open load file: No such file or directory, loadup.el
    Sharon> make[1]: *** [Makefile:72: org-version.el] Error 255
    Sharon> make[1]: Leaving directory '/home/boudiccas/git/org-mode/lisp'
    Sharon> make: *** [mk/targets.mk:133: autoloads] Error 2
    Sharon> =====

What does your local.mk contain? I donʼt think the default org
makefile references loadup.el anywhere.

Robert
-- 


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29 12:00                 ` Robert Pluim
@ 2022-07-29 12:24                   ` Sharon Kimble
  2022-07-29 12:37                     ` Robert Pluim
  0 siblings, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-29 12:24 UTC (permalink / raw)
  To: Robert Pluim; +Cc: Ihor Radchenko, emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Robert Pluim <rpluim@gmail.com> writes:

>>>>>> On Fri, 29 Jul 2022 09:48:09 +0100, Sharon Kimble <boudiccas@skimble09.plus.com> said:
>
>     Sharon> Morning all.
>     
>     Sharon> =====
>     Sharon> foo$ git pull
>     Sharon> From https://git.savannah.gnu.org/git/emacs/org-mode
>     Sharon>    5be0c709b3..d37c0ee5fa  main       -> origin/main
>     Sharon> Updating 5be0c709b3..d37c0ee5fa
>     Sharon> Fast-forward
>     Sharon>  lisp/org.el      | 2 +-
>     Sharon>  lisp/ox-latex.el | 7 +++++--
>     Sharon>  mk/org-fixup.el  | 2 +-
>     Sharon>  3 files changed, 7 insertions(+), 4 deletions(-)
>     
>     Sharon> foo$ make autoloads
>     Sharon> make -C lisp autoloads
>     Sharon> make[1]: Entering directory '/home/boudiccas/git/org-mode/lisp'
>     Sharon> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
>     Sharon> org-version: 9.5.4 (release_9.5.4-684-gd37c0e)
>     Sharon> Warning: Lisp directory '/usr/local/share/emacs/29.0.50/lisp': No such file or directory
>     Sharon> Cannot open load file: No such file or directory, loadup.el
>     Sharon> make[1]: *** [Makefile:72: org-version.el] Error 255
>     Sharon> make[1]: Leaving directory '/home/boudiccas/git/org-mode/lisp'
>     Sharon> make: *** [mk/targets.mk:133: autoloads] Error 2
>     Sharon> =====
>
> What does your local.mk contain? I donʼt think the default org
> makefile references loadup.el anywhere.
>
Thanks for replying Robert.

=====

# Remove "oldorg:" to switch to "all" as the default target.
# Change "oldorg:" to an existing target to make that target the default,
# or define your own target here to become the default target.
oldorg:	# do what the old Makefile did by default.

##----------------------------------------------------------------------
##  CHECK AND ADAPT THE FOLLOWING DEFINITIONS
##----------------------------------------------------------------------

# Name of your emacs binary
EMACS	= emacs

# Where local software is found
prefix	= /usr/local/share

# Where local lisp files go.
lispdir= $(prefix)/emacs/site-lisp/org

# Where local data files go.
datadir = $(prefix)/emacs/etc/org

# Where info files go.
infodir = $(prefix)/info

# Define if you only need info documentation, the default includes html and pdf
#ORG_MAKE_DOC = info # html pdf

# Define which git branch to switch to during update.  Does not switch
# the branch when undefined.
GIT_BRANCH = 

# Where to create temporary files for the testsuite
# respect TMPDIR if it is already defined in the environment
TMPDIR ?= /tmp
testdir = $(TMPDIR)/tmp-orgtest

# Configuration for testing
# add options before standard load-path
BTEST_PRE   =
# add options after standard load path
BTEST_POST  =
              # -L <path-to>/ert      # needed for Emacs23, Emacs24 has ert built in
              # -L <path-to>/ess      # needed for running R tests
              # -L <path-to>/htmlize  # need at least version 1.34 for source code formatting
BTEST_OB_LANGUAGES = awk C fortran maxima lilypond octave perl python
              # R                     # requires ESS to be installed and configured
              # ruby                  # requires inf-ruby to be installed and configured
# extra packages to require for testing
BTEST_EXTRA =
              # ess-site  # load ESS for R tests
# See default.mk for further configuration options.
=====

Does this help? Its been a very long time since I looked at it, and I don't think that I changed anything in it then.

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLj0Y4dHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1v3YQ//YZIRrIqIZjSdW9pe
SuTFsgZDYJD2w6M0+3sT2qiFrtN1PdeNvDZXshbVMEHX3ozyMB5GA0ioctAtiiD0
ohUID7oeZCwxBf/qMadRQ66vxiliw86AHdk0vEH72HdOFb0EPTD4ggUlIdYg8Agm
pHyG62ZKA6yEgwamnfd5gtxQtI+L4dqr3UbvoqBXgh4RBgvXX8OianrRDZHMgVp7
HwbTLEmeOFYuc8De+bzgLSkMrHBUzOFxtCmeFmIAraJ8KnJ5d0wUJBZOl1H0zhLH
UigeVK7WEJar8pjpSmEttyNYYo8ibJYe6wJZgtKtLHxDWhlG/HFCww3vLDu15tyl
iqpEWzqNhgL1cPYguDwRyIPi1s/s0ox6q2h5sXhCNHWsUVXq+x9WDYtBKM9P29Zk
y/0uh7qfUd3B783AOUPQ5YKPtzJBVqYZ1jFDwKI/GNDMPsKPiATJHTTSkU0ZVmEX
lpOrvvSNqd97+MBZE3xQ80HgnprN2/a4jS6sWr6hS7tcmmzrnFIABhiFZrDyKw5G
Sn0WzV+FtcScdlqvDneSL7Lte7xtYRXJc0RuRQDT33bTK9nNpcYNZKePwUww5rkx
n/21K1v59u1hTSTxkjva8Qie5pT/rXNBcRi8xqdu8nxtjFawjrGdoqwbsJ+vpM7D
8tW/OqkNALB16c9ybCH3TIbcJFw=
=Ut1g
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29 12:24                   ` Sharon Kimble
@ 2022-07-29 12:37                     ` Robert Pluim
  0 siblings, 0 replies; 23+ messages in thread
From: Robert Pluim @ 2022-07-29 12:37 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: Ihor Radchenko, emacs-orgmode

>>>>> On Fri, 29 Jul 2022 13:24:46 +0100, Sharon Kimble <boudiccas@skimble09.plus.com> said:
    >> What does your local.mk contain? I donʼt think the default org
    >> makefile references loadup.el anywhere.
    >> 

    Sharon> Does this help? Its been a very long time since I looked at it, and I don't think that I changed anything in it then.

Hmm, that doesnʼt reference loadup.el at all, which is normally passed
to temacs during the Emacs build process, not when running emacs
itself. Can you try removing the ʼ@ʼ from the start of the lines in
the recipe for $(LISPI) in lisp/Makefile and re-running the make? If
that contains loadup we need to figure out why.

Robert
-- 


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29  8:48               ` Sharon Kimble
  2022-07-29 12:00                 ` Robert Pluim
@ 2022-07-29 13:24                 ` Ihor Radchenko
  2022-07-30  7:25                   ` [SOLVED] " Sharon Kimble
  2022-07-30  3:18                 ` Tim Cross
  2 siblings, 1 reply; 23+ messages in thread
From: Ihor Radchenko @ 2022-07-29 13:24 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: emacs-orgmode

Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> foo$ git pull
> - From https://git.savannah.gnu.org/git/emacs/org-mode
>    5be0c709b3..d37c0ee5fa  main       -> origin/main
> Updating 5be0c709b3..d37c0ee5fa
> Fast-forward
>  lisp/org.el      | 2 +-
>  lisp/ox-latex.el | 7 +++++--
>  mk/org-fixup.el  | 2 +-
>  3 files changed, 7 insertions(+), 4 deletions(-)
>     
> foo$ make autoloads

Considering that you have a questionable local.mk, I suggested trying
cloning the Org repo from scratch. Just in case.

If that does not work, I suspect that you have some peculiar Emacs
installation. The error you are getting appears like Emacs compilation
wrongly set the environment somehow. It is the first time I am seeing
such a strange error.

Best,
Ihor


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: Something has happened such that I can't export to latex
  2022-07-29  8:48               ` Sharon Kimble
  2022-07-29 12:00                 ` Robert Pluim
  2022-07-29 13:24                 ` Ihor Radchenko
@ 2022-07-30  3:18                 ` Tim Cross
  2 siblings, 0 replies; 23+ messages in thread
From: Tim Cross @ 2022-07-30  3:18 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: Ihor Radchenko, emacs-orgmode


Sharon Kimble <boudiccas@skimble09.plus.com> writes:

> [[PGP Signed Part:Undecided]]
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>>
>>> But, I'm unable to 'make autoloads' in the git version because its
>>>     trying to connect to /usr/share/emacs and looking for something
>>>     there which isn't there and just ends up deleting org-loaddefs, and the only way that
>>>     I can get round it is by restoring git/org-mode from backup. 
>>>
>>> Can you advise please as to how I can surmount that obstacle?
>>
>> I am not sure. make autoloads should have nothing to do with
>> /usr/share/emacs
>>
>> What exactly happens when you run make autoloads?
>>
>> Best,
>> Ihor
>
> Morning all.
>     
> =====
> foo$ git pull
> From https://git.savannah.gnu.org/git/emacs/org-mode
>    5be0c709b3..d37c0ee5fa  main       -> origin/main
> Updating 5be0c709b3..d37c0ee5fa
> Fast-forward
>  lisp/org.el      | 2 +-
>  lisp/ox-latex.el | 7 +++++--
>  mk/org-fixup.el  | 2 +-
>  3 files changed, 7 insertions(+), 4 deletions(-)
>     
> foo$ make autoloads
> make -C lisp autoloads
> make[1]: Entering directory '/home/boudiccas/git/org-mode/lisp'
> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc
> org-version: 9.5.4 (release_9.5.4-684-gd37c0e)
> Warning: Lisp directory '/usr/local/share/emacs/29.0.50/lisp': No such file or directory
> Cannot open load file: No such file or directory, loadup.el
> make[1]: *** [Makefile:72: org-version.el] Error 255
> make[1]: Leaving directory '/home/boudiccas/git/org-mode/lisp'
> make: *** [mk/targets.mk:133: autoloads] Error 2
> =====
>
> Does this help please?
>

After you do a pull from git, I think you should always do a make clean
before trying anything else. The error is referencing a file which has
nothing to do with org, so I suspect something is wrong with your local
environment. I would also try

git clean -dxf

in the root of the org git tree just to ensure there are no files there
which don't belong. Follow that with make clean and make. 


^ permalink raw reply	[flat|nested] 23+ messages in thread

* [SOLVED] Re: Something has happened such that I can't export to latex
  2022-07-29 13:24                 ` Ihor Radchenko
@ 2022-07-30  7:25                   ` Sharon Kimble
  2022-07-31 19:49                     ` Robert Pluim
  0 siblings, 1 reply; 23+ messages in thread
From: Sharon Kimble @ 2022-07-30  7:25 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ihor Radchenko <yantar92@gmail.com> writes:

> Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>
>> foo$ git pull
>> - From https://git.savannah.gnu.org/git/emacs/org-mode
>>    5be0c709b3..d37c0ee5fa  main       -> origin/main
>> Updating 5be0c709b3..d37c0ee5fa
>> Fast-forward
>>  lisp/org.el      | 2 +-
>>  lisp/ox-latex.el | 7 +++++--
>>  mk/org-fixup.el  | 2 +-
>>  3 files changed, 7 insertions(+), 4 deletions(-)
>>     
>> foo$ make autoloads
>
> Considering that you have a questionable local.mk, I suggested trying
> cloning the Org repo from scratch. Just in case.
>
> If that does not work, I suspect that you have some peculiar Emacs
> installation. The error you are getting appears like Emacs compilation
> wrongly set the environment somehow. It is the first time I am seeing
> such a strange error.
>
    
Thank you to all who've been trying to sort out my problem, but I think that I've found the solution.

I have now rebuilt emacs with this bog-standard setup -

===
/autogen.sh
/configure
make
sudo make install
===

and it then builds org-loaddefs with zero problems.

My previous build was using this setup -

===
/autogen.sh
/configure
make bootstrap
make
===

And I suspect that the lone 'make' caused the problems, but I haven't done a test build to try it out.

I don't know where I got the bootstrap build mantra from, I must've found it online somewhere some time ago.

But thank you to all who tried to find a solution.

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, fluxbox 1.3.7, emacs 29.0.50, org 9.5.4
-----BEGIN PGP SIGNATURE-----

iQJRBAEBCgA7FiEELSc/6QwVBIYugJDbNoGAGQr4g1sFAmLk3PodHGJvdWRpY2Nh
c0Bza2ltYmxlMDkucGx1cy5jb20ACgkQNoGAGQr4g1s0fRAAwe3SJQjVZ0p+yxke
2FMin2cC6d2qoRlO3rIAimQ5irlvDY7JRD6rZU4pSLWb0MBvJv8bzvcKDGlfDpxy
W40abdsi1A0Pha1RyBAcGppaIlaHXLJMZ5qi+yIfiWX4/G1D219KRftaSKuO2WE9
T+UDaMRBhzIyMpGH5QB/L8sdgkw59YRPa5INj/c4B+oxpvjPxwp6+gCJpepyopzW
Skj/BXbywn1viM9Zce1e9SrAd83Sw6DbAVWERStl+4A5FI9nsD7j+U+g+pS1CAbU
I2+Ywgll8HAAqZAQLRsVq52EpLX4Mjc26lg2oz3/4iIAYPnTRl21VeLKvJ31frrs
ZfW7VatNGixXs6PV0OvlTIpvufT2cbiHx7OjZOj3hJY9fmVMci17eL8ZRBuyqpzb
GN2aZNYeaeDG8mBxy+qXdcOv9yqHLFfiqrByjhcfU15hQnvZfx7Dr6o6EuOfNjXU
lSp/Wn9R6G9Hh7XHoZBq5o1WmkKhvw2PWJondadJGgcId589vjw/89R83j7GzY3U
HnjW0MaFuOJRYFb9wD004gi7loPxGw0PPuLlPxs6scVSubX//RBNkBjf+JxIc31l
0Tnv1d+PX44J6XEB9HYIMVw4uhWnjRZHgGHOoEPXR6Ui7GvwZInoBLnE15KCrw5m
H98RE6esSb98lzqSFC6rBfEv+W0=
=DbuR
-----END PGP SIGNATURE-----


^ permalink raw reply	[flat|nested] 23+ messages in thread

* Re: [SOLVED] Re: Something has happened such that I can't export to latex
  2022-07-30  7:25                   ` [SOLVED] " Sharon Kimble
@ 2022-07-31 19:49                     ` Robert Pluim
  0 siblings, 0 replies; 23+ messages in thread
From: Robert Pluim @ 2022-07-31 19:49 UTC (permalink / raw)
  To: Sharon Kimble; +Cc: Ihor Radchenko, emacs-orgmode

>>>>> On Sat, 30 Jul 2022 08:25:46 +0100, Sharon Kimble <boudiccas@skimble09.plus.com> said:
    Sharon> ===
    Sharon> /autogen.sh
    Sharon> /configure
    Sharon> make bootstrap
    Sharon> make
    Sharon> ===

    Sharon> And I suspect that the lone 'make' caused the problems, but I haven't done a test build to try it out.

    Sharon> I don't know where I got the bootstrap build mantra from, I must've found it online somewhere some time ago.

If youʼve got a completely clean Emacs checkout, then thereʼs no real
difference between 'make' and 'make bootstrap'. The thing to know
about 'make bootstrap' is that you donʼt need to run 'make' again
afterwards, since everything will already have been built.

    Sharon> But thank you to all who tried to find a solution.

Iʼm glad you sorted it.

Robert
-- 


^ permalink raw reply	[flat|nested] 23+ messages in thread

end of thread, other threads:[~2022-07-31 19:50 UTC | newest]

Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-26 15:32 Something has happened such that I can't export to latex Sharon Kimble
2022-07-26 15:37 ` Ihor Radchenko
2022-07-26 16:33   ` Sharon Kimble
2022-07-26 16:39   ` Sharon Kimble
2022-07-27  3:41     ` Ihor Radchenko
2022-07-27  6:30   ` Sharon Kimble
2022-07-27 14:03     ` Fraga, Eric
2022-07-27 14:16     ` Ihor Radchenko
2022-07-27 15:20       ` Sharon Kimble
2022-07-27 15:43         ` Fraga, Eric
2022-07-27 23:02         ` Tim Cross
2022-07-28  9:50       ` Sharon Kimble
2022-07-28 10:20         ` Ihor Radchenko
2022-07-28 13:29           ` Sharon Kimble
2022-07-29  1:10             ` Ihor Radchenko
2022-07-29  8:48               ` Sharon Kimble
2022-07-29 12:00                 ` Robert Pluim
2022-07-29 12:24                   ` Sharon Kimble
2022-07-29 12:37                     ` Robert Pluim
2022-07-29 13:24                 ` Ihor Radchenko
2022-07-30  7:25                   ` [SOLVED] " Sharon Kimble
2022-07-31 19:49                     ` Robert Pluim
2022-07-30  3:18                 ` Tim Cross

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).