all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: org: problem loading compiled files that use org-element
Date: Thu, 04 Jul 2024 07:46:26 -0700	[thread overview]
Message-ID: <p91plrtnrjx.fsf@google.com> (raw)
In-Reply-To: <86ed89adyv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Jul 2024 09:06:00 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Head = master branch.I did distclean is that the same as bootstrap?>> From: "T.V Raman" <raman@google.com>
>> Date: Wed, 03 Jul 2024 20:34:27 -0700
>> 
>> I have code that does
>> (require 'org-element)
>> and then uses functions like org-element-property
>> 
>> All this worked until recently (suspect until a week ago) but having
>> rebuilt emacs from @head, things are broken like so:
>
> "@head" meaning the master branch or the emacs-30 release branch?
>
>> 1. Code compiles with no warnings.
>> 2. When my compiled module is loading, calls to org-element-property
>>    throw a voide-function org-element--property error.
>> 3. grep on my compiled .elc file for org-element--property shows a match.
>> 4. grep on the *.elc for the above in the emacs build tree also shows a match.
>> 5. At this point, this has gone beyond my understanding of .elc files.
>> 6. Loading the .el source of my module works without errors; the .elc
>>    loads but throws an error when run.
>
> Did you try "make bootstrap"?

-- 



  reply	other threads:[~2024-07-04 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04  3:34 org: problem loading compiled files that use org-element T.V Raman
2024-07-04  6:06 ` Eli Zaretskii
2024-07-04 14:46   ` T.V Raman [this message]
2024-07-04 15:44     ` T.V Raman
2024-07-04 15:53     ` Eli Zaretskii
2024-07-04 16:17       ` T.V Raman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p91plrtnrjx.fsf@google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.