From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Uberti <manuel.uberti@inventati.org>
Cc: 56981@debbugs.gnu.org
Subject: bug#56981: 29.0.50; No org-loaddefs.el file could be found from where org.el is loaded
Date: Thu, 04 Aug 2022 19:47:48 +0300 [thread overview]
Message-ID: <83bkt02bwr.fsf@gnu.org> (raw)
In-Reply-To: <3839aac3-dee8-9ded-0183-399b1d29e3b5@inventati.org> (bug-gnu-emacs@gnu.org)
> Date: Thu, 4 Aug 2022 18:16:53 +0200
> From: Manuel Uberti via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> After building Emacs sources with the following steps:
>
> git clean -fdx
> ./autogen.sh
> ./configure --with-harfbuzz --with-native-compilation --with-pgtk
> make bootstrap
> sudo make install
>
> When I do the following:
>
> - emacs -Q
> - C-x C-f /tmp/test.org RET
>
> This warning appears:
>
> WARNING: No org-loaddefs.el file could be found from where org.el is loaded.
> You need to run "make" or "make autoloads" from Org lisp directory
I cannot reproduce this.
Do you have org-loaddefs.el and org-loaddefs.elc in the lisp/org/
directory? They should be there.
next prev parent reply other threads:[~2022-08-04 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 16:16 bug#56981: 29.0.50; No org-loaddefs.el file could be found from where org.el is loaded Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:42 ` Lars Ingebrigtsen
2022-08-04 17:55 ` Peder O. Klingenberg
2022-08-05 5:38 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:45 ` Eli Zaretskii
2022-08-05 7:20 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 16:47 ` Eli Zaretskii [this message]
2022-08-04 19:03 ` Pankaj Jangid
2022-08-04 19:11 ` Lars Ingebrigtsen
2022-08-05 6:35 ` Pankaj Jangid
2022-08-05 12:10 ` bug#56981: bug#56982: 29.0.50; Loading org.el fails to load org-loaddefs from installed location Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkt02bwr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56981@debbugs.gnu.org \
--cc=manuel.uberti@inventati.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.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).