From: Tim Cross <theophilusx@gmail.com>
To: Sharon Kimble <boudiccas@skimble09.plus.com>
Cc: Ihor Radchenko <yantar92@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Something has happened such that I can't export to latex
Date: Sat, 30 Jul 2022 13:18:30 +1000 [thread overview]
Message-ID: <86bkt746yu.fsf@gmail.com> (raw)
In-Reply-To: <871qu4e246.fsf@skimble09.plus.com>
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.
prev parent reply other threads:[~2022-07-30 3:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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=86bkt746yu.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=boudiccas@skimble09.plus.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).