unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: morf <amorfortia@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70355@debbugs.gnu.org
Subject: bug#70355: emacs-29 build fails byte-compiling lisp/org/ox.el
Date: Sat, 13 Apr 2024 16:33:30 +0200	[thread overview]
Message-ID: <628b6349-39d9-d7f0-16f4-e381631bc06b@gmail.com> (raw)
In-Reply-To: <86v84lrbdh.fsf@gnu.org>

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

Ah yes, my bad, thanks for setting me straight. I've been out of this too long.



Eli Zaretskii wrote on 4/13/24 09:05:
> [Please use Reply All to reply, to keep the bug tracker CC'ed.]
>
> Forwarding to the bug tracker:
>
>> Date: Sat, 13 Apr 2024 02:19:17 +0200
>> From: morf<amorfortia@gmail.com>
>>
>> Thank you for responding.
>>
>> Yes, make bootstrap, did that already a couple of times, but I keep running into the same error. What is odd is
>> that the byte-compile (see fragment in my post) of ox.el gives the line number, when manually trying to
>> byte-compile org-element.el (the offender) I get no line number at all. Hmm.
>>
>> Will keep trying to figure out what is wrong here. I wonder where the tramp stuff enters.
>>
>> Eli Zaretskii wrote on 4/12/24 20:20:
>>
>>   Date: Fri, 12 Apr 2024 16:14:38 +0200
>> From: morf<amorfortia@gmail.com>
>>
>> While wondering if this is the place to bring my issue, allow me to state it nevertheless.
>>
>> I was trying to compile emacs-29 from sources. However the build fails, and chokes on byte-compiling
>> lisp/org/ox.el:
>>
>> ...
>> make[3]: Entering directory '/home/bjd/mint/packages/emacs-mirror/lisp'
>> '../src/emacs' -batch --no-site-file --no-site-lisp --eval "(setq load-prefer-newer t byte-compile-warnings 'all)"  -f
>> batch-byte-compile org/ox.el
>>
>> In toplevel form:
>> org/ox.el:82:2: Error: Eager macro-expansion failure: (error "Eager macro-expansion failure: (error \"Eager
>> macro-expansion failure: (error \\\"Eager macro-expansion skipped due to cycle:
>>    … => (load \\\\\\\"tramp-archive.el\\\\\\\") => (macroexpand-all …) => (macroexpand (eval-and-compile …)) =>
>> (load \\\\\\\"tramp-gvfs.el\\\\\\\") => (load \\\\\\\"tramp.el\\\\\\\") => (load \\\\\\\"tramp-archive.el\\\\\\\")\\\")\")")
>> Makefile:332: recipe for target 'org/ox.elc' failed
>> make[3]: *** [org/ox.elc] Error 1
>> make[3]: Leaving directory '/home/bjd/mint/packages/emacs-mirror/lisp'
>> Makefile:383: recipe for target 'main-first' failed
>> make[2]: *** [main-first] Error 2
>> make[2]: Leaving directory '/home/bjd/mint/packages/emacs-mirror/lisp'
>> Makefile:533: recipe for target 'lisp' failed
>> make[1]: *** [lisp] Error 2
>> make[1]: Leaving directory '/home/bjd/mint/packages/emacs-mirror'
>> make[1]: Entering directory '/home/bjd/mint/packages/emacs-mirror'
>> ***
>> *** "make all" failed with exit status 2.
>> ...
>>
>> I think this can be traced back to byte-compiling lisp/org/org-element.el; when I try to byte-compile that
>> manually I do indeed get the error about Eager macro-expansion failure, but I am unsure what actually causes
>> this failure.
>>
>> Comments?
>>
>>
>> I cannot reproduce that.  Suggest "make bootstrap".

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

      reply	other threads:[~2024-04-13 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 14:14 bug#70355: emacs-29 build fails byte-compiling lisp/org/ox.el morf
2024-04-12 18:20 ` Eli Zaretskii
     [not found]   ` <68e6ab8c-a01a-8863-f637-d0b255e7412b@gmail.com>
2024-04-13  7:05     ` Eli Zaretskii
2024-04-13 14:33       ` morf [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.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=628b6349-39d9-d7f0-16f4-e381631bc06b@gmail.com \
    --to=amorfortia@gmail.com \
    --cc=70355@debbugs.gnu.org \
    --cc=eliz@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 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).